Care needs to be taken with big orgs like the NHS to not try and boil the ocean with massive IT systems. Concentrating on open interoperability standards allows for smaller more flexible contracts and the ability to swap out components when needed.

Open source licences would be the ideal default although at a minimum the purchasing org should have a licence that allows them (or subcontractors) to make fixes without being tied to the original vendor.

The other option is to use VirtIO with Native Context support as a software based partitioning scheme that is relatively lightweight compared to the mdev approach.

The kernel on GitHub is just a mirror - the primary source is on kernel.org

Not just that - modern Androids compile apps in a VM these days to reduce the attack surface of the compiler. You can also push other services into VMs that support the main image. You could even push some vendor drivers into VMs and help keep the main kernel less of a vendor fork fest.

Does anyone know what the underlying filesystem is on DSM? The ability to easily replace disks with a degree of redundancy across the 4 bays is the biggest plus point for Synology although I have no doubt all the bits underneath are the Linux storage stack.

It’s a shame because I really like the point and click nature of DSM. Although I’m a happy Linux hacker I don’t want another Linux box to suck up my limited admin time just to store files.

A lot of the Emacs language modes have been replaced with tree-sitter equivalents now.

Bold of you to assume we’ll make it that far. I’m not convinced that our current networked CO2 phase isn’t another great filter event.

FLOSS projects can only be sustainable if their are enough shared interests able to support it through contributions of all kinds. Fortunately the code is free so that constellation of support can change over time. It’s a shame this particular line of government funding is coming to an end but others can help.

Android gets a leg up from being built on a FLOSS base but I don’t think it was the community that pushed Android to where it is today. That’s taken a lot of money and resources from Google and it’s phone partners investing in the slightly more open platform than Apple.

That’s not really true. Yes avoiding complex instructions makes the front end easier to pipeline but there are lots of smarts in the backend to do prediction and scheduling to keep the execution units fed. The ISA might be free to use but no one is sharing their highly optimised server silicon architecture designs.

RISC-V’s challenge is can they standardise the software ecosystem enough that things just work across a multitude of chip providers or does everything devolve into specialist distributions taking advantage of each manufacturers “special sauce” custom instructions.

Gaining design wins over Arm’s microcontrollers for bespoke hardware was the easy bit. Replacing stuff in the server space is much harder and something that took Arm decades to make inroads into.

Very handy site. Nice 🙂

I pay for it so the TV and web experience is ad free. I use PipePipe on my phone because the native client won’t stop pushing shorts at you.

Do you think there is information YouTube wouldn’t collect about you even if they could be better at selling ads to people based on it?

Do you live somewhere with data protection laws? If so you could request a dump of all personally identifying data they hold on you.

I think the most useful thing for this is hosting repos that suffer from constant DMCA takedowns. Emulators, ad-blockers, site revancers etc.

It’s not like Android is especially open to drive-by contributions anyway. I don’t think really changes much for the downstream consumers of the releases.

We’ll go from Google sucking up all our data to another entity sucking up all our data and selling it to other people. How much funding does it take to keep Chrome running?

It used to slowly drive haters insane, hence mad haters. There was a theory Napoleon was exposed to excess levels of Arsenic over time although that might have well been background exposure. Nevertheless over time it’s not good for you. Neither is lead.

Magit is one of Emac’s many superpowers.

These are all excellent ways someone can contribute to a project. Our project website has a repo anything can contribute to to make changes, even the blog entries are statically generated pages.