It might be nice to do the following: Have a Julia-lite build, that only has core stuff (by core, I’d still have all the tuples, arrays, numeric and string types, i/o, documentation, etc., but not the esoteric math stuff… but that with a single import (or package add, whatever), could load up all the non-GPL stuff, to be about equivalent to what Julia has now.
Also a Julia no-GPL build, same as Julia-lite with the numerical computing package pre-loaded… and finally, for people who don’t care that their programs *must* become open source just by using Julia, a Julia + GPL (FFTW, the GPL parts of SuiteSparse, and whatever the 3rd thing was…) Would that be that much harder than having both a stable and nightly build? Scott > On Apr 30, 2015, at 5:42 PM, Stefan Karpinski <[email protected]> wrote: > > This is not why Base is so large – it's large because people expect technical > computing environments to be "batteries included" and to just work without > having to install additional stuff. > > On Thu, Apr 30, 2015 at 5:26 PM, Scott Jones <[email protected] > <mailto:[email protected]>> wrote: > Maybe because it seems that a lot of the major packages have been put into > Base, so it isn't a problem, as MA Laforge pointed out, leading to Base being > incredibly large, > with stuff that means Julia's MIT license doesn't mean all that much, because > it includes GPL code by default... > > Scott > > On Thursday, April 30, 2015 at 5:03:52 PM UTC-4, Stefan Karpinski wrote: > On Wed, Apr 29, 2015 at 9:08 PM, Scott Jones <[email protected] <>> wrote: > Your restrictions are making it very hard to develop easy to use APIs that > make sense for the people using them… > > That’s why so many people have been bringing this issue up… > > Not a single person who maintains a major Julia package has complained about > this. Which doesn't mean that there can't possibly be an issue here, but it > seems to strongly suggest that this is one of those concerns that initially > appears dire, when coming from a particular programming background, but which > dissipates once one acclimatizes to the multiple dispatch mindset – in > particular the idea that "one generic function" = "one verb concept". >
