Luddites weren’t against new technology, they were against the aristocrats using new technology as a tool or excuse to oppress and kill the labor class. The problem is not the new technology, the problem is that people were dying of hunger and being laid off in droves. Destroying the machinery, which almost always they were the operators of when working on said aristocrat’s factories, was an act of protest, just like a riot, or a strike. It was a form of collective bargaining.

You assume most stock investors read beyond the headline, you assume wrong.

Well, you see, that’s the really hard part of LLMs. Getting good results is a direct function of the size of the model. The bigger the model, the more effective it can be at its task. However, there’s something called compute efficient frontier (technical but neatly explained video about it). Basically you can’t make a model more effective at their computations beyond said linear boundary for any given size. The only way to make a model better, is to make it larger (what most mega corps have been doing) or radically change the algorithms and method underlying the model. But the latter has been proving to be extraordinarily hard. Mostly because to understand what is going on inside the model you need to think in rather abstract and esoteric mathematical principles that bend your mind backwards. You can compress an already trained model to run on smaller hardware. But to train them, you still need the humongously large datasets and power hungry processing. This is compounded by the fact that larger and larger models are ever more expensive while providing rapidly diminishing returns. Oh, and we are quickly running out of quality usable data, so shoveling more data after a certain point starts to actually provide worse results unless you dedicate thousands of hours of human labor producing, collecting and cleaning the new data. That’s all even before you have to address data poisoning, where previously LLM generated data is fed back to train a model but it is very hard to prevent it from devolving into incoherence after a couple of generations.

This part of Twitter

Replacing garbage with sewer water. Not exactly an improvement.

Bazzite comes with wine all setup by default. KDE’s file managerl can integrate running exe with wine on a default prefix automatically.

Most distributions and DEs already package wine in a set it and forget it configuration. Wine by default has a system wide prefix such that clicking on any exe in the file system automatically runs it on the default prefix. This way of doing things predates wsl by a long time. It is just safer and better practice to setup a new prefix for every software, specially if they are games.

Some linux installers will refuse to erase the bitlocker partition automatically. Then you have to manually erase it before running the installer.

My biggest fear is that so far Nvidia has a track record of introducing regressions and new bugs with each new driver version. Just a week ago all my flatpaks weren’t working on Wayland, again. It happens almost with every single update. Some games that are native or platinum randomly stop working and it takes several updates before they start working again. While on AMD everything just works all the time and regressions are solved in a day not weeks. It’s just annoying.

If gaming is top priority. Go all amd, disregard Nvidia. AMD has extraordinary linux support and if it runs on the steam deck it will run on any all AMD machine.

Always remember to disable secureboot and remove bitlocker before installing linux on a oem windows machine. They make it hell to remove that malware from newer machines.

By the third patent: Elden Ring, WoW, Everquest, Neverwinter, SW: The Old Republic, Final Fantasy, and many many others have infringed Nintendo patents. Fuck Nintendo.

Please remember that no one is taking anything away from you. If you don’t like it, you don’t have to use it. Traditional package managing isn’t going away any time soon. You are safe. Others can have their preferred tech, and you don’t have to like it. It’s ok to have different tastes.

It’s not a flaw. Ostree is a last resort, you should be using containerized software. Layering a package should only be done when strictly necessary and not as the regular way to manage packages. If you need an overtly customized system, you use Nix or universal blue to design your new system declaratively and create your custom image.

Then just install KDE in your Arch install. Or use endeavorOS with KDE, or any other Arch based OS with KDE. Don’t be dismissive of other people’s interests.

Settings live in user space. Software exist in containers like AppImage, Flatpak or Distrobox. If something need deep system integration, they can be layered on top of the system in the user layer. Immutable does NOT mean less control. Just exerting control over the system in a different, usually more systematic, automatic and deterministic way.

your base distro is immutable, then any extra changes go on an additional mutable layer

That is exactly how OsTree and other layering solutions work. Only Nix requires a whole distro rebuild.

There’s KDE Neon already. The whole point of this distribution is the atomic immutable part.

Maybe they’ll fix the sddm custom theming? It’s currently broken on all immutables and doesn’t allow custom themes.

On Mint, you troubleshoot the wifi antenna following a guide once and then you’re done. On Bazzite you probably just needed to click to change to X11 instead of plain Plasma, on the login screen. I would bet money that you have an Nvidia GPU. Sometimes Nvidia breaks the drivers support on Wayland. They intentionally neglect it in order to keep your kind of mentality around.

On Windows, MS is going to eventually fix the workarounds so you can’t update your computer anymore.