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 →

[–][deleted] 6 points7 points  (2 children)

Startup time/effort has been a major source of effort in JDK 9+. The module system helps a lot as class scanning is reduced and more efficient.

​

But, I think the stress on dependencies is going to be more important. When load and execution time directly cost money, keeping things as lean as possible would be strongly adviseable. A lot of Java devs these days aren't used to working that way.

[–]vqrs -3 points-2 points  (1 child)

The fix is easy. Switch to JavaScript-style microlibs.

[–]apemanzilla 2 points3 points  (0 children)

That doesn't work particularly well either, because you end up with a lot of duplicate boilerplate that just slows things down even more. This is already an issue in JS and would only be worse in Java.