PACE (iLok) have acquired JUCE

[d.healey]

@Lindon where did you see that?

[Lindon]

@d-healey its down at the bottom of the press release that @coreyu21 pointed to - saying he'd be around to help out but was staying to work on SOUL

[d.healey]

@Lindon Oh yeah, don't know how I missed that!

[ten7kur]

Interesting!

[ten7kur]

@ten7kur said in PACE (iLok) have acquired JUCE:

Interesting!

I bet my ass GNU will not exist with PACE.
I hope im wrong!

[d.healey]

@ten7kur It won't in PACE, but they can't take it out of JUCE :) Although they could make a new version without it if Jules transferred the copyright to them.

[LightandSound]

From the looks of things they're intending to keep the license structure in place for JUCE, so I doubt this will be as much of a change as it initially sounds :p (though fingers crossed of course!)

[ten7kur]

@d-healey said in PACE (iLok) have acquired JUCE:

@ten7kur It won't in PACE, but they can't take it out of JUCE :) Although they could make a new version without it if Jules
reference?

[ten7kur]

@d-healey said in PACE (iLok) have acquired JUCE:

iff Jules transferred the copyright to them.

Im sure they did

[Win Conway]

I doubt very much that they don't intend to push heavily and/or even force iLok usage, it could even be as simple as "JUCE is now free to developers, but you have to use iLok" acquisitions are made to make money, and if the business of iLok is more valuable than the business of JUCE (Which you would have to assume it is given they where able to procure JUCE) then JUCE will be used to leverage more iLok business.
How much this affects HISE in the long term is debatable, I would have to assume that Christopher already has back up plans and such if anything nefarious was to happen with JUCE, there are alternatives for him to implement if he needed to.

[d.healey]

@Win-Conway said in PACE (iLok) have acquired JUCE:

How much this affects HISE in the long term is debatable, I would have to assume that Christopher already has back up plans and such if anything nefarious was to happen with JUCE, there are alternatives for him to implement if he needed to.

The existing JUCE codebase will always be GNU GPL so it likely won't affect HISE. However if they release a proprietary only version in the future and Christoph wants to use the features it provides then there might be issues, especially since HISE is also licensed under the GNU GPL.

[Win Conway]

@d-healey said in PACE (iLok) have acquired JUCE:

GNU GPL

Yes but if they stop selling the licences for the current codebase, you cant use it to make commercial plugins, right ?

[d.healey]

@Win-Conway Commercial yes, proprietary no.

[Win Conway]

@d-healey said in PACE (iLok) have acquired JUCE:

proprietary

Well, commercial is generally the point.

[d.healey]

@Win-Conway said in PACE (iLok) have acquired JUCE:

Well, commercial is generally the point.

Commercial developers of proprietary software are generally already paying license fees so they won't be too badly affected (assuming PACE doesn't hike the price). Non-commercial proprietary developers will suffer though, but maybe that will push more of them to make free software.

[hisefilo]

@d-healey do you think iLok protection system will be forced into Juce framework? meaning our users need to install iLok?

[Christoph Hart]

meaning our users need to install iLok?

Nah, won't happen. The JUCE team already clarified that in the forum, plus it would be a terrible marketing move...

[hisefilo]

@Christoph-Hart phew!!!! good to know :)