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

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.

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/

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

I am on MicroOS-based distro, so all my GUI applications are from Flatpak. I don’t see any difference from more traditional distro, it just works.

You don’t need a dotfile manager, you need proper backups.

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.

deleted by creator

Please, don’t use subjects like “I love this”. Please.

It turned out to be a lot more complicated https://github.com/JimmXinu/FanFicFare/issues/985 and not at all a Flatpak fault.

Don’t. That is to distro hop.

Yes, I am a long time openSUSE user (heck, I am a SUSE employee!), but the difference between various distros is truly minimal. Yes, openSUSE has Yast, but aside from that it is really very similar to any other distribution. Instead of spending time on distro hoping, just sit on your behind and learn to resolve your issues with your current distribution.