That's a good question... And I have - sorry... - another one that may be a nasty question.. From the very few info I've read about Meteor, I understood that it's another framework based upon Node.js Node.jsis growing in popularity, as related frameworks... So is Meteor just another nail in the coffin of java ee as web platform?
Honestly, I was never a big fan of Java EE, but we created great applications with it. Node.js is sexy and hip, but it cannot do all the things J2EE can. Meteor itself is only Node.js in disguise, so you can count it as yet another MEAN variant (MongoDB, ExpressJS, AngularJS, Node.js, only without Express and Angular).
Similar to what we've seen a while ago with the SOAP movement we now observe a move to micro services. That means applications are split up into small. independent modules that work together to perform what previously monolithic apps did. Java was often used for those monolithic blocks, the application server received HTTP requests, it did processing of some kind and spit out HTML. I think this will change and Java will lose its position in front of the processing chain - where Node.js fits perfectly.
Thanks Stephan for your kind answer...about Java EE, I wonder if it may become "microservices based", since at least theorically there's no technical limitation to this (as far as I know, of course).
Maybe I'm wrong, but OSGI - for example - is all about bundles each of which is responsible for a small number of task....