4 ms·

Version 11? Last time I checked they where at 4. Are they using semantic versioning? If yes, that many major versions is a red flag.

by brodo 6y ago

255kb 6y ago
Tell that to Java or Nodejs :D
- jmisavage 6y ago
  True. Node is an interesting one since the odd number releases are for more for testing new features while the even numbered ones are the stable/lts builds. Odd numbered releases are become EOL as soon as the next major release is out. I always try to tell the devs I work with to stick to the even numbered ones because of that.
- lolive 6y ago
  For Java, it’s easy: - v8: we added functions and streams. It basically changes everything. We also added asynchronous stuff but you don’t care yet. - v11: we added built-in async http. Now you really want to have a look at that asynchronous stuff from v8. And that’s pretty much it.
  - lolive 6y ago
    By the way, we are at Java15 at the moment. And don’t ask me what happened in seasons 9, 10, 12, 13, 14 and 15. Like grey’s anatomy, nobody knows and nobody cares.
    - The_rationalist 6y ago
      Only mediocre developers don't care about mastering their tool, but it seems that such mediocrity is quite institutionalized in the Java ecosystem. Java is evolving very quickly and will soon have e.g pattern matching.
      - lolive 6y ago
        Am I the only one to consider "var" as a pointless way to declare a typed variable in Java? Especially in very classical cases like interface/implementation: AnInterface<String, String> foo = new AnImplementation<>();
jmisavage 6y ago
Its this artificial 6 month release cycle which is causing it. Some of the breaking changes are extremely minor, but according to SemVer that's a new major release. They do have minor and bug releases in the months following the release.
Abildtoft 6y ago
They use semantic versioning. Their handling of the upgrade process, however, is one is one of their strong suits. In my experience, updating even medium to very advanced apps is often quite simple and well guided. For more, see: https://angular.io/guide/releases https://angular.io/guide/releases https://update.angular.io/ https://update.angular.io/ https://angular.io/cli/update https://angular.io/cli/update

Version 11? Last time I checked they where at 4. Are they using semantic versioning? If yes, that many major versions is a red flag.

by brodo 6y ago

Version 11? Last time I checked they where at 4. Are they using semantic versioning? If yes, that many major versions is a red flag.

255kb 6y ago

Tell that to Java or Nodejs :D

jmisavage 6y ago
True. Node is an interesting one since the odd number releases are for more for testing new features while the even numbered ones are the stable/lts builds. Odd numbered releases are become EOL as soon as the next major release is out. I always try to tell the devs I work with to stick to the even numbered ones because of that.
lolive 6y ago
For Java, it’s easy: - v8: we added functions and streams. It basically changes everything. We also added asynchronous stuff but you don’t care yet. - v11: we added built-in async http. Now you really want to have a look at that asynchronous stuff from v8. And that’s pretty much it.
- lolive 6y ago
  By the way, we are at Java15 at the moment. And don’t ask me what happened in seasons 9, 10, 12, 13, 14 and 15. Like grey’s anatomy, nobody knows and nobody cares.
  - The_rationalist 6y ago
    Only mediocre developers don't care about mastering their tool, but it seems that such mediocrity is quite institutionalized in the Java ecosystem. Java is evolving very quickly and will soon have e.g pattern matching.
    - lolive 6y ago
      Am I the only one to consider "var" as a pointless way to declare a typed variable in Java? Especially in very classical cases like interface/implementation: AnInterface<String, String> foo = new AnImplementation<>();

jmisavage 6y ago

Its this artificial 6 month release cycle which is causing it. Some of the breaking changes are extremely minor, but according to SemVer that's a new major release. They do have minor and bug releases in the months following the release.

Abildtoft 6y ago

They use semantic versioning. Their handling of the upgrade process, however, is one is one of their strong suits. In my experience, updating even medium to very advanced apps is often quite simple and well guided. For more, see: https://angular.io/guide/releases https://angular.io/guide/releases https://update.angular.io/ https://update.angular.io/ https://angular.io/cli/update https://angular.io/cli/update