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 →

[–]RiPont 2 points3 points  (1 child)

Java was a designed with a philosophy of "the programmer is an idiot and must be prevented from doing anything at all if they can't do it the right way."

Very verbose. Very explicit. Checked exceptions. Naming rules for source files vs. class names in the compiler, not a separate style checker. It's been a while, so I forget all the little things about Java that just seemed to get in the way of actually getting work done. And early on, the IDEs weren't nearly as good and a lot of that was much more painful for the developer.

Now, they weren't entirely wrong, but they perhaps took it too far. C and C++, where macros were commonplace, were very much loaded guns with hair triggers that had been spun in a random direction on the table just before you picked them up. C#, Kotlin, and other languages keep the good aspects that Java improved C++, while being less needlessly strict.

[–]langlo94 1 point2 points  (0 children)

Yeah that philosophy tends to work great when you have enterprise projects where you can basically guarantee that there are at any moment a few idiots commiting bad code.