![](/static/253f0d9b/assets/icons/icon-96x96.png)
![](https://lemmy.zip/pictrs/image/1cd49a31-190e-42b4-9214-f53b5ae8ea66.webp)
Sorry for the confusion 😅 I don’t have any experience with NixOS apart from memes here in Lemmy. So… maybe?
Yes, I love atomic distros and I’m glad the term was changed.
Sorry for the confusion 😅 I don’t have any experience with NixOS apart from memes here in Lemmy. So… maybe?
Yes, I love atomic distros and I’m glad the term was changed.
I never needed it. I know from my school days that windows supports that use case. You get a full system and can do with it as you please but on reboot you get a completely fresh file system. The only thing that persisted were the user profiles that roamed through active directory. Seemingly there was no way of tampering with the file system, that would persist a reboot. And as school kids we tried hard 😅
I would be surprised if Linux didn’t have utilities for that, that were better designed and safer - but again, not my expertise.
Sure. Not all directories are protected and the ones that are, are just protected from immediate write access. A malicious app or a user who copies the wrong snippets can create overlays and apply them immediately without a reboot. Having atomic distros is awesome but it has nothing to do with immutability and it someone needed that for example for PCs that are in random control at least some of the time, then they need a different solution on top, that gives actual immutability.
No, that’s not what I wrote.
I specifically picked the statistic that claimed to have included the full cost of installing something new. Most other statistics only include prolonging the life of existing plants, thus ignoring the installation costs completely. You can just quote the paragraphs that prove your point the same way I have and then we can discuss further. Maybe I made a mistake, who knows.
Silverblue/Kinoite
Those are not immutable, especially on the file system. I’m glad the fedora team switched the term to “atomic”, because “immutable” set all the wrong expectations.
If they are used to Windows, go with Kinoite. I agree with the previous sentiment, that atomic distros are much safer. Far fewer bits and pieces that can break. I love it.
Extremely cheap per kilowatt? Every statistic out there that I’ve seen and that includes government funding, as well as construction and deconstruction costs, paints a different picture. Nuclear is only competitive with coal or the relatively underdeveloped solar thermal.
In 2017 the US EIA published figures for the average levelized costs per unit of output (LCOE) for generating technologies to be brought online in 2022, as modelled for its Annual Energy Outlook. These show: advanced nuclear, 9.9 ¢/kWh; natural gas, 5.7-10.9 ¢/kWh (depending on technology); and coal with 90% carbon sequestration, 12.3 ¢/kWh (rising to 14 ¢/kWh at 30%). Among the non-dispatchable technologies, LCOE estimates vary widely: wind onshore, 5.2 ¢/kWh; solar PV, 6.7 ¢/kWh; offshore wind, 14.6 ¢/kWh; and solar thermal, 18.4 ¢/kWh.
Emphasis mine, source: https://world-nuclear.org/information-library/economic-aspects/economics-of-nuclear-power
1Password can’t fail that hard easily. They’ve done great write-ups to compare their architecture to that of LastPass. Long story short: it’s the secret key that protects you: https://blog.1password.com/what-the-secret-key-does/
Trouble with those tests is, that they become unreliable or even meaningless, when you have done then once before, let alone daily.
What I’m missing from the article that claims that the “precise” burial place of Plato was now revealed: is it, though? Is the location of the shrine of the Muses known?
Windows hss supported slashes in both directions for a very long time. I almost exclusively use forward slashes to reduce mental load when switching between OSes.
This would be my gut reaction as well. I’ve met some game developers privately and got to know them better and after that a career in game development was out of the question for me. It’s not even the fault of the game studios, many of which are being lead by idealistic game devs themselves. It’s the publishers who only offer contracts that are so tightly knit, that many game studios go bankrupt after release if they can’t get another contract quick enough. The whole industry is rotten and no amount of management will save that on the lowest level of the food chain. It felt too me that only idealistic devs with a high frustration tolerance go into game development and that is being exploited to the extreme.
Wunderbare Form des Antiterroranschlags
When the low rolling character convinces the high rolling one, that they are seeing things, the real fun begins.
Very well written. I’d only change something about this paragraph:
- Operated without production interruption even with frequent team member exit during critical phases of operation
Sounds like people were quitting on you because of terrible work conditions you fostered. An alternative could be:
The original author of git flow begs to differ. But hindsight is always 20/20 https://nvie.com/posts/a-successful-git-branching-model/
If you use feature flags, don’t forget to remove them after some grace period. Almost everything bad about feature flags that you can read online is related to long-lived feature flags and all the dead code and complexity involved. Adding a feature flags without a commitment and plan to remove them (the flag, not the feature), is asking for trouble down the line.
You can implement public or semi public ledgers without Blockchain. That’s what banks are doing already by sending huge CSV files internally and externally. Blockchain is not a technology of zero trust. It’s close to the opposite. You trust a few peers and blindly trust everyone they trust. That way you trust a network that you know nothing about and if the network decides on a common truth that you are convinced is incorrect, there is nothing you can do about it. The consensus always wins and there is no single entity to complain to and get it fixed. This is great for making sure that many actors need to be bad actors in order to have the whole system fail. It’s bad if you don’t trust anyone and want to make sure that your standards are always observed. From a technology standpoint I love the concept of Blockchain. But use cases that are not forced are few and far apart. Too few for the amount of hype it receives.
Also, Kanban was invented in the 40s as a process for automotive production lines. That’s why it aligns so well with maintenance and operations projects in IT. It’s ridiculous how more and more people claim it comes from software development and would not fit hardware projects, when that’s the core use case of the methodology.