In terms of algorithms, nothing. But you were the one who mentioned algorithms. I am speaking of code in general. I do want for persons to contribute back to the community if they use community sourced code. I don’t think we can trust corporations to be altruistic.

This all being said in your earlier message you were implying it’s all about ego. I was just saying it is not about ego.

For me it’s all about community resources and societal enrichment.

CC0 vs CC-SA is actually a really good (rough) analogy.

Sure. Very briefly. These are all open source licenses which (roughly) means the source is freely viewable and changeable. But the specific differences are:

• MIT/BSD - Anyone can take the code and do whatever they want, if they start with your code, improve it then make it proprietary there is nothing you can do.

• GPL - If someone makes changes to your code and improves it they have to make it available for use by the community too IF and only if they distribute the binary.

• AGPL - Like GPL except that even if they are running the code on their server and not sharing it they still have to give back improvements.

• MPL 2.0 - Like GPL but limited to specific files. This is useful for things like statically linked code. I don’t often recommend this but it can be needed for static only code bases like rust. Proprietary software can link with this and not be covered by the copyleft share alike stuff.

• LGPL - Like the GPL but for dynamically linked libraries. Proprietary software can link with this and not be covered by the copyleft share alike stuff.

• SSPL - Like AGPL but technically even more intense. If you use SSPL you must open source all the tooling you use to manage that hosted SSPL license. Any tools to make sure the SSPL software is running well or to set it up must also be open sourced.

The OSI technically does not say the SSPL is “open source” but given that they recently admitted that they regret defining the AGPL as open source I think the OSI might be showing a bit of corporate bias.

Pull requests have nothing to do with any of this. Also algorithms can’t be copyrighted nor patterned in the first place so it would not matter.

You could implant an algorithm in a proprietary code base and some gal could reverse engineer it and publish it as GPL or MIT or whatever and all would be a-ok.

Wait, so because a few execs violated the GPL and threw their employees under the bus, we should abandon copyleft entirely? That’s like ditching locks just because burglars exist. Companies that want to exploit software will do so, BSD or not. The GPL didn’t land those four guys in prison; their higher-ups did. Giving up and saying “ok big corp I’ll just do what you want“ just makes it even easier for corporations to profit at societies expense.

MIT and BSD software licenses might as well be renamed to “I love big daddy companies and trust them 100% uwu”

There is no reason not to choose GPL/AGPL/MPL 2.0/LGPL/SSPL if you are writing open source code.

MIT and BSD just let companies enrich themselves at societies expense.

Helix + the appropriate set of LSPs.

It’s like neo vim without the need the manage plugins. That and it uses select -> action instead of vim style action -> select, which makes more sense to me.

Supper happy with lemmy.word

You can actually have a conversation there without the whole thing being taken over by people who write like they are edgy 14 year old American tankies.

Civ 6 should perform quite well on your new CPU.

Also strong recommend for Satisfactory.

But that’s not a no.