This post literally links to the leading one.

I was never distro-hopping much. Switched from Debian only when I got a job with Red Hat, and then switched to openSUSE when I switched to SUSE. I have actually switched recently to my own semi-distro https://sr.ht/~mcepl/moldavite/ (basically MicroOS with sway).

Eh? Both pandoc and rst2epub can generate eBooks. All those lightweight markup languages are especially awesome for converting into various output formats.

Discuss it with https://lemmy.world/post/12126335

I think you have arguments about MicroOS (or Silberblue, which I know less about, and possibly Nix, which I know nothing about, and it seems to me it is not in the same group) wrong. Take a look at this https://youtu.be/lKYLF1tA4Ik.

https://github.com/swaywm/sway/ still claims that sway is “i3-compatible Wayland compositor”.

Ehm, what would be a difference for you, if you install sway?

Not vim necessarily, but I would really suggest thinking about a plain text editor of your choice and some of those lightweight markup languages (Markdown itself, reStructuredText, ASCIIDoc … I prefer rST, but they are mostly the same). Exactly because it allows me to concentrate on the content and ignore formatting. Besides, formatting, do you write for print or as everybody else these days for HTML? Why do you need a large word processor which is build primarily for preparing documents for print? Every serious text editor has some kind of plugins with spellcheckers, grammar checkers, dictionaries, etc.

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.

https://youtu.be/4WuYGcs0t6I (Richard Brown (FOSDEM 2023): “I was wrong about Flatpak, AppImage, and Snap”)

Yup, and “I use Gentoo” before that.

Without regards about this discussion, run, don’t just go, and buy a vertical mouse. Just saved my wrists.

Give a man a regular expression and he’ll match a string… teach him to make his own regular expressions and you’ve got a man with problems. – yakugo in http://regex.info/blog/2006-09-15/247#comment-3022 (and yes, it is http:// never https:// for this domain)

1. Many Linux installers can preserve /home when asked nicely.
2. (as root) rsync -avz /home/youruser/ other-machine:/home/

I haven’t meant it as the criticism of ZFS. It is just so, and perhaps there were good reasons for it. Now (especially with the convergence trend) it hurts.

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

ZFS is not really hip. It’s pretty old. But also pretty solid. Unfortunately it’s licensed in a way that is maybe incompatible with the GPL, so no one wants to take the risk of trying to get it into Linux. So in the Linux world it is always a third-party-addon. In the BSD or Solaris world though …

Also ZFS has tendency to have HIGH (really HIGH) hardware/CPU/memory requirements.

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.

Mimic is by far the best I was able to find from FLOSS TTS software.