This is most definitely an LLM problem and a marketing problem combined, but it is all rooted in the LLM problem. Just where do you think the LLM gets its useful information? And how useful do you think the LLM would be without the underlying websites used to feed it?

Put down the Crack pipe.

That won't happen any more than it does now. Look at what happened during the Covid lockdown. Trillions of addtional dollars were pumped into the economy, and the end result was a staggering inflation spiral. That had a short-term benefit to the super poor, but they were soon in the exact same situation they were in before the stimulus. That happens for many reasons, but the end result is that giving money to people will cause as many, if not more, problems than existed prior to the giveaway.

It would help nothing. The super-rich would still be super-rich, and the super-poor would still be super-poor. Universal basic income has absolutely zero chance of ever working in a free society. Every time the government pumps more money into the economy, prices rise to compensate for it. The end result will always be economic harm to everyone who isn't already wealthy.

NAT didn't kill IPv6. Corrupt government officials killed IPv6. Our governments collude with large ISP's to keep the gravy flowing with the obsolete IPv4. There is LOTS of money to be made for maintaining the artificially scarce IPv4 addresses.

It is the current owners that decided to buy property that is guaranteed to flood. Even in tornado country, the property is very unlikely to be destroyed in a tornado. But flood plains are guaranteed to flood.

The last system I had that couldn't sleep is my current Linux build with a Gigabyte motherboard that is notorious (I discovered after-the-fact) for not sleeping under Linux. There is no known cure, and it seems to have been the case for 20+ years. My prior system, which had the same NVidia graphics card, slept and resumed every day just fine for months on end. I will never buy another Gigabyte motherboard.

A reusable set of libraries to kickstart new development is enough to qualify as a basic framework.

I have run my own email server for about 20 years now, and I have over 500 email address aliases; a unique one for everyone I have ever emailed. Whenever I start getting spam on one, I know exactly which service was compromised without having to go to haveibeenpwned (it seems like most online services have been compromised). I can disable the email address and create a new one at will (or I just live with it).

Most are bloated, but some are not. When I was doing Assembly on the 6809 in the 1980s, I wrote a framework that contained everything I used in most of my programs (printing to the screen, letting the user input a line of text, printing to the dot-matrix printer, modem file transfers, saving and loading files, etc). My assembled projects were quite small (usually around 20-25 kilobytes when finished). I did not include anything just for the hell of it, and my framework saved me tons of time on subsequent projects.

Fast forward to about 12 years ago, when I started creating a Web programming framework for my own use. The framework is about 50K lines of PHP code (including comments and whitespace). It does include some dead code bloat, as it originated from a project I was writing for a specific project (which is easily trimmable if I ever get around to it). Barring that project-specific code, though, I would have to rewrite the vast majority of the framework for each Web project, so it is actually rather trim around the waist. It easily saves me years-worth of man hours on each project, and each project uses about 95% of the framework.

But most modern frameworks are indeed bloated all to hell with no justifiable reason. And the reason is probably because they want to do everything for everyone, which always results in a bloated pig. But frameworks that target a specific need can be lean and efficient.

And the auction (with bids starting at $100K) should have only earned the company's H1B hire an interview to prove his worthiness for the position.

It's the exact same transformation as placing a book on the surface of a copying machine and pressing Copy. That is the only transformation done by LLMs. It's a copy, and the judge is entirely wrong. Sometimes he gets it (like he did in the Oracle case), and sometimes the bullshit machine runs him over (like it does with LLMs).

It is a certainty that this sane judge's ruling will be overturned, as the U.S. Supreme Taliban has already ruled this particular law to be Constitutional. That's why this insanity is spreading throughout the Taliban-controlled U.S.

I'm going to piss off a lot of people, but I don't care. The first steps are:

1) Get rid of RPM. Red Hat created it because they saw Debian and wondered how they could fuck it up. RPM was the result. Standardize on the Debian format.
2) Get rid of GNOME. GNOME was created because someone didn't think the QPL was Free enough. The result was possibly the worst desktop in existence.
3) Improve the deb format to be per-user friendly. Developers currently can't automate the installation of a desktop icon on a user's desktop because all packages are installed as root. This is a fairly simple problem with large repercussions.
4) Abandon SNAPS, AppImage, etc. They don't work as advertised, and can only work if they package an entire operating system in each application.

That should solve many of the problems with minimal pain.

AppImage has proven itself to be a huge disappointment, and I suspect the same holds true for the others as well. I was running Kdenlive on Kubuntu 20.04, and there were must-have features in a newer Kdenlive that required a newer Kubuntu, so I downloaded the last AppImage of the Kdenlive I needed.

When I tried to run the AppImage, it failed with a GLIBC dependency error. That, for me, completely killed the whole notion of AppImage, SNAP, and all the others. They need the entire dependency chain (essentially the entire operating) included in each package, or something will fail.

We can thank Red Hat for this entire packaging clusterfuck, naturally. If they had just adopted the Debian format, 99% of current packaging issues would never have existed. But they saw a good think and thought, "I wonder how we can destroy this awesome user-centric advance. Ooh! I know!" Hence, RPM was born, and the Linux world became a decidedly worse place.