less friction is better

I strongly but respectfully disagree.

Are you installing your secondary OS on the same drive or on a separate SSD?

Do terms like partition, file system and bootloader mean anything to you?

This isn't a discussion about "entitlement", but ease of use.

This makes sense, but am I allowed to ask "why do those corporations who will only use software until under mit license or BSD, not want to contribute back? Wouldn't that make them leeches?

yeah i mostly agree. it's not that much more work to make it available directly in the software store through flatpak. this thing of developers making their software and not even bothering to even build it on linux must end right now.

that said windows users will still get their .exe files from github. sorry, no better alternatives for them.

that's their self made problem. BSD could as well be on GPL if they're open sourcing it anyway.

if the standards are open, what is the problem with open sourcing code that implements that standard?

Yes, the filesystem is BTRFS set up with subvolumes that fit the way pacman installs packages well. If a package or a -Syu breaks something, you can simply roll back but not lose the files in your /home. In the default CachyOS config your /home also gets rolled back which caught me by surprise the first time and deleted half a day's worth of writing. So in the Limine boot menu you can select the snapshots that get made before and after each pacman command, boot into them and restore your system to that specific state but keeping your configs, documents and such. It's not a back-up or atomic filesystem, but it's definitely a way of making your OS reliable that also fits an Arch-based distro way more than the ostree concept I was working on.

Regarding the speed optimizations, the CachyOS kernel is fantastic, 1000Hz tickrate, custom scheduler and so on, it really is noticeably smoother and faster. Compiling everything in -v3, -v4 microarchitecture optimizations CAN be beneficial in some cases but mostly it caused the CachyOS team to fall deep into scope creep, they sometimes lag weeks behind in releasing updates for packages the core and extra repos already have so I decided to stick with the regular x86_64 only, just like stock Arch also does.

Cool project for the ui possibilities, but idk about my desktop being an effectively electron app

Cool! Hats off! 😊 I was running Arch for a few years before going to Artix to easily get rid of systemd - didn't have the enthusiasm to go through the hassle of replacing init and process manager... But!

I have been wondering what could be done to a clean Arch install other than installing exactly what I need and removing what I don't need. In that spirit, what are these "speed optimizations" that CachyOS bring to Pu239?

Also, what does

ostree got replaced by a perfect Limine-BTRFS-Snapper setup
mean? Is the OS filesystem BTRFS on Pu239?

I love the detail of python2 lmao.

Oh. my. god. That just triggered me and I'm a dev. WHY THE FUCK ARE RELEASES AT THE BOTTOM ON MOBILE??!

Like on the desktop it's right there in the right panel. Then I open the mobile interface for some APK and for the life of me I can't fucking find it. So I enable desktop mode and there it is. Jesus fucking Christ I hate it. It took me months to find it.

There is no reason to be aggressive, insulting and confrontational the way you are.

If you can’t make your point without resorting to personal attacks then consider not replying until you’re cooled off.

It’s pretty clear from what I said that I’m referring to the pc still running fine while multiple ssds have died.

From what I can tell the other components the op references are: the WiFi module. Unfortunately radio baseband chips were well into their implementation without any kind of heat mitigation era when this pc was manufactured. That’s another part that could likely benefit from sticking a heatsink on, lots of desktop motherboards and even some laptops have some kind of heatsink or pad coupling the radio to the chassis. Probably glue a nut to that too, straighten it right out. Radio is even more duty cycle dependent than ssds due to the nature of ip communication. It’s likely what drove thousands of devices to be designed without any way to deal with the heat from those little things. Why spend five times the cost of the chip sticking a sink on there when it’ll just automatically throttle down to protect itself was probably the engineering calculus.

When we're talking about free software someone makes in their free time, I don't think the normie is entitled to anything. I made a thing and gave it away to the world, figure it out.

That being said less friction is better, so I really appreciate when the dev gives simple to consume packages.

This dynamic changes when money starts getting exchanged, either explicitly by buying or implicitly by donating, the sponsor is entitled to have their needs acknowledged and addressed.

Oh yeah that’s just what we need, an entire desktop based off of Googles rendering engine. I honestly wouldn’t be surprised if the entire desktop was AI slop too.

https://codeberg.org/tazjin/reka

River based

Why is Slax so small? (Or, rather, why are other distros so large?)

Sure, yeah.

So what you want is an app store, then?

3 dead ssds

67C idle ssd temps instead of ~45

OP mentions 'other' overheating components

Pics of a case that's basically a cramped oven

Pics of ssd on back of case in dead air envt

Based on what we know about the pc it’s going fine

Dumbass.

Why not just wait and see how things turn out?

The knowledge and experience to reliably predict how this will end and empathy for anyone who has to deal with a PC sudden (or more likely slow and bizarre) death event.

There’s no need to continue to be insulting and confrontational.

Talks out their ass and defends it to the death when called out at the expense of OP

Okay dumbass.

"smelly"??

I think you're projecting

Wow that's actually really sweet. I used Slax years ago but they've certainly refined their product.

And 30 less pre-installed packages you would need to get rid of first

That is correct.

Yeah, I don't recommend anyone using GPL x "or newer". I explicitly use AGPL 3 for most code.