The results are in: http://www.leonardoborges.com/writings/2009/07/31/jvm-language-preferences-poll-results/
To save you some suspense the winner was groovy. But a common theme was both simplicity of the language (which hurt scala) and Java integration. As unscientific as this poll is, integration with the Java platform is a key requirement for many looking to alternate languages. So this is something we as a community should work to get right. Even if not all of us are compiler geeks (I'm certainly not), perhaps our collective experiences and input can help brian and andy iron out all the kinks. I know this integration is very important for me and will help determine my future tooling/langauge choices for a long time to come.
brianFri 31 Jul 2009
So this is something we as a community should work to get right.
Completely agree - hopefully the existing tickets we have are the biggest outstanding problems.
I also have some ideas to package up Fan's meta-data into a standard Jar so that you only need to deploy the jars containing your Fan code (and don't also need pods).
Any other stuff should definitely be brought up on forum for discussion to make sure it is on the radar.
cheeserFri 31 Jul 2009
Now that sounds really interesting actually. Would this solution include the ability to use pods as well if you needed to? That'd be handy, though not necessarily a deal killer either way. I'm thinking of use cases like plugin systems where libraries are added in the wild that don't necessarily come from/with the project itself. But that could be mitigated with an SDK for that project that converts pods to jars as well. One extra step for that 3rd party dev but not onerous, i don't think.
tompalmerFri 31 Jul 2009
Importing a jar as a pod would be nice, too. Then you get your nice Fan setup.
When you are ready to export, it could export all your Fan pods as well as those Java jars back out again.
cheeser Tue 28 Jul 2009
Go vote! ;)
http://www.leonardoborges.com/jvm_languages_poll.html
cheeser Fri 31 Jul 2009
The results are in: http://www.leonardoborges.com/writings/2009/07/31/jvm-language-preferences-poll-results/
To save you some suspense the winner was groovy. But a common theme was both simplicity of the language (which hurt scala) and Java integration. As unscientific as this poll is, integration with the Java platform is a key requirement for many looking to alternate languages. So this is something we as a community should work to get right. Even if not all of us are compiler geeks (I'm certainly not), perhaps our collective experiences and input can help brian and andy iron out all the kinks. I know this integration is very important for me and will help determine my future tooling/langauge choices for a long time to come.
brian Fri 31 Jul 2009
Completely agree - hopefully the existing tickets we have are the biggest outstanding problems.
I also have some ideas to package up Fan's meta-data into a standard Jar so that you only need to deploy the jars containing your Fan code (and don't also need pods).
Any other stuff should definitely be brought up on forum for discussion to make sure it is on the radar.
cheeser Fri 31 Jul 2009
Now that sounds really interesting actually. Would this solution include the ability to use pods as well if you needed to? That'd be handy, though not necessarily a deal killer either way. I'm thinking of use cases like plugin systems where libraries are added in the wild that don't necessarily come from/with the project itself. But that could be mitigated with an SDK for that project that converts pods to jars as well. One extra step for that 3rd party dev but not onerous, i don't think.
tompalmer Fri 31 Jul 2009
Importing a jar as a pod would be nice, too. Then you get your nice Fan setup.
When you are ready to export, it could export all your Fan pods as well as those Java jars back out again.