So it is architecturally possible (but infeasible in plain Emacs Lisp).

For river (the thing this article is about) I wrote an Emacs WM, but also opted for a dynamic module for the Wayland protocol parts: https://code.tvl.fyi/tree/tools/emacs-pkgs/reka

This one could technically be written in plain Emacs Lisp, but I'm happy to use something that already has all the XML codegen stuff for Wayland figured out. Dynamic modules work pretty well, fwiw.

It kind of would be good for everyone if they did do it though. Need to get rid of this monopoly, and maybe people will discover that there are alternatives with actually good workflows out there.

However, it all makes sense from the perspective of Graphene not attempting to be a general purpose OS like Lineage, but explicitly a security focused OS. Security is often in conflict with what the average consumer wants, and they can go use Lineage or whatever.

It's like writing lots of comments complaining about OpenBSD devs coming across as grumpy and refusing to support Bluetooth. That is part of their value proposition! You're just not the target audience and that is okay.

In many places the default is prepaid SIMs with separately purchased phones. Sometimes the prepaying can be automated (e.g. in Russia), sometimes it involves you physically going to a shop once a month or so (e.g. in Egypt).

The best article on this topic is probably "the void". It's long, but it's worth reading: https://nostalgebraist.tumblr.com/post/785766737747574784/th...

I spent some time on Google Maps, and the furthest spot I managed to find from a town was about 35km. Note that I didn't say anything about supermarkets - this is a thread about car reliability, so the context is how far you can be from a town where it's reasonable to expect that someone can help you with your car.

Note, not impossible: You can always carry cash to avoid phone-based bank payments (which would be needed at e.g. my local farmer's market, where nobody has a card payment terminal), some taxi services (Yandex Go for example) provide a web view with some of the features, you can open map services in the browser ...

But for the browser-based cases the experience will be even worse than the standard app experience, and friction is overall much higher.

As a result, only a very small fraction of nerds are committed enough to buy and use these devices. You then have a chicken&egg problem about getting a third option to work.

The only way this has been done semi-successfully in recent years is Huawei's HarmonyOS - and they did it by way of a) already being an absolutely massive phone company, and b) keeping around an expensive Android-compatibility core for many years.

If your thing ends up actually good you now have a defence against exploitation, and a way to generate income reliably (by selling the code under a different license). afaik, organisations like the FSF even endorse this.

It's much longer than the equivalent flight, but also much more comfortable. There's something annoying about airports - with the train I can get to the station 15-20 minutes before departure and it's fine.

Once the train rides get much longer than 12 hours it shifts, but there's a sweet spot right around there.