News for hackers. Stuff that matters.
Re:Porting 58000 lines of D and C++ to jai, Part 0: Why and How by bsder on Wednesday November 23, 2022 @04:53PM (#33725008)
> I don't understand why they are not working in the open, this is a tool, not a game, input for a large community is extremely valuable.

Ayup. Talking about JAI is simply a waste of time until they put it in the open under a genuine open-source license.

Otherwise, you wind up with situations like "Our Machinery".

Re:Porting 58000 lines of D and C++ to jai, Part 0: Why and How by throwaway17_17 on Wednesday November 23, 2022 @07:44PM (#33726487)
Just curious, but when you genuine open-source license what do you include? Going back to the earliest talks on a potential language Blow cites a non-GPL, permissive license as his probable license. I know some folks tend to not count BSD, Public Domain, etc as open source.
Re:Porting 58000 lines of D and C++ to jai, Part 0: Why and How by bsder on Wednesday November 23, 2022 @08:15PM (#33726723)
Certainly anything OSI is acceptable. GPL isn't my cup of tea, but it's fine, too. Owner/authors are doing the work and if you don't like what license they choose, you can go elsewhere.

As long as no entity can retroactively revoke your ability to use the source code, it's probably sufficient.

As things currently stand, that is NOT true for JAI.

Re:Porting 58000 lines of D and C++ to jai, Part 0: Why and How by umanwizard on Thursday November 24, 2022 @12:59AM (#33728187)
> I know some folks tend to not count BSD, Public Domain, etc as open source.

This isn’t true, unless you’re talking about some niche opinion held by a few eccentric people.

Even Richard Stillman, probably the most ardent and uncompromising copyleft activist in the world (elevating the GPL to nearly religious status) accepts that non-copyleft licenses like BSD are open-source (and free software, a term he prefers).