To be fair, it’s entirely possible to make the same and very similar mistakes in Rust, too.

you can’t know that

I think that entire comment is actually incorrect. My understanding is that they did not “remove” any maintainers, but actually rejected patches from Russian citizens (because of their employer), and also removed some Russian names from the maintainers list who already have code in the kernel.

yikes.

That doesn’t invalidate my statement though.

freedom TO vs freedom FROM

I was more referring to mainline specifically, otherwise your chances of having many people actually benefit from your changes without a lot of effort is small IMO.

And here I am looking to move away from Linux after they started rejecting contributions for political reasons.

I still don’t think something so important should be beholden to the whims of one company (Linux Foundation) or their country’s laws (USA).

I would strongly prefer to use an operating system that didn’t have this problem. Do any even exist?

go against their spirit

I think this is more of a failure of the license itself. It’s not a good look to allow something explicitly and then go “no not like that!”

For professionals used to Photoshop, yes it is that bad. People want what’s familiar because they’re used to it and they’re busy or lazy. They don’t want to learn something new.

If GIMP wanted to increase their userbase by a million overnight, they would make it look more like Photoshop.

The problem is they and many current users are huge FOSS zealots and see this kind of thing akin to selling your soul to the devil.

except gaia is one of the largest forums on earth.

they have more subscribers than Apple TV+

xpra can do this

Not everyone wants to live in the terminal. I would argue most people don’t.

you might need a time machine for that

I think if Rust people want C and C++ devs to switch over, there needs to be a lot more documentation that’s easy to follow on how exactly to do that. For example with Swift there’s an amazing tutorial called Swift for C++ Practitioners that step-by-step goes over all the equivalent functionality and how to translate existing concepts over from one language to the other. I think Swift at least has the edge there with familiarity because the syntax physically looks closer to C-like languages, so when that’s not the case, even more hand-holding is going to be necessary IMO.

Please work on your Japanese.

落ち着いてください

I would use Ada or Spark in a heartbeat if there was an easy-to-use, mature cross-platform GUI library for it.

I think eventually if a federated system (or particular server) gets too popular they will just defederate from everyone else and perpetuate the same problem all over again