61–70 of 354 posts
> Visual Studio Code (VS Code) no longer works with derivative products such as VS Codium [..] They seem to have this backward. Visual Studio Code is a derivative product of VS Codium.
> This is a repository of scripts to automatically build Microsoft's vscode repository into freely-licensed binaries with a community-driven default configuration.
It's licensed under MIT + VS Marketplace Terms: https://github.com/microsoft/vscode-cpptools?tab=License-1-o...
If you fork it and don't use VS Marketplace, it's only MIT. Or am I missing something?
> Visual Studio Code (VS Code) no longer works with derivative products such as VS Codium [..] They seem to have this backward. Visual Studio Code is a derivative product of VS Codium.
Earlier quoted context omitted.
Anything that’s not gpl-licensed is going to pull the rug from under your feet, people should have learned this by now. Also, if you do open source contributions, never ever agree to assign copyright to the project: doing so means the project owners can relicense the code base, even towards proprietary license.
FreeBSD must be pulling a very long con, then.
Half of the initial mac os x kernel was ripped off freebsd, giving pretty much nothing back.
Afaik netapp is also basing their system on bsd.
Sony uses freebsd as the OS for their playstation.
And many more, giving essentially nothing back.
How is it not open-source? It's licensed under MIT + VS Marketplace Terms: https://github.com/microsoft/vscode-cpptools?tab=License-1-o... If you fork it and don't use VS Marketplace, it's only MIT. Or am I missing something?
Earlier quoted context omitted.
Anything that’s not gpl-licensed is going to pull the rug from under your feet, people should have learned this by now. Also, if you do open source contributions, never ever agree to assign copyright to the project: doing so means the project owners can relicense the code base, even towards proprietary license.
Absolutely. I signed one copyright assignment, ever, with the FSF. I trust them enough to do that, but they're just about the only ones.
> Visual Studio Code (VS Code) no longer works with derivative products such as VS Codium [..] They seem to have this backward. Visual Studio Code is a derivative product of VS Codium.
No VS Codium is just a alternative build of Visual Studio Code. > This is a repository of scripts to automatically build Microsoft's vscode repository into freely-licensed binaries with a community-driven default configuration. https://github.com/VSCodium/vscodium
Earlier quoted context omitted.
Anything that’s not gpl-licensed is going to pull the rug from under your feet, people should have learned this by now. Also, if you do open source contributions, never ever agree to assign copyright to the project: doing so means the project owners can relicense the code base, even towards proprietary license.
FreeBSD must be pulling a very long con, then.
I think project governance matters more than license, and the BSDs are great examples.
Having said that, I’ve soured on the GPL. V3 more-or-less bans companies from selling you hardware that runs free software, but lets Google, Meta, etc use the software to expand their cloud-based monopolies where surveillance capitalism and enshittification have won out.
AGPL or BSL seem much better if you want free as in freedom. BSD and Apache at least don’t force your software off of machines that end users control.
Yes, BSL is not open (TM) or free (TM) or whatever. It’s still better IMHO, since it at least has some path to revenue for the developers.