I played for a while on the switch, controlling with buttons and stick is so much better then with a finger on a phone or tablet, but they kind of stopped supporting the switch version with new updates only available to mobile OS. It is a fun little game to kill a few minutes.
I tried Elder Scrolls: Castles when it came out but it didn’t click with me.
I will never understand why it is a good idea to put SMB into the Kernel. Stuff like that belongs in user space, IMHO
There was a major focus shift maybe 5 or 10 years ago towards security in Linux design, especially with the development of Wayland, pipewire and systemd. The problem is that accessibility software behaves in many ways like spyware or malware. It reads all windows, it hooks themselves in programs, it redirects output and input. The security focused (even security first) approach of many developers broke all the accessibility workflows and proper API to do it the new and safe way have low priority. A few exist but it is still far away from feature parity.
That’s why I am against the Wayland default or even worse Wayland only approach that many distributions have nowadays, Wayland is still barely useable for many people who need working accessibility solutions and that should be seen as a major stopper issue for a wide release like that.
F2FS was made primary with removable storage like SD cards and USB thumb drives in mind.
16TB is still a few years away for those, but yes a update to add larger sizes would not be that bad.
It was never a secret that speed is not Btrfs strongest feature. That was known for years.
Most likely because it is not a Filesystem that is available as a native, in-tree, Kernel module.
Edit: Yes, there just is no 6.15 Version of the out of tree module for OpenZFS yet
Supported Platforms
- Linux: compatible with 4.18 - 6.14 kernels
Atomic/immutable distros are just another tool in the tool box. It is great for systems with a limited use scenario like the SteamDeck or HTPCs. I also love to install immutable distributions on systems where the user (often IT-illiterate) and the administrator are different people.
On my desktop PC I will, for the foreseeable future, use a normal distro (ArchLinux in my case) but i am planing to look into changing my servers to immutable with docker. That could make updates/maintenance easier and reduce the risk for full server compromises
Well… Yes, Steam has a (very stupid in my eyes) policy of “if the developer puts up an update, then everyone must update” but that is not (fully) invalidating my point.
The content of the update and the time of release of the update is still outside of Steams responsibility. If the developer decides to push an update that uses some crazy stuff that works fine in Windows but would need some obscure codepath that are not available in Wine/Proton and by that rendering a game with a “Great on Deck” rating to “unplayable” then there is nothing Steam can do about it. Or if the developer patches in some DRM that will not run on Linux. Well, yes they could put up some lines in the terms of contracts for the developers to disallow this kind of changes but i am sure this would not end well at all.
Another thing, that most likely could even less be regulated, would be if the developer pushes an update that changes the UI to something that looks great on a huge screen but is unreadable on the SteamDeck.
Yes, all this would be way less an issue if Steam would make updates optional or would allow (an easy way) to choose the version. So i am totally on your side with that point.
Depends… The technician inside me asks: How big and heavy is the theoretical cow and can I get a huge spindle with a powerful motor?
I first read it as milking machine…
Modern games are ever changing, the Verified Status is only valid for the version of the game that was tested. Valve has no influence over the patches and changes to the game.
Zola really is great, I have started to work with it and it is so much easier to grasp and to get results with. Thanks a lot for pointing me to Zola!
The concept yes, the term for it (and the abbreviation) I am not sure.
Pennies per device can add up when hundreds of thousands of devices are produced. But it is not only the price of the storage but the whole circuit layout is simpler and therefore easier/faster to design and produce. That adds up too.
I will look into that too, thank you for the suggestion
A new homepage for the business of my wife.
I plan to use Hugo for it, I just wish the documentation would be better.
For the homepage I need a few additional “non-blog” pages and from the documentation I am not sure how to do that the best way.
But to be honest, I have not really looked deeper into that, so it is very possible that I just missed something.
I prefer to do both, a validation check to see if it has the general form of data I expect then parse what got successfully validated.
This way they only need RAM on the device and can get rid of the need for persistent storage/flash memory. Makes a much simpler board design and easier manufacturing with less costs for parts.
So efficient!! C-Level and shareholders love that!!
He just turns into a Zombie Process and keeps going