What's the difference? I rarely use Python and every time I do I have to relearn which tools are the go to ones. In Java it's a little simpler, we really just have Maven and Gradle. They have their own problems, sure, what tool doesn't, but the thing that annoys me about python is the quantity of tools. There often isn't a clear winner.
Now, to be fair to python, a lot of the ones mentioned on this post are very specifically for data science use cases and not general purpose development.
This is probably my biggest complaint about trying to learn Python past the beginner level and into intermediate and beyond. This is also one of my strongest arguments in favor of static type systems over dynamic ones.
It doesn't really roll off the tongue, I get it, but it's the best and most widely used term for software whose source is available to view but not modify and/or redistribute.
CC0 is awful for code. I didn't understand why until reading this https://lists.opensource.org/pipermail/license-review_lists.opensource.org/2012-February/001431.html (you can click the thread button to see the full thread as well).
https://creativecommons.org/publicdomain/zero/1.0/legalcode.en#limitations
No trademark or patent rights held by Affirmer are waived, abandoned, surrendered, licensed or otherwise affected by this document.
The only license/declaration approved by both the FSF and OSI for putting something into the public domain while having a permissive fallback license (for jurisdictions without public domain) is the Unlicense. If you know of others please let me know.
Fuck the OSI. They've done more harm to free software than any other organization. In the recent controversy with redis and SSPL, they refused to acknowledge the actual problem of the SSPL license, that it was unusable due to requiring all "software used to deploy this software" being open source. Does that mean that people who deploy software on Windows have to cough up the source code for Windows? What about Intel Management Engine, the proprietary bit of code in every single Intel CPU. Redis moved to a dual license with that a proprietary license. An unusable license... and a proprietary license = proprietary software. But instead, the OSI whined that the problems with the SSPL was that it would "restrict usage" because people have to share more source code. The OSI, and open source, have always been corporate entities that unsurp free software. Just look at their sponsors page and see who supports them: Amazon, Google, Intel, Microsoft...
I'd disagree with you there somewhat. It was all discussed in the mailing list. https://lists.opensource.org/pipermail/license-review_lists.opensource.org/2018-October/thread.html#3603
I've dug through this and the discussion for SSPLv2 a bit because I used to disagree with their decision. The criticism is that it accomplishes the alleged goal of discrimination against SaaS providers specifically by doing what you're saying.
I'll check my notes some more, I could've sworn I had a link to an email specifically saying as much but I can't find it right now. I'll poke around and see if I can find it.
Didn't realize you were the same user, I would've used different words so it didn't feel like I was trying to reopen an argument or something. My mistake, friend. ❤️ I mean that genuinely. I hope you don't view me as some thread hopping flame lord about this topic.
Edit: Wait, I wasn't replying to you lol. My point still applies though.
As long as we don't call them free, libre, or open source I don't care. We shouldn't make the terminology any more confusing for those.
@JackbyDev
@programming.dev