You missed on a lot with a pet rock, my daughter discovered them just a few years ago and was completely in heaven from the idea. Perhaps, the similar with AI?
Not just with Zypper, but if you have everything on BTRFS, I have managed to do so using btrfstools while still on MicroOS (which is where I came from) and with guidance of Gemini.
Iamb, but yes, sometimes with help from the Web client in Firefox. (old Element Android on F-Droid, because Element company hates its customers, and Element X is still not supported on One Element).
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.
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.
They should keep it about something. The first film seemed like a great start to so many stories, but the second film was about none of those (and yes, I am still bitter, that nobody wrote a story of Modesty Barebone).
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.
TL;DR
You missed on a lot with a pet rock, my daughter discovered them just a few years ago and was completely in heaven from the idea. Perhaps, the similar with AI?
if you have it on a separate partition, it is more complicated if /home is just a BTRFS subvolume.
Not just with Zypper, but if you have everything on BTRFS, I have managed to do so using btrfstools while still on MicroOS (which is where I came from) and with guidance of Gemini.
Iamb, but yes, sometimes with help from the Web client in Firefox. (old Element Android on F-Droid, because Element company hates its customers, and Element X is still not supported on One Element).
You can right now … except it is a paid service … https://element.io/blog/element-one-all-of-matrix-whatsapp-signal-and-telegram-in-one-place/
This post literally links to the leading one.
Hmm, how to react to that? “Go through his brain and look for loose thoughts.”? (Sounds like Legilimency from Harry Potter world)
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
pandocandrst2epubcan 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.
They should keep it about something. The first film seemed like a great start to so many stories, but the second film was about none of those (and yes, I am still bitter, that nobody wrote a story of Modesty Barebone).
You mean, of course, his role of a lifetime.
OR
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_socketon 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.