• 0 Posts
  • 88 Comments
Joined 2 years ago
cake
Cake day: July 5th, 2024

help-circle







  • Saying the chance of something going sideways is smaller than on Windows isn’t saying much

    True. I’ll grant you that.

    I’ll pick a distro that’s stable by default

    Arch isn’t “unstable” by any means. I’ve been running Arch EndeavourOS as my desktop distro that I develop on for years and it’s entirely reliable. Now I personally wouldn’t run Arch on any of my distros (I go with either Debian or NixOS), but there are people who do it and it works fine.

    Edit: I said “Arch” but I meant EndeavourOS, which is Arch with some QoL improvements.


  • But if my client is angry and my boss is breathing down my neck, and I can’t work because a thing isn’t thing-a’lating, a support path is essential.

    Arch is still stable enough for that. The chances of something going sideways is smaller on Arch than on Windows. And unless you’re a medium to large company paying Microsoft for enterprise support, you’re going to be stuck with forums for community help with Windows.




  • But nobody who uses it treats it like “just a tool.”

    I do. I use it to tighten up some lazy code that I wrote, or to help me figure out a potential flaw in my logic, or to suggest a “better” way to do something if I’m not happy with what I originally wrote.

    It’s always small snippets of code and I don’t always accept the answer. In fact, I’d say less than 50% of the time I get a result I can use as-is, but I will say that most of the time it gives me an idea or puts me on the right track.


  • Kinda. Generally the user files (including custom installed applications) are on a rw partition. Whereas the system files (OS files, root folder, etc) are on a ro partition. When updates are applied to the core system they come as complete images. No compiling from source on the fly.

    The advantages to this is that it should be near impossible to break your system. If you need to roll back to a previous version the system just/downloads/mounts the previous image. There is less flexibility in terms of changing system files. But the idea with immutable distros is that you shouldn’t be modifying system files anyways, and there are different ways to accomplish things.

    A really good example is Android. Android (non-rooted) is kinda-sorta an immutable distro. Except it uses an A/B partition method, where the active system downloads and installs to the other partition, triggers a flag, then a reboot picks up the flag and boots from the newly installed partition. If anything goes wrong, another flag is triggered and it boots from the “good” partition.

    It’s not quite the same, but at a high-level it kinda is.

    Edit: article I found about it

    https://linuxblog.io/immutable-linux-distros-are-they-right-for-you-take-the-test/




  • I think the best bet is an entirely new system from the ground up that has an open architecture that every company can equally implement that from the ground up and is as simple as possible.

    This keeps getting said by people who don’t understand operating systems. Even if you build something from the ground up, you still end up with an operating system very much like Linux and Windows. The choices that were made for each OS were not random. The principles of I/O, user input, graphics display, filesystems, etc, are more or less universal concepts across all OSes.

    What you will accomplish is making an OS that no one will use. Linux, Windows, and macOS already fill every market that can be filled. Microsoft tried to become a third player in the mobile market and their product died pretty quickly.

    Google has been trying to build Fuschia into a new OS and they’ve asked back their ambitions (from what I recall reading).