@deprecated_ii except the megacorps are mostly indeed releasing code according to the license. MIT would mean they don't have to, thus, 0 code contribution back
@coolboymew@shitposter.club tbh I think MIT license is more popular than GPLv3 in new projects (while older project likely to have GPLv2/3) hence the reason why they make that assumption with Rust rewrites. Interesting conspiracy theory though
@coolboymew@shitposter.club Yeah I know, although this seems more about the whole free software vs open source feud and license preferences on FOSS software than just Rust at this point.
@deprecated_ii@coolboymew there are companies doing it but i think it's more about getting sole control of the project so they can switch licenses at any time, they can't do it to linux kernel because there's no contribution copyright assignment, if you wanted to change the license you'd have to get buy-in from every single contributor.
nobody who's not disclosing source code is doing it you're right though lol, there isn't even conscious thought about vioating GPL for most companies they just use whatever a developer finds online and don't care. I have seen it many times.
@coolboymew@alex gnutards will find conspiracy theories everywhere. If you coded in C or C++ and any modern language you are probably all too well aware of the insane gap of QoL and bug surface between them. People wanted to toss out C++ 20 years ago and this only increased with time; there’s no conspiracy or corpo push needed for most of developers to jump onto a sensible replacement once it finally appeared. Many of those developers work at corps so corps jump on it too, no surprises there.
@coolboymew@Amikke@alex Where this conspiracy falls apart for me is that if they wanted to do license laundering, they have plenty of ways to do it already without resorting to "rewrite it in rust". So as much as it's a tempting pov, I feel like the two are more or less unrelated. (side note: the GPL family of licenses has failed in their stated objective, but that's another discussion for another day)
@deprecated_ii Years ago, I was tasked with checking the licenses of every library and framework we used on a project and find replacements for those that were under the GPL.
@deprecated_ii@josemanuel@coolboymew Nor is corporations abiding by GPL necessarily the Freedom Increasing outcome many advocates like to claim it is (see for example how Artifex and parts of Oracle have built their entire business model around copyright trolling with AGPLv3)
@coolboymew@Amikke@alex Because they've been looking for something like Rust for quite a while. Really, the whole "memory safe language without garbage collection" premise was enough to sell most corpos sight unseen, ditto with the fact that it was designed and marketed as a drop-in replacement for C++ with the backing of a large company and not as a pure research project. It's like saying Java is some huge conspiracy against FOSS because it came out in the 90s and there was a push to rewrite Everything in it. The reality is just more complicated I'm afraid.
@coolboymew@alex I was only talking about how unnecessary and therefore unlikely a conspiracy/intentional push is, the license flame war is a whole another can of worms.
But if I am to touch that topic I’m of the opinion that MIT-like licenses are the main contributor to the open source boom we witnessed in the past decade. You may not like it but day-job developers are the biggest workforce. Without GPL companies are actually willing to use open source projects and since maintaining a fork is more effort they do contribute back. In fact the claim that we get no contributions back is silly when for example the entire front-end ecosystem is driven by corp developers. (Which might be one of the reasons it’s so shit but that’s beside the point.) If gnutards had their way it basically wouldn’t exist and every company would be cooking up its own variant of shitty in-house frameworks.
MIT popularised open source incomparably better than a bunch of neckbeards unsuccessfully whining about freedom for decades at that point, and redirected a significant part of employed developers’ effort from in-house to open source and collaboration. That’s a huge win in my book.
A license that is trying to grab companies by the throat and force them to contribute is pointless without the means to actually grab them by the throat and force them to even accept it. Linux did it because it’s so huge and complex that developing an alternative in-house isn’t feasible. It’s an exception, not the rule.
@coolboymew@Amikke@alex And if it wasn't MINIX, they would have used some other RTOS. There really isn't much that actually gets prevented in the grand scheme of things, and the only way to a just and equitable scheme for software past the current status quo is copyright abolition.
@netdoll@deprecated_ii@josemanuel@coolboymew I think this is a little different, before there was a very cool C compiler, TCC, it could even compile a kernel quickly, on old hardware, now we have a raster that is not quite suitable for old hardware, because no one will rewrite the old drivers for x86 processors, or mips, they will most likely want to remove all backward compatibility for old computers, for example gnu-utils will be rewritten for raster, the old hardware will not receive gnu-utils updates, the old hardware will have the latest version in C as I understand this situation