News for hackers. Stuff that matters.
Re:Doubling down on permissive licensing and the Elasticsear... by nealmcb2 on Wednesday January 27, 2021 @09:53PM (#25937557)
Re: > it was to inhibit Cathedral-style codebases from using GPLed software at all.

I'm surprised at the notion that RMS ever had the intention of inhibiting GPL use in Cathedral-style codebases. And I agree with others that big frameworks existed back then also.

Re:Doubling down on permissive licensing and the Elasticsear... by derefr on Thursday January 28, 2021 @10:31AM (#25943349)
Sure, big frameworks existed back then, but they were all either

1. literally "frameworks" in the inversion-of-control sense — where your code is a script that runs "inside" the framework — and you don't ship the framework to your customers as part of your product, but rather walk them through getting it from its own vendor as a prerequisite step to installing your product (e.g. TeX); or

2. proprietary, not copyleft-licensed (e.g. game-console SDKs.)

If anyone has a good counter-example, I'm all ears :)

Re:Doubling down on permissive licensing and the Elasticsear... by xorcist on Thursday January 28, 2021 @03:36AM (#25939599)
Especially since the term cathedral was popularized by esr to call out the development style of the GNU project.