I couldn’t agree more with this, projects like artix are undermined by all the hard dependencies on systemd and Bash.
Void attracted me because of the support for posix, runit and musl (plus good zfs support). It’s unfortunate that Arch doesn’t have that greater portability.
This sounds a lot like Luet which is used in Moccacino (formerly Sabayon).
The manual is OK, much of it’s out dated and often outright wrong. It is still a great document.
Edits to the wiki are often knocked back if they weren’t made by the inner circle, discussions on the back page are often closed and frankly the TUs are mostly wankers. The forum policy on necro-bumping leaves half answers everywhere but the notion of “put it in the wiki” is undermined by the toxic community among inner party members.
Arch is a great middle ground between Fedora and Gentoo, but I had to walk away because the community was so toxic and childish.
I’m using void and Gentoo now and I’m pretty happy, anything that doesn’t run works in a container anyway.
TL;DR: community behaviour is much more important to me than technical use.
You want H2OGPT or just use Langchain with CLI
Just use flatpak and podman, in a punch you can proot into a different system / zfs data set / btrfs sublime
Re your update.
My framework has been great, I’ve had no issues with it and I’m quite happy. Make sure to go with the matte screen though.
In saying that, I think I was happier with my thinkpad, but I have no good scientific reason for that, I suspect the nipple and keyboard are a big part of it.
Framework and ThinkPad have both been a really positive experience.
Also, if it’s just the DE, install sway / i3 and try that for a week. If you liked that it’s on literally every Linux distribution, even the BSDs.
Go with EndeavourOS. It won’t “just work”, but it will be the best compromise between confusing abstraction and low level frustrations.
Fedora is good but it abstracts a little too much away, this is great when you understand how software works, but it’s very confusing when you’re new to Linux and programming.
Arch is good, but you won’t be able to hid the ground running, you’d have to sacrifice a weekend to learn.
Go:
Tinkering with those in that order, after about 6 months, you’ll start to feel at home.
Worth mentioning that one can use bubblewrap directly over chroot to get similar behaviour as well.
It’s often simpler to use distrobox but being able to rsync chroot a between devices can be very convenient.
Cachy is a great live usb because it has zfs.
I enjoyed arch for how straight forward the install was.
Gentoo however, every time I do that from scratch it’s with X, Westland is NetworkManager that give up (my recommendation is oddlamma installer)
It’s great but still really unstable. I’ll be sticking with Sway / DWM for a bit longer.
However, it looks promising.
Similarly OpenSuse Aeon. A Benefit of Suse is the greater portability of the tooling.
Further TL;DR
In preparation for an IPO:
Reddit: you must now only use our app to prop up our add revenue. No third party apps (unless you pay us handsomely)
Everyone: no thanks, just make our own alternative
Well, no, neither approach is better than the other, it’s apples and oranges.
There will always be a place for installing native applications. In the least analysis, the container itself should probably have some dependencies packaged for the target program.
The benefits of containerisation are obvious, but it’s been a lot of work and there are still edge cases to iron out.
FreeBSD has had jails since 2000. Linux, however, only got namespaces in 2008 and the first bubblewrap release on GitHub was 2016.
I’ve been using chroots and containers for development for about 2 years now and it’s been fantastic, however, I’m still grateful I don’t have to jump inside one every time I need to write a python script.
The ZFS stuff was exciting! Are they still incorporating zfs in current releases though?
Snap is a sandboxed environment to install applications in.
Flatpak is a more portable implementation of the same broad idea, it downloads a chroot and runs applications from within using a separate program called bubblewrap (one could, in theory, use chroot to run apps from within the downloaded flatpak images, bubblewrap offers further isolation through things like namespaces and cgroups etc. )
Snap, unlike flatpak, is a Canonical specific implementation that has a reputation for breaking a lot of things.
PL can have a large impact on features, bugs, bug reports, troubleshooting, performance and documentation. Particularly when dev resources are limited.
It’s hard to see how this opinion holds any water.
Rust is a great choice for a shell built as an interactive shell that doesn’t have to be core to the OS. Over C++ this also makes development more accessible to young programmers.
Just use anything and set up a good workflow with snapshots.
Have a “current” snapshot, rollback to it before using and then re-snapshot over it.
Now your system is immutable in practice but you can still edit /etc to debug.