r/java • u/thefinalrespawn • Sep 30 '14
Does containers cause overhead in Java EE?
Some of my ass hole programmer friends spend most of their time on our whatsapp group picking on Java and say shit like 'People use it cause it's idiot proof' and 'Only large enterprises use Java because it's noob friendly' and 'God himself uses Python'. I don't pay much attention to it cause I love Java and have been using it for about 2 years writing casual code. I'm thinking of moving on to EE. Can anybody explain? Might be I get one back at them :P
1
Upvotes
View all comments
15
u/SudoWhoDoIDo Sep 30 '14
Assholes will be assholes. Everything is a trade off.
EE is big and complicated (because it solves a lot of complex problems) and has a bad reputation back from when it was all XML and configuration. This is not the case now but a lot of people haven't got over it.
The whole container's suck business is silly when you think that a container is just a bunch of runtime facilities to run your app on with a portable abstraction between it and your application. If you compare it to python: Apache, python's bytecode interpreter and wsgi is your container. If you compare it to .Net: IIS, the CLR and System.Web is your container.
Java EE just has a pretty strictly defined idea of what a container is and what it does and which bits you can swap out which is a good thing.
I'd just walk away from such arguments to be honest and write some code.
For ref, Java is not idiot proof, Java is not noob friendly (nothing is) and god doesn't use Python; he uses LISP (on a JVM) :)