because they haven’t? We don’t want any changes to our ability to install software. This would still kill f-droid, and the “flow” they talked about isn’t a system wide setting. You have to do it per app. And you, the owner of the divice who just wants to install something on your device, would have to register. So if too many people install the app, the dev would be forced to register as well.

How is any of that “listening to user feedback”?

as a beginner, this was what made me move away from ubuntu years ago. And something wrong will sometimes end up with you messing up your system. Ubuntu just isn’t a good beginner’s distro anymore.

everyone’s adopting it because they’re forced to. And shut up with your “but you can use X”, some distros literally plan to drop support for it entirely.

that’s the thing… wayland has repeatedly said they will not reach feature parity. So from the word “until” onwards cad be deleted, back to the older comment

you mean 365 cloud pc?

“these new cars have a teeny tiny fuel tank with a tiny range! They used to have a bigger tank!”

“Drive an old car”

In this case the new car is objectively inferior, and I can’t buy a new old car anymore.

When something complains about very real problems due to missing functionality, the proper answer isn’t “fuck you, use the old stuff, or stop yearning for the functionality that te intentionally crippled”

eh, the lots of info thing cuts both ways. You’ll find a Lot of outdated advice

I am not referring to it being a drop-in replacement. I’m referring to the fact that there are multiple supposedly-interoperable-but-not-really non-drop-in replacements is the problem. And it does affect the end user if devs find it difficult to adopt (as many do).

Wayland is designed for ease of development for wayland designers. “We’re just a protocol, the coding is left to anyone else” is the easiest way to write code. Because they decided not to write any at all.

well that’s the problem. “I don’t use it therefore it must be a bad idea”

see that’s the problem. Everyone’s first response is that it’s a niche problem. For every complaint. So what? It’s a new problem is the point, however niche.

Btw, this is not a niche problem. Some big projects have explicitly said they have had this very problem

is it ddr4?

it will be refused in the name of security. Which is notreally a good argument. “it rather involved being on the other side of that airtight hatchway” type of thing

I am not better served. I am now in the quite new position where I’d have to rewrite some of my own personal software if i simply just decided to change DE

missing feature that used to be there but has been removed in the name of protecting me from myself, is an inability to customize.

speakers are analog devices by nature.

The other two are used for the distortions they introduce, so quite literally lower fidelity. Whether some people like those distortions is irrelevant.

You want high fidelity: lossless digital audio formats.

what audio tech uses analog for better fidelity?

at least two, you can’t stuff a rocket full of just gpus, you need something to actually dock and deliver the payload in space. So you need to launch at least 2 rockets (in a non-reusable configuration, so you need to pay for the whole rocket and the launch) to ship a bunch of gpus that are, at best, only 10% as fast as usual.

they did think of it. lots of people have. I just mentioned what was required. Rad hardened processors are usually 10 to 20 times slower than what we have on the surface

and the infrastructure and robotics to replace them, of course.

Assuming 200 nvidia H100 failures a day (conservativo, reality is worse) that’s an extra ~340kg of weight you’d need to launch per day. Which is an extra 120 tons yearly.

and forget about running 4nm chips in space. shit has to be radiation hardened, which means bigger process nodes and higher energy cost, and lower speed