snabelen.no is one of the many independent Mastodon servers you can use to participate in the fediverse.
Ein norsk heimstad for den desentraliserte mikroblogge-plattformen.

Administrert av:

Serverstatistikk:

451
aktive brukere

Thor A. Hopland

Watching a video that makes a bad case against - so here I go.

I don't care if you run like and , because certain software is so huge and complex that it requires return on investment.

There's also something to be said for and licenses in general software, even.

But when it comes to the fundamental software you run, like kernel or essential userland commands, it's gotta be - if not some other license. Why?

means "power to the user". That is certain expectations are expected of companies and organizations that partake in the code, and those expectations are levied in the users interests.

That is you are expected to contribute back improvements and not put them behind a paywall. This makes is anti by default.

There are plenty of companies that try to slip one by, but in the fundamental software that's in all of our computers? That's historically a bad idea.

The first time really rubbed me the wrong way wasn't , but .

Back back in the days, when Jesus rode dinosaurs into Jerusalem, there was still a dispute about which new standard was going to be adopted.

was in planning stage then and Canonical was fighting against it for no other reason than "not invented here".

There I was, with an union tired around my belt, seeing that the license was - with an agreement that could "relicense" your code... wat?!

Now is going to replace ? Not trusting that one bit.

The core utilities of any given , as well as the kernel, display protocol, etc, etc, etc should NEVER be up to like or .

For total power to the user, the fundamental technological stack should be , because we should have expectations towards vendors.

This is also from the system that brought you . wants a and it shows.