Re:Why Wolfram tech isn’t open source (2019)
by detaro on Saturday December 18, 2021 @10:57AM
(#29605407)
Source available is specifically if the code is not under an open source license. Whereas software that is under an OS license is open source, whatever the maintainers policy on contributions.
Re:Why Wolfram tech isn’t open source (2019)
by leeoniya on Saturday December 18, 2021 @11:07AM
(#29605512)
ah, you're right. i missed that.
Re:Why Wolfram tech isn’t open source (2019)
by rwmj on Saturday December 18, 2021 @10:58AM
(#29605409)
Not necessarily. There are some true open source projects where the development model is some company "throwing code over the wall". Often they don't make it easy or even possible for anyone outside the company to contribute, they don't have an open repository or bug tracker, release only periodic tarballs, etc. But the license is OSI approved, such as GPL, BSD, etc. so in theory someone could fork the project.
TL;DR - development model != license
Re:Why Wolfram tech isn’t open source (2019)
by samhw on Saturday December 18, 2021 @02:32PM
(#29607750)
> There are some true open source projects where the development model is some company "throwing code over the wall". Often they don't make it easy or even possible for anyone outside the company to contribute[...]
Google's V8 engine is essentially an example of this, though they do notionally have some framework for outside contributions (https://v8.dev/docs/contribute).
Re:Why Wolfram tech isn’t open source (2019)
by dotancohen on Saturday December 18, 2021 @11:04AM
(#29605495)
Which would be fine for e.g. verifying the results of computations done using Mathematica.
I completely agree that Mathematica needs a steady stream of income to continue, it is a great language and for many use cases the best available. But every time I see a paper that relied on Mathematica for critical conclusions I'm forced to dismiss it as incomplete speculation.
this is commonly referred to as "source available".