The obstacle is supposed to be there and is supposed to be respected as an implicit order. Getting around it without extremely explicit instructions is an alignment problem.

> Normal computer means a choice of OS to run on it without having to hack it to do that job.

That's too high a standard. When we consider MacOS along with Windows and Linux, there are basically no computers that let you freely choose between all three without hacks.

And even just considering Windows and Linux, a big chunk of the laptop market only supports Windows properly.

A laptop that runs any normal desktop OS is a normal computer.

I'm surprised you want to run real CAD software on a netbook. I think your use case is pretty unusual.

Also drivers are often better on Linux.

tbh I suspect it would be just fine. even the really cheap ones tend to have at least a few gigabytes of RAM.

> There are tradeoffs, suggesting "shut down your website unless you provide access everywhere" is worse on all fronts for everyone.

Maybe, maybe not.

If block-heavy websites shut down entirely, we lose some content, but other content moves to block-minimal sites and the average user might be able to access more.

Also if there's no blocking crutch, and people get pushed into shutdown and are mad about it, they might fight harder for anti-spam technology and legal enforcement, which could improve the situation.

I managed to solve my scraper problems without optimizing much, but if I had to optimize I think the only option might be "don't use mediawiki" and that's an extremely obnoxious solution. Though maybe I could get there by throttling specific kinds of pages.

Please read their last sentence again and think about how much it understates the difference between stack overflow in its prime and a normal website. Also the "much of which still needs to be done".

> Because safe code isn't fast enough to decode live video.

I strongly doubt that.

And if any implementation of AV2 can be "fast enough", then there should be no question at all that we can write "fast enough" safe decoders for every other codec. Absolutely no way safe code is inherently that much slower.

What makes you think that would use less resources?

And it's not really hardware hitting limits, it's specifically software decoding on somewhat weaker machines.

It could help in the same way that running things in a shader uses less resources than running it on CPU. You're flattening the pipeline, and you can optimize better with simpler primitives and less branches.

More reason to never use the builtin stuff in a tv. Cheap sticks can handle decoding fine.

> If you license something under GPL, that necessarily means you’re okay with people making local changes and not sharing them. If you aren’t okay with that, then don’t use the GPL.

GPL has always meant you're okay with someone making local changes for their own internal use.

When it comes to servers, someone making a project this decade that uses GPL might be signalling they're okay with server code staying closed source. Or it might be other reasons, like the uncertainty over what code is covered by AGPL. And if a project is older, there's an increasing chance they didn't expect the current ecosystem and hate that the code is being used this way.