so you’re saying it is the wrong word, because most apks are downloaded from the internet on-device. That is not a local transfer

but that’s steam, not linux.

it’s impossible for that to exist. First you have convince tle linux community toagree to one (1, uno, more than zero but less than two) runtime environment. And then to keep it backwards compatible. Because “you just need to recompile it” doesn’t work for this (or ever, really, if you want something to keep working)

what if it’s poinsoned data, and i instruct you not to crawl it, but you do it anyway. Whose fault is it then?

arch v debian?

LESS CHOICE!

Choice is only exciting for us techheads. Too much of it actively harms adoption.

and they just dropped support for pascal :/

even when said “one program” is actually 69 (nice) different binaries

he literally said it was not one of the features cherry picked to be reimplemented. So he did say, paraphrased, “because we couldn’t be bothered”

the reason is literally “because we decided not to implement it”

Saved you a click.

i installed mandrake in 2004. It came with a nice graphical installer.

doesn’t change anything if you can’t avoid having to write the unsafe parts

you seem to be confusing an operating system for the user interface. An os can (and regularly does) have more than one interface. In this case steamos ships with two of them. One they designed which is targeted for games. And they also ship plasma as a desktop environment for those who need it. The operating system lies under all that, and you can launch any piece of software from either of the interfaces. (or the terminal, that counts as a 3rd way to interact with the computer, I guess)

as amazing as snake was as a toy on phones, it still doesn’t make sense to put a copy of snake in outlook. Or notepad, or paint, or office, or as an always available widget in the task bar

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”?

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

“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”

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”