He fought a young competitive boxer once and lost so awfully he never tried again. His career is entirely based on beating up geriatric boxers. He is not out there boxing sub 16 kids because they won’t let him. He would definitely punch kids in the face if allowed to.
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.
Replacing garbage with sewer water. Not exactly an improvement.
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.
I think it was part of the story that some group had already broken into the tomb but got wiped out by the traps. You’re looting their equipment. You even fight them in between puzzles.
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.
How is having to apply workarounds to keep windows working on old machines any different from troubleshooting the occasional linux issue? It’s a rethorical question, the difference is that the workaround on Windows is mandatory while the Linux troubleshoot is nowadays rare and usually related to edge cases.
Some of the workarounds in this article are far more involved and convoluted than what I’ve ever had to do in 15 years of linux. Some are even dangerous for system stability and security. My very recent install of bazzite in a new laptop has been a perfectly out of the box it just works experience. Not even having to open the terminal. 100% friendly GUI without compromising flexibility, power and customizability. Today, suggesting linux with a solid desktop environment like KDE plasma is just foolproof. The end user will be using exactly the same knowledge and habits of Windows, without the harassment machine that is MS now. The change is not learning a new OS, is just switching a few assumptions on how some advanced things work.
If this were done by MS or Apple, who lack any shred of respect left, sure. If it were a material change on how the code works, certainly it would be most concerning. But what happened was blown entirely out of proportion for who Bitwarden has been and how they’ve acted in the past. They are still ethically very solid. And it was an immaterial change in the build tools, that could very well have been neglectful or accidental.
That’s a poor understanding of the situation. Nothing in the licensing changed. The SDK has always been the proprietary business to business secrets management product. The client integrates with and can use that SDK to provide the paid service to businesses. The client and the server side management of password has always been and still is FOSS.
This was apparently an accidental change in the build code (not the client code, just the building scripts) that required the inclusion of the SDK to build the client when actually it has never and doesn’t really need any of that code. It prevented building the client without accepting the SDK license. Which it shouldn’t.
This was fixed and some things will be put in place so it doesn’t happen again. Nothing in the licensing scheme changed, at all. This is not a catastrophic enshittification event. A Dev was just being lazy and forgot to check the dependencies on the build chain before their commit.
Firefox has all those things already (albeit vertical tabs are experimental still). Just without the AI marketing and the built-in identity theft.
Surely the former because at least clowns try to be funny and entertaining.
Oh no, orbit is actually quite hostile. Specially unexpected torque forces from spinning in unplanned ways. And there’s very little but definitely present atmospheric drag. Not so much from the density of the air but from the extremely high speed it’s moving. Then there’s orbital debris. Also extreme and fast changes in temperature from the sun. Not to forget cosmic radiation.
The SDK was never FOSS, and was never under the GPL. Hence why they can add the text mentioned in the article. You don’t get to change the text of a FOSS license to begin with. It isn’t unheard of for text like this to be part of proprietary software that integrates with and uses FOSS that are under different licenses.
That said, this is concerning, but whether it changes BW’s FOSS state is a matter of legal bickering that has been going on for decades.
Most likely, as with all AI as a service startups. After a certain mass of users the models can’t keep up. So to reduce the response times they pay offshore firms to have real people answer the chat. Unfortunately, doctors willing to answer a chat all day are way less numerous than cheap labor.