On 23 July 2012 11:07, Russel Winder <[email protected]> wrote: > On Sun, 2012-07-22 at 16:41 -0700, Cédric Beust ♔ wrote: > […] > > As for the concurrency library... seriously? java.concurrent.util is not > > just very powerful, it's very well designed and it's running tens of > > thousands of high volume web sites today. No other library can claim to > > come close to this, except maybe .net's. > > Sadly though it doesn't look like ParallelArray will make it into Java > 8. Unless I missed something recently. >
What! This on top of the Jigsaw fiasco? I'm thinking that Java 8 won't actually be Java 8. Based on established naming conventions, a far more appropriate number would be Java 7S (though I suspect that Apple has already patented the idea of sticking 'S' to the end of an underwhelming yet over-hyped release) > java.concurrent.util is showing more and more high-level features as > Doug et al. work them in, but the problem remains that most Java > programmers still think shared-memory multi-threading is the way to code > up parallel algorithms. > > Clearly GPars and Akka are trying to provide something at higher levels, > but traction is relatively poor amongst people other than very early > adopters. > > Having done some Java training recently, I am depressed by the attitude > of the average Java programmer. All they want to do is fulfil management > requirements, no thought of improving themselves and their knowledge and > expertise. This is in stark contrast to the folks involved with > organizations who are ditching Java in favour of C++/Python or > Scala/Python of which there is a lot happening, hence me getting solid > business doing Python training. > > -- You received this message because you are subscribed to the Google Groups "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.
