IssueRaiser

> AutoCAD is going to be big, Quickbooks is going to be big, FireFox is going to be big 1.

> AutoCAD is going to be big, Quickbooks is going to be big, FireFox is going to be big 1. you probably aren't writing those. 2. Even if you are, you probably aren't writing them in Java. The problem is the reason why you have to write so many lines in Java. Annoying checked exceptions, lack of expressiveness, boilerplate. Strong type checking? great. prevents whole swaths of errors. > Move code around, change signatures, add a function to an interface, and I know nothing is broken. Python can’t. True, now how painful is it without the IDE? > It’s true that in Java you tend to have lots of filler code right and that sucks. The reason that few lines of code is nice isn't just the chances of bugs occuring. It's also nice because it means that I can pack in logic into a smaller, more readable, space. All that other stuff in java doesn't really do much of anything, it is just there (mandatory javadoc on a method called boolean isFooFrobulated(Foo foo), yay so useful!). It means I have to write it, have to maintain it, have to read through it when looking for a bug. Consider how many java haters actually like C#. It just adds in better tooling to reduce the amount of stupid boilerplate code you have to write. It adds a nice layer of sugar on top that makes things far more pleasant.

Posted by serge2k on Jun 24, 2015, 6:18 PM

Tags

Related issues

Raise real-world problems, find people facing the same issue, and discuss solutions.5,500 issues0 comments

reliability (Other)

> AutoCAD is going to be big, Quickbooks is going to be big, FireFox is going to be big 1.

serge2kJun 24, 2015, 6:18 PM

> AutoCAD is going to be big, Quickbooks is going to be big, FireFox is going to be big 1. you probably aren't writing those. 2. Even if you are, you probably aren't writing them in Java. The problem is the reason why you have to write so many lines in Java. Annoying checked exceptions, lack of expressiveness, boilerplate. Strong type checking? great. prevents whole swaths of errors. > Move code around, change signatures, add a function to an interface, and I know nothing is broken. Python can’t. True, now how painful is it without the IDE? > It’s true that in Java you tend to have lots of filler code right and that sucks. The reason that few lines of code is nice isn't just the chances of bugs occuring. It's also nice because it means that I can pack in logic into a smaller, more readable, space. All that other stuff in java doesn't really do much of anything, it is just there (mandatory javadoc on a method called boolean isFooFrobulated(Foo foo), yay so useful!). It means I have to write it, have to maintain it, have to read through it when looking for a bug. Consider how many java haters actually like C#. It just adds in better tooling to reduce the amount of stupid boilerplate code you have to write. It adds a nice layer of sugar on top that makes things far more pleasant.

Comments (0)

No comments yet. Start the discussion.

Comment on this issue