EWM implements a Wayland compositor as a native thread spawned by a dynamic module in Emacs, it's a full compositor within the Emacs process: https://codeberg.org/ezemtsov/ewm
So it is architecturally possible (but infeasible in plain Emacs Lisp).
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 is probably country and language dependent, I think. I don't know anyone under 40 who doesn't write in cursive (in Russian), and for other languages I personally also write in cursive (and learnt that in school). I'm in my 30s.
Okay, so which hardware are you buying that isn't using any Chinese components?) I don't think the empire can make this kind of hardware from scratch without China at the moment.
Killing off free repos is not going to happen. That would be a suicide move on the level of the Digg redesign, or Tumblr's porn ban.
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.
People go through all this trouble to host convoluted chat systems, and all this time IRC is right there. There's modern servers like Ergo and modern clients like Halloy (or for the JavaScript addicts: Convos, The Lounge, Kiwi, ...) providing all the multi-device history sharing and emoji reactions you could need. All on top of a super simple, extremely battle tested protocol.
These weird anti-Graphene posts confuse me. I use GrapheneOS, fwiw, and I believe some things the project does (like its attacks on F-Droid) are misguided for orthogonal reasons.
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.
I've only seen the carrier locked phones and long-term contracts in a handful of countries. I've lived in a lot of countries on three continents.
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).
No. It was obvious from the title that this was about the UK, and also why should they - American sites don't indicate this either, and they have no monopoly on the language.
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.
The EU is entirely dependent on US services, which don't much care about a fringe phone OS some fraction of people in the EU use. It's like adding duck/egg, crow/egg and other similar problems into the dependency web, too.
You can sell the phones alright, and they might even work, but the fact is that participation in society - especially if you live in a city - will be much harder without Android/iOS.
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 a definitive answer on this topic was known then it, well, would be known.