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.
Oh, reka looks interesting. Thanks for linking it. I don't disagree with you about dynamic modules, I just think that EWM's architecture shouldn't be necessary. (In which I think we agree?)
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.
OP double negated - cursive is the norm for Russians of all ages.
Russian cursive is actually not that bad to read for the most part. Russian “print” is super awkward because all the characters are very angular.
There are some differences between generations (younger generations are more likely to write “т” in handwriting whereas the “correct” form looks more like a Latin “m”, but with obvious examples excluded (like the above), it just takes learning as a separate alphabet.
I know. I always feel utterly embarrassed when Russian-speaking friends write down a movie title for me, and I have to ask them to rewrite it in block capitals.
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.
But according to https://ircv3.net/software/clients, none of the clients you mentioned actually support emoji reactions (draft/react), and other features like multi-line messages and image uploads are likewise extremely limited in server/client support. So, for the time being, you can't use these features if you want to actually be interoperable with existing IRC users and their clients. Sounds like if you want decentralized, Matrix is still the better bet.
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.
Most if not all of their attacks are inexcusable. Calling a competing OS, CalyxOS, nazi sympathizers is unacceptable and when I first read that I started seeing the red flags.
Nothing is open about GrapheneOS aside from the source code. We officially know nothing about the leadership, their current plans, what their finances look like or even who this new mysterious OEM is.
not much in the parent comment is anti-graphene. it's probably the best available option for a mobile OS right now.
the sentiment is that the dev team - specifically one zealot - does not engage politely/rationally/transparently in any public forum, which undermines the image of the OS as a whole.
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).
There are many pragmatic reasons to do what Anthropic does, but the whole "soul data" approach is exactly what you do if you treat "the void" as your pocket bible. That does not seem incidental.
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.
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.