Hello, The issues:
- GPL family of licenses and left licenses is not whitelisted in certain organisations - If you make any changes add internal functionality, even if it not relevant or has no chance of getting accepted into upstream, you cannot keep it proprietary when distributing - In libraries you cannot make changes or hacks to the interface for workarounds which may not be relevant to upstream since this might to accommodate better fit with proprietary API - If some organisation is not using Racket because of the license, then this will increase adaptation hence the whole ecosystem - Since it is Homoiconic and has metaprogramming, when code is generated and then optimised either in source or binary, it is not clear whether what license apply. You may not have consistent interface due to inlining and other optimisation and mixing of code from libraries in meta programming S -- You received this message because you are subscribed to the Google Groups "Racket Developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/racket-dev/CAAfFNYFKP66vnqeb3KbQS%2BJtDgRpqeYG4rSLpFH6amun%3DHP%2BxQ%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
