3 ms·
I built my bread and butter with Java and Spring for ~20+ years, and I can safely say whilst commendable to reduce the bloat, it's the language itself which is
by SillyUsername 3y ago
I built my bread and butter with Java and Spring for ~20+ years, and I can safely say whilst commendable to reduce the bloat, it's the language itself which is bloated af.
Features bolted on late like function pointers (sorry lambda functions, which are effectively delegates, something they said they'd never do https://web.archive.org/web/20080127045532/java.sun.com/docs/white/delegates.html https://web.archive.org/web/20080127045532/java.sun.com/docs... ), too many deprecated APIs, keywords that mostly go unused and have alternatives (volatile - a CPU option for memory access with shared threads, transient - now handled by serialisation frameworks, synchronized - now handled by locks, protected - barely used in preference to package etc).
I moved to Typescript, AWS lambdas and Express framework, it has all this framework's simplicity baked in.
To other Java Devs who have made their bread and butter with the language (and perhaps nothing else), don't knock it until you try it, the path from Java to Typescript or other typed language is easier than it looks and you'll wonder why it ever took so long to knock up quick systems.
- deleted 3y ago[deleted]
- croo 3y agoJava is 28 year old, Typescript is 10. Give it another 20 year and similar patterns will emerge as the language matures.
- SillyUsername 3y agoTrue, but imho at some point people need to let go of legacy code because of the maintenance headache and start again, same is true for the whole eco system. I fully expect if I'm still alive in another 10 I'll be choosing something other than TS as a main language (fwiw I still do Java).