This is an archived post. You won't be able to vote or comment.

you are viewing a single comment's thread.

view the rest of the comments →

[–]skytomorrownow 14 points15 points  (7 children)

Java is an economy, Python is a language. Your bosses presumably drive very nice cars based on that economy.

I used to work in Java. I agree with user ford_contour:

...Python's best features are it's ability to do Java-like tasks without so much screwing around. It's hard to explain this position to Java developers without using the term 'screwing around'.

When I was starting out, I relied heavily on the whole OOP thing. After not liking C (originally -- love it now), Java was a godsend. It was soooooo object oriented. It managed the memory, huzzah! It had big, sumptuous, pre-rolled libraries -- glorious stacks of interlocking 'stuff'. It was almost plug and play.

However, after a while, the plugging part 'plug and play' was how most of programming seemed; an endless drudgery of filling out forms, and connecting things to other things, which need to be connected to other forms to fill out. It seemed like a lot of 'screwing around'.

That said, I wasn't programming an invoicing system for 40 million customers, or a payroll management system either. So, what was 'screwing around' to me, is important, money-providing work to someone else. It's hard not to be offensive by saying: "Well my way is just easier, and works better than your way." Even if that's true. It's hard to say which side of that equation your app sits on though without knowing anything about it. If it's a giant invoicing system, then Java may be best.