Yes, of course, the sockets are the answer to everything (and BTW, d-bus uses sockets as well, e.g. /run/dbus/system_bus_socket on my current system), but the problem is no standard for the communication over these sockets (or where is the socket located). For example, X11 developed one system of communicating over their socket, but it was used just by few X11 programs, and everybody else had their other system of communication. And even if an app found some socket, there was absolutely no standard how exactly should programs communicate over it. How to send more than just plain ASCII strings? Each program had to write their own serialization/deserialization code, their own format for marshalling binary data, etc. Now there is just one standard for those protocols, and even libraries with the standard (and well tested) code for it.

Size. I really don’t like the current 6”+ phones. The last phone I really liked was Google Nexus 5, because it had just 5" display.

This is twelve years old, but it nicely illustrates what BTRFS (and ZFS on other OS) can do … https://youtu.be/9H7e6BcI5Fo?t=206

It cheaper alternative it RHCE. It should be able to persuade a potential employer that when they put you next to a Linuxbox the result most likely won't be an explosion. It did work for me and I got my first IT job with it, paradoxically with Red Hat. While being there I got also RHCE (both certificates are long expired now) and it was a way more practical and thorough. Whereas LFCS is much more wide (including LDAP and similar exotics if I remeber correctly), RHCE is much more deep.

As usual, you get what you pay for.

Talking about unpopular, I have just created fork of the project Greybeard (MicroOS+Sway) called “Moldavite” (meteorite induced explosion near Nürnberg caused a lot of gems falling on the ground in Bohemia, if it is not a symbol of the cooperation inside of SUSE, then I don’t know what would be ;)). The main project site is https://sr.ht/~mcepl/moldavite/ and OBS project is https://build.opensuse.org/project/show/home:mcepl:moldavite . Whereas, as I understand it, Greybeard is at least for the moment more or less on the back burner, I hope to continue to work on this.

People who can use them effectively tend to be a way faster with the regular admin work. Also, they can do some things which are not that simple on the command line (browse through tarball, browse through remote directories).

Because X's janitor budget for lunch is better than their whole budget.

I am trying to help with vis and it is a lot of fun to use. Aside from things where I really need neovim (because of large plugins), I use vis every day. Sam and ACME (and whole Plan9 for that matter) have the biggest problem with being too GUI oriented. They are from times when we discovered a mouse and then decided we need to use it for everything. Thirty years down the line we know better: we don’t.

Please, don't use subjects like "I love this". Please.

The huge difference between FTC and EC in terms of the mandate of their operation. Whereas the Sherman Law and FTC are operating with aim to protect customers’ rights or something like that, EC anti-monopoly law is oriented just on that: fighting anti-competitive behaviour. The problem is IMHO that “customer rights” is so flexible term, that (with good support in the campaign contributions, I am sure) it is easy to persuade FTC that almost anything you do is perfectly nice. EC’s anti-monopoly mandate is on the other hand rather strict and inflexible.

Firefox can import from Chrome profile.

Actually, this is not necessarily true. Because it is open source doesn't mean it cannot be commercial. I can happily imagine that with the future rise of spam, porn, and other nasties, I would happily pay small amount of money for well moderated, clean experience.