4 ms·

Thanks for that, it was always unclear in my mind, now it's clear! ok so I'll move it to LGPL soon then ;) Yep, This is what I want for Illuminated.js. I pre

by gren 14y ago

Thanks for that, it was always unclear in my mind, now it's clear! ok so I'll move it to LGPL soon then ;) Yep, This is what I want for Illuminated.js. I prefer to have benefits of the library modifications. It's a bit more restrictive coming from MIT (I used to use it for some projects) but it's not as restrictive as a "non-commercial only" license, so IMO it's quite ok, it's a minimum of thanks to the library. Regards

Arelius 14y ago
The problem with the LGPL is that it's designed for code that is compiled and binary linked, which makes it harder to reason about for JS code. Additionally, afaict, it's problematic to use on embedded, closed platforms, such as iOS.