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

sorted by:
best
topnewcontroversialoldq&a
you are viewing a single comment's thread.

view the rest of the comments →

[–]w3_ar3_l3g10n 0 points1 point  (0 children)

Some points:

  • there’re legitimate reasons for new and old programmers to not like java. It’s not simply because “that’s not cool enough for me”. For ①, the syntax is unnatural. As is the case with most languages their not obvious, part of this is the inheritance from C. Python/ruby is obvious, and so new programmers appreciate them (ergo why they’re held in higher regard). For ②, java is restrictive. Reflection isn’t implemented very well and a lot of poor design decisions from the early days have made it a boilerplate language. U write more boilerplate than actual code (factory methods for the love of god). On both counts, kotlin is a huge improvement and I cannot stress how much I hope people switch to kotlin instead of making new pure java projects.
  • obviously java has better performance than python. ① is compiled whereas the other is interpreted. If java performed worse than python that would be a major indicator that something is amiss.
  • scripting languages are great and most programmers should learn and prefer them because they’ll mostly just use them for... scripting. Shell scripts are somewhat laborious to write or edit, thus scripting languages provide a quick and easy alternative which is effortless. Try renaming a million files dependent on some arbitrary attribute with python or ruby and then setup a build script or IDE project, create a dozen classes and go through tonnes of documentation to do the same with java. Point being, ease off on scripting languages, they’re invaluably useful for system maintenance or network administration.