I've actually found that Scala is a very effective gateway to many of these technologies.
If Hadoop is your thing, just compare cascading <http://www.cascading.org/>to scalding <https://github.com/twitter/scalding>. Working with immutability and having lambdas available leads to a far friendlier API. Dig deeper still and you'll discover Spark <http://spark.incubator.apache.org/>; it's Hadoop on steroids with a bunch of in-memory caching. Bootstrap? You might want to try Jade <http://scalate.fusesource.org/documentation/jade-syntax.html>templating from the Scalate library. It's the cleanest syntax I've yet discovered for knocking out pages built out of class-heavy DIVs, which is *exactly* how Bootstrap operates. Angular? You've already got a headstart on the right mental model if you're used to lambdas and reactive programming via Futures. These technologies are not mutually exclusive choices, they're very often synergistic. And it just so happens that Scala makes a particularly good synergy with many of them. On 19 February 2014 22:58, Oscar Hsieh <[email protected]> wrote: > You would be right if Scala is the only new thing. > > I know plenty Java people interested in Hadoop, gradle, vaddin, bootstrap, > angular, mobile. Before we can inject knowledge directly to our brain, we > have to pick and choose what we want to learn. > > I agree with Rakesh. Personally I like Scala and wrote a couple programs > but Java does not bother me. None of my colleagues have any interest in > Scala. They are not lazy or stupid, in contrary they are pretty smart and > they are allocating their resources in learning technologies that can help > them the most. > > By the way, you do realize that saying "Java programmers are not actually > that interested in learning new things" does not help you to push your > agenda. > > On Wed, Feb 19, 2014 at 3:07 AM, Russel Winder <[email protected]>wrote: > >> On Tue, 2014-02-18 at 22:39 +0000, Rakesh wrote: >> […] >> > By the same token,Java 6 is 'good enough'. There's hardly any project >> > that could not be done in Java 6(assuming competent developers). >> […] >> >> Alternatively it could be that the majority of Java programmers are not >> actually that interested in learning new things, they do their job for >> money with the tools they have. So when management are not interested >> in managed change but in stable status quo because they are afraid of >> disruption, programmers fall into the trap of failing to learn and >> develop. >> > -- 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.
