There was a time when the people who complained about soldered RAM (and I was one of those people) were a significant enough proportion of the community that manufacturers would pay attention. This was the age when gaming PCs were constructed from high end pieces from the wild-assed cases to the heavy duty PSUs to overclocked CPUs and next gen GPUs.

But overall, that segment of the consumer market has dwindled. Most folks just want to charge their new machine up, connect it to their WiFi network and get going. On the corporate end of things, save for pretty niche areas like engineering and R&D, a cube you can plug a keyboard, mouse and camera into and will last through a few upgrade cycles before it's sold back to a refurb outfit is all that is needed. Nobody in IT departments is pulling RAM chips anymore, particularly at RAM prices right now! Even the folks writing operating systems are starting to get it, and have rediscovered the glory of native apps that don't required bloated Javascript engines just to select a few radio buttons.

Yes, Windows 11 is really that bad. It's cluttered, slow, inconsistent. I've seen it on pretty high end hardware, and it's a dog. And that's before we even talk about how they tried to insert Copilot into everything. It's a shitty version of Windows and even Redmond acknowledges it. It was the impending EOL of Windows 10 that lead me to buy an M1 MacBook Pro, and I've never looked back. If I want to run Linux, I've got servers set up to do that kind of heavy lifting, but I have absolutely no need for whatever it is MS is trying to sell me these days.

Still, Slashdot doesn't have to play along with their weasel wording. For example, "ergonomic collars that deliver an electric pulse" - just say "shock collar". Don't help them whitewash what they're talking about.

This is a valid retort. But let us not think that lawyers are struggling: once they get to be a "partner" in a firm they are likely making $1 million/year. And the entire context of the discussion is that they aren't relying on staff like they used to. Back in 1980, a lawyer had staff members who ran down to the court house to get documents, bring them back, photocopy them, staple them, file them, make phone calls. Now all of that is 100% automated, plus now they have AI.

I'm not sure the legal overhead is quite what it used to be.

Disclaimers like this apply to Excel, TurboTax, GCC, ChatGPT, and more: The user is ultimately responsible for the application. The manufacturers always disclaim responsibility.

You can get companies to stand behind products and accept liability or sign a Business Associate Agreement - but you are going to have to put it in a contract and pay extra for it. This is why the product you buy at Home Depot and the one the government/military/NASA buys has a very big price difference even if it is the exact same part.

Every industry does this.

From Housing inspectors and plumbers, to software products - it is super common. I just had plumber put this into their contract for replacing a cast-iron drain with PVC. Then I had the tub reglazed and they did the same thing. There are often two prices, based on if you want a guarantee behind it or not. I paid a structural engineer to inspect the foundation of my prior to purchase. While he said the cracks were normal setting, the price was $200 for the inspection + verbal assessment, or $600 to put it in writing and stand behind it. In the last two weeks I've gotten this same thing from a tax preparer and a property attorney. Free advice from the tax preparer, but if we want him to file it and sign it there was a price. The attorney told me what to say in court, but quoted me a price to put it on his letterhead or to show up and say it.

1. Raw work: 8 hours
2. Work with unchecked AI: 8 minutes
3. Work with check AI: 16 minutes

I don't get why people choose option 2 over option 3.

They stocker making $15/hour needs to work extra hours to survive. Why does the lawyer making $500/hour overwork?

You're confusing the importance of avoiding Kessler syndrome in LEO with the difficulty of causing Kessler syndrome. GEO debris can potentially remain there for millions of years before interactions between the gravitational pull of the Sun, Earth, and Moon sufficiently perturb it. LEO debris remains for weeks to months. You have to have many orders of magnitude more debris in LEO to trigger Kessler Syndrome, where the rate of collisions exceeds the rate of debris loss.

The fact that a LEO Kessler Syndrome would also be short is something that exists on top of that.

It's also worth nothing that not only are modern satellites not only vastly better at properly disposing of themselves than they were in the 1970s when Kessler Syndrome was proposed, but they're also vastly better at avoiding debris strikes. All of these factors are multiplicative together.

Lol, I was thinking of this instead ;)

People forget that the primary concerns about Kessler Syndrome were about geosynchronous orbit, which used to be where all the most important satellites went (many of course still go there, but not the megaconstellations). It takes a long, long time for debris to leave GEO. But LEO is a very different beast.

They said it's internal rather than a collision, so probably a failed COPV would be my guess.

Yeah. In particular:

with fragments likely to fall to Earth over the next few weeks

LEO FTW. Kessler Syndrome is primarily a risk if you put too much stuff with too poor of an end-of-life disposal rate in GEO. End-of-life without proper disposal rates have declined exponentially since Kessler Syndrome was first proposed (manufacturers both understand the importance more, and do a better job, of decreasing the rate of failures before deorbit - in the past, sometimes there wasn't even attempts to dispose of a craft at end-of-life). And now we're increasingly putting stuff in LEO, where debris falls out of orbit relatively quickly. It's not impossible in LEO, esp. with higher LEO orbits - but it's much more difficult.

Or to put it another way: fragments can't build up to hit other things if they're gone after just a couple weeks.

And this trend is likely to continue - a lower percentage of premature failures, and decreasing altitudes / reentry times. Concerning ever-decreasing altitudes, we've already been doing this via use of ion engines to provide more reboost (with mission lifespans designed for only several years before running out of propellant, instead of decades like the giant GEO ones), but there's an increasing interest in "sky skimming" satellites that function in a way somewhat reminiscent of a ramjet - instead of krypton or xenon as the propellant for an ion engine, the sparse atmospheric air itself is the propellant, so the craft can in effect fly indefinitely until it fails, wherein it quite rapidly enters the denser atmosphere and burns up.

ED: "But it doesn't work for gravity with linear curvature"

Relativity = gravity is represented by the curvature of spacetime. Curvature is linear, R. The formula treats curvature linearly. As things get closer and curvature spikes, the math just scales at a 1:1 rate

Quadratic gravity = Squares the curvature. Doesn't really change things much when everything is far apart, but heavily changes things when everything is close together.

Pros: prevents infinities and other problems when trying to reconcile quantum theory with relativity ("makes the theory renormalizable"). E.g. you don't want to calculate "if I add up the probabilities of all of these possible routes to some specific event, what are the odds that it happens?" -> "Infinity percent odds". That's... a problem. Renormalization is a trick for electromagnetism that prevents this by letting the infinities cancel out. But it doesn't work with linear curvature - gravitons carry energy, which creates gravity, which carries more energy... it explodes, and renormalization attempts just create new infinities. But it does work with quadratic curvature - it weakens high-energy interactions and allows for convergence.

Cons: Creates "ghosts" (particles with negative energies or negative probabilities, which create their own problems). There's various proposed solutions, but none that's really a "eureka!" moment. Generally along the lines of "they exist but are purely virtual and don't interact", "they exist but they're so massive that they decay before they can interact with the universe", "they don't exist, we're just using the math out of bounds and need a different representation of the same", "If we don't stop at R^2 but also add in R^3, R^4, ... on to infinity, then they go away". Etc.

The theory isn't new, BTW. The idea is from 1918 (just a few years after Einstein's theory of General Relativity was published), and the work that led to the "Pros" above is from 1977.

In short, Java was invented for a reason, and while it has become a victim of legacy cruft as well, the underlying concept of truly portable apps, with a minimum of fuss to jump from platform to platform, still ought to be the preferable path. The problem is that that true platform neutrality/ambiguity pretty much kills Microsoft in all but a few niches, like gaming, but only because hardware vendors put less effort into drivers for other operating systems.

Yes, Office is still king, although I think that crown is beginning to slip, and it may end up being Excel, with its large list of features, that may last the longest. But it isn't 1990, or even 2000 anymore. Developers have multiple ways of developing portable applications, and while MS may (for the nth time) update or swap out its toolchains, the real question is will developers really care?