3 ms·

> of Java is how verbose and full of boilerplate it is. yes, new SimpleLang can have lessons learned during last 20 years implemented, as in example from anoth

> of Java is how verbose and full of boilerplate it is. yes, new SimpleLang can have lessons learned during last 20 years implemented, as in example from another commenter: https://news.ycombinator.com/item?id=37068380 https://news.ycombinator.com/item?id=37068380 Currently, for a given task, Java usually have 5 legacy deprecated ways to solve, and two more in newish Java versions, and dev needs to keep all of them in memory to be able to read and understand other's code. > As for there now being multiple ways to write the same thing, this seems like something that could be easily linted into consistency. that's if you don't work with any legacy systems and 3p libraries and never switch projects/jobs

user432678 3y ago
Sounds like Kotlin is exactly such SimpleLang.
- seanmcdirmid 3y ago
  Ya, I'm not sure why people would use Java anymore given that the SimpleLang is pretty good.
- lmm 3y ago
  Kotlin is even worse; it's younger than Java but also has 5 legacy ways to solve the problem and two more in the newer version, it's just that the legacy ways have been removed so any examples you find online won't work any more.
  - unscaled 3y ago
    Are there any examples for this? Kotlin sure moves faster than Java, but except for features that were experimental or unstable to begin with (coroutines, -X flags), I can't think of a case where more than 1 deprecated version exists (and the "deprecated" versions are not nearly as crufty as Java).
    - lmm 3y ago
      Those "experimental or unstable" features tend to be the advertised selling points of Kotlin. Particularly for async, the previous "experimental" APIs were the only ones available at the time and the recommended way of using Kotlin.
- kaba0 3y ago
  Kotlin is anything but simple
kaba0 3y ago
You way over exaggerate the number of different ways a given thing can practically be done in Java. Pattern matching for example only has the visitor pattern as a counterpart and you ain’t going around spewing visitor patterns, it not as simple. Sure there are a few warts, e.g. arrays work a bit differently than Lists, and primitive-object discrepancy, but every language will pick up similar issues over time.

user432678 3y ago

Sounds like Kotlin is exactly such SimpleLang.

seanmcdirmid 3y ago
Ya, I'm not sure why people would use Java anymore given that the SimpleLang is pretty good.
lmm 3y ago
Kotlin is even worse; it's younger than Java but also has 5 legacy ways to solve the problem and two more in the newer version, it's just that the legacy ways have been removed so any examples you find online won't work any more.
- unscaled 3y ago
  Are there any examples for this? Kotlin sure moves faster than Java, but except for features that were experimental or unstable to begin with (coroutines, -X flags), I can't think of a case where more than 1 deprecated version exists (and the "deprecated" versions are not nearly as crufty as Java).
  - lmm 3y ago
    Those "experimental or unstable" features tend to be the advertised selling points of Kotlin. Particularly for async, the previous "experimental" APIs were the only ones available at the time and the recommended way of using Kotlin.
kaba0 3y ago
Kotlin is anything but simple

kaba0 3y ago

You way over exaggerate the number of different ways a given thing can practically be done in Java. Pattern matching for example only has the visitor pattern as a counterpart and you ain’t going around spewing visitor patterns, it not as simple. Sure there are a few warts, e.g. arrays work a bit differently than Lists, and primitive-object discrepancy, but every language will pick up similar issues over time.