thanks for pointing out its AGPL.. i was going to mention it as an additional alternative in the switch from PHP to one of Java/Node.js/Python/Ruby. but AGPL

thanks for pointing out its AGPL.. i was going to mention it as an additional alternative in the switch from PHP to one of Java/Node.js/Python/Ruby. but AGPL for a language is a deal breaker. i accept AGPL for an application, but not for our language (we will make sites for our clients that dont want their stuff open source, and we dont want to be back in license-hell) on tip for opa: pick a license that is common for languages. besides the license i think the language looks _very_ useful (more compile time checks, pretty syntax, same user created data types on both client and server).