On Sat, 21 Jan 2012 14:31:26 +0100, Moandji Ezana <[email protected]> wrote:
In 2006, when Neal Ford coined or popularised the term polyglot
programming, it seemed to gain some popularity.
However, in the past few years, the trend seems to have gone towards
using
as few languages as possible.
I don't know whether it was a passing fancy...
In Java you could use GWT or Android on the client and Hibernate on the
server and not see either JavaScript or SQL.
... but you have JPAQL. I'd say that you can only avoid it in simpler
cases.
With Node.js, JavaScript becomes the common language. Fantom and Clojure
(via ClojureScript) can also compile to JavaScript.
Compiling to JavaScript just doesn't mean you're noy polyglot. In this
case JS serves as bytecode.
Was polyglottism ever a good way to build an application? Is this just a
pendulum swing or rather the result of more powerful tools?
Actually we have created an ecosystem where it often happens that a rock
star extracts a new concept from his bag and we have some "wow" effect,
and it seems that from now on everything must be done in that way.
Fortunately, the effect sooner or later vanishes, but the good idea
remains. For what concerns me, I don't feel compelled to be polyglot. I'm
just fine knowing that I can have multiple weapons to do something and I
can pick the best fitting if I want.
--
Fabrizio Giudici - Java Architect, Project Manager
Tidalwave s.a.s. - "We make Java work. Everywhere."
[email protected]
http://tidalwave.it - http://fabriziogiudici.it
--
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.
