On one hand, I'm really glad they had something like this ready, espeecially as someone who did work in cybersecurity.
On the other, I really hope they move it outside of the US jurisdiction. As it is now (based in Washington, as mentioned in FAQ), the US has basically won - CVE continues to function, they don't need to pay for it, and they can still exert power over it since it is still in the US. Fuck that.
This. The whole discussion about "tinkering with immutable distros" fells like it misses the point and literal meaning of atomic and immutable.
Rebuilding the whole OS to layer another immutable read-only part into it isn't tinkering. Of changing one OS file has you rebooting, then that's not tinker-friendly.
Atomic distributions are by definition something you don't tinker with, and it stays the way you need it.
And no, having bundled distrobox or rollbacks doesn't make it tinker friendly, you can do both on normal distribution.
But once you have done tinkering and want the system to stay the way it is - that's what atomic means and is for.
Snapshots and rollbacks already exist in other distros, so the (only?) advantage you are mentioning is kind of a weak point.
Everything is a bother, since you can't just easily dnf install what you need, without actually rebooting or dealing with containers. I wasn't able to get a Win11 VM and work VPN properly working for long enough that rebooting to windows and just doing the RDP there was easier for me. (Because getting TPM to work simply wasn't feasible on atomic, and no - FOSS rdps didn't work)
If an app doesn't have Snap or .App file, it will be a bother. Having to enter a container just so I can edit something in a properly set up nvim just sucks, adding bloat to something that could have been one easy command.
There's a learning curve that gets in your way a lot, and since there are no actually payoffs for going through it, why bother?
I currently have Bazzite on my desktop as a daily driver, and it has been way worse experience than I had with Nobara, debugging any issues with I.e audio or drivers is awfull because the resources about it are a lot sparser, and so far I simply don't see anything it does better. I did rollback my Nobara few times with brtfs and it never was an issue.
One thing that may be worth it, if it's the case - can you actually export your layers into a VCS that you can then simply clone, just like you can with NixOS? Because if not, then following your logic, there's really no point in choosing atomic distro over NixOS. Sure, it has a slight learning curve, but you get a system you can not only rollback, but also easily clone anywhere you need it. What are your reasons for not using NixOS?
That said - there is one use case where atomic distros are amazing - if you have a, well, atomic environment you don't need to change often. Bazzite on SteamDeck or LegionGo being the best example, I'm using it there and it's been amazing experience.
He's 18, contributed to the Switch emulator Ryjunix, alongside some other projects while also doing school. His reasoning is that he along with Whisky doesn't have the capabilities, manpower and skill to properly contribute to the Wine on MacOS, just like Proton is doing for Linux, and that he's worried that if Whiskey would make CrossOver unsustainable (who do have the resources to do it better), that it could kill Wine on MacOS.
I'd say that's fair, and anyone allegeding blackmail or buying off is insulting.
This... Is actually unironically the best argument I've heard in favor of AIs so far, that I haven't thought about.
Still - the thing you'd be doing instead is feeding money and attentention to AI bros, and that's probably even worse than any job you could be micro sabotaging.
How's PostmarketOS doing recently, anyone using it as a daily driver? I have a PinePhone in a cupboard that I bought more than a year ago that lasted like a week as my daily before I quickly gave up on it (or rather, reinstalled it to Kali Nethunter and just have it in my pentesting bag. Not that I ever used it :D), since it had too many issues.
I highly recommend looking into vertical ergonomic mice. It's really easy to switch to (took me around an hour to get used to it when I randomly decided to get one), I regularly switch between regular and vertical for work/gaming and I don't even notice any difference, and they are reasonably cheap (I've been using one for 15EUR).
If you can't stand anything else, I highly recommend giving vertial mouse a try. It took me around hour top to get used to it and forget that I switched mouse types, and I also regularly switch between vertical for work and regular for gaming and it's effortless.
The point is that the mouse is, well, vertical, so you don't have twisted wrist. It's a pretty small difference and it's super easy to get used to it, and the mouse costs basically the same as a regular mouse. I have been using one for 15EUR for years now, and am pretty happy with it - I don't see any reason why not to make the switch, if it has a health benefit.
I have randomly decided to buy a cheap vertical mouse when I needed a new mouse in my office, and it has been suprisingly easy to get used to. I didn't struggle with it, and after a few hours I didn't even notice any difference, so I highly recommend giving it a try.
I still use regular mouse for gaming, but for any office work or programming, as well as in a laptop bag, I have this mouse. I haven't really looked into any research behind it, and since I'm fortunate to not have issues with my wrist (so far), I can't really rate the health benefits, but I assume it should be at least slightly better than a regular mouse.
And since the transition was effortless, the mouse is cheap and works for daily programming and web browsing perfectly, even if the health benefit was actually small, I don't see any reason why not use it instead of a regular mouse.
I didn't know that LINQ had more usages than just me being lazy to write a for loop, I have something to look into, thanks. Judging by the first documentation page I found, I wouldn't even recognize the syntax as the LINQ I'm used to. I really need to catch up on new C# stuff.
Saying LINQ produces garbage is uncalled for when it’s a different use case and supports other or more use cases.
I don't think I understand why would it be uncalled for, though. At least in the context of game development, where even small allocations can be a problem, it feels ok to generalize, especially if most people probably only encounter LINQ in it's basic form instead of the other use cases. Mostly for the sake of new programmers, who may fall into a trap of over-using it.
Unless you are talking about using the term garbage, which now I realize may sound degradatory. That wasn't my intention, and I don't have any negative connotations with that word, so it was not meant in a negative way - I though it's the correct terminology for allocations that need to be collected by garbage collector later, which is an issue in performance critical applications.
I don't think you need any active sabotaging in this regard. I'm not really worried about the future of LLMs, because we are already at a point of feedback cascade where thanks to LLMs, more and more of content they steal from the internet has been AI generated by them anyway, which will eventually cause the models to collapse or stagnate. And besides, you wouldn't be able to sabotage at a scale required for this. Thankfully, the spread of fake AI generated websites and content it has enabled is so massive, that it works as well.
I'm looking forward to that.