Good point. But ideally the story needs to be complete (decent package manager/configuration/repl/deployment story/build system/testing libs). Dispense with the worst of java…. that takes time of course, but the strategy of letting java devs keep writing java is good.
On Mon, Feb 24, 2014 at 3:10 PM, Cédric Beust ♔ <[email protected]> wrote: > On Mon, Feb 24, 2014 at 9:59 AM, phil swenson <[email protected]>wrote: > >> The reason I brought up Play/Akka is as far as I know is there is no >> equiv on ceylon/kotlin/etc. if someone wants to adopt a new language, it >> sure is nice if you don’t have to roll your own ecosystem. >> > > Both have a Java version so I don't see any issue there. That's assuming > you'd want to use either of these (Play has some good momentum but I don't > see a lot of traction for Akka outside the bleeding edge Scala crowd). > > -- > Cédric > > -- > You received this message because you are subscribed to the Google Groups > "Java Posse" 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]. > Visit this group at http://groups.google.com/group/javaposse. > For more options, visit https://groups.google.com/groups/opt_out. > -- You received this message because you are subscribed to the Google Groups "Java Posse" 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]. Visit this group at http://groups.google.com/group/javaposse. For more options, visit https://groups.google.com/groups/opt_out.
