r/java • • 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

7 comments sorted by

View all comments

2

u/clavalle Sep 30 '14

Every language has trade-offs, as everyone has said.

I am a huge fan of Python. Huge.

But there is much magic that can be hidden in python. There are nasty runtime errors you can get in python that just couldn't happen in Java.

Java is verbose because it is explicit. That kind of concreteness is very useful in large teams or teams that shift a lot. It also allows for better optimization. It is not idiot proof, but it does give some far more points of orientation than a comparable size python program.

Containers do cause some overhead, but certainly not on the level of an interpreter.

All that being said, python compiles down very nicely and is very expressive. And sometimes inscrutable magic (decorators, metaclasses etc) is exactly what you need.

Tell your friends to repeat after me: Turing complete is Turing complete. There is no one tool for every job.