|
|
|
|
|
by killerstorm
27 days ago
|
|
The original Java standard class library is very capable, and you can do a lot using just 20+ years old classes. People responsible for Java platform design were thinking from perspective that software can be "done" and keep working for decades if not centuries. But modern Java developers don't want to write this way, it's not "modern". I guess incentives aka "job security" is the main force here. Would you rather say that a piece of software is "done" and can keep working for decades with only periodic maintenance required, or would you rather "we need to migrate from Quux to Baar as Quux is deprecated and unmaintained now, and Bazz might not be optimal from performance standpoint so we need a replacement. so yeah we'll be busy this year"? And conference people are so helpful with "Baar is the only valid way to make Java now. If you think about rawdogging JCL you're a goblin" |
|