On Wed, Mar 2, 2011 at 1:54 AM, Kevin Wright <[email protected]>wrote:
> > No difference, it's all part and parcel of the same thing - expanding your > mental toolbox. Let's see how you might go about some of these challenges: > > *moving from server to client:* > - JavaScript (a browser is a client, right?) > - Tcl/Tk > Don't forget .net technologies as well. Stackoverflow has shown that you can actually do something cool with the .net stack :-) > *asynchronous/messaging architectures:* > This is painful to learn in any language without lambdas/function objects. > If you need to do this in Java then the SAM types will bite you. Learn in a > more suitable language first and backport your knowledge. > - Erlang > - Akka (Scala) > node.js is an easy way to get your feet wet with asynchronism and CPS, and also a good way to find out for yourself how painful it can be. > *usability/UX/design:* > Java/Swing overwhelms with boilerplate, making it hard to concentrate on > the essentials. Try something designed for design. > - JavaFX script is sadly dead now. Flex perhaps? > - HTML > - OpenGL :) > Don't forget SWT/JFace if you want to see what a modern and properly designed Java GUI API looks like :-) > Not only is it normal to learn new paradigms alongside new languages, I'm > thinking it's actually very unusual to learn just a language in isolation. > Agreed. I think the Pragmatic Programmers are being unnecessarily restrictive when they say "one new language per year". It should really be one new "technology" per year, which can be a programming language or just a new paradigm or a different way to approach development. -- Cédric -- You received this message because you are subscribed to the Google Groups "The 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.
