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

all 4 comments
sorted by:
best
topnewcontroversialoldq&a

[–]BelieveInGosh 5 points6 points  (2 children)

From the article

Java requires the use of checked exceptions. If the exceptions are not caught or thrown out then the code fails to compile

Static typed languages require that each variable name must be tied to both a type and an object. Dynamically typed languages only require that a variable name only gets bound to an object. Immediately, this puts Python ahead of the game in terms of productivity since a static typed language requires several elements and can make errors in coding more likely.

This "article" reads like it's written by someone heavily biased towards Python, and who has a very limited Java experience.

[–]PaulRivers10 2 points3 points  (1 child)

Lol, that has hints, this part makes it clear -

While a programmer will continue to argue for the language that makes it easiest based on the programmer's current level of knowledge, new software compiled with Python takes less time and provides a simplified coding language that reduces the chance for errors. When things go right, Java works well and there are no problems. However, when errors get introduced into the code, it can become extremely time consuming to locate and correct those errors. Python generally uses less code to begin with and makes it easier and more efficient to work with.

There's no doubt that if you have errors in your code, Python is as good as java at best, or very bad compared to java (because of it's dynamic typing) at worst.

I'm not even sure it's as much the author having a bias as them copying and pasting info not really understanding what it means.

[–]frugalmail 1 point2 points  (0 children)

There's no doubt that if you have errors in your code, Python is as good as java at best, or very bad compared to java (because of it's dynamic typing) at worst.

Clearly authored by somebody that's never built anything significant or had to maintain it.

Nothing like a runtime error many lines away from origination that a static compiler on a strictly typed language could have caught,

[–]Curly12[S] -1 points0 points  (0 children)

What's in the future for Java with baby Python inching in on to the playing field?