Without wishing to get into a holy war I'd like to suggest that if you're unsure about licences it's best to go with BSD. That gives your users some confidence that their time wasted learning and writing code for your language won't be wasted when they change jobs.
Or worse, should *you* change jobs you might find yourself unable to use the language you created just because you don't own all the copyright. Best to stay out of that toenail-fest. -----Original Message----- From: Stefan Hong <[email protected]> Sender: [email protected] Date: Mon, 21 Nov 2011 09:50:15 To: <[email protected]> Reply-To: [email protected] Subject: Re: [The Java Posse] A new Java-ish programming language: Meso The server is up, but you might need to wait a little longer to load the page since it is a busy server at my school. I will probably move the site to amazon someday... The language is still in the proof-of-concept stage and does not have any library yet. If it does, I will either use the GPL with linking exception or LGPL for the library. Stefan On Nov 21, 2011, at 2:43 AM, Mark Derricutt wrote: > Interesting - I'd love to take a look but your server seems down. > > Any reason for choosing GPL v3 at all? I was wondering, do you have a > runtime library and if so - is that also under GPLv3? ( i.e. meaning no > commercial applications can be built using Meso )? -- You received this message because you are subscribed to the Google Groups "The Java Posse" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/javaposse?hl=en. -- You received this message because you are subscribed to the Google Groups "The Java Posse" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/javaposse?hl=en.
