3 ms·

I built a desktop application in Java Swing about 15 years ago. I dropped it because it was cemented in "old" tech. After trying to rewrite the app several time

I built a desktop application in Java Swing about 15 years ago. I dropped it because it was cemented in "old" tech. After trying to rewrite the app several times in various cross-platform frameworks for the web and mobile I gave up and went back to the old code. I fired up the project after not touching it for ten years and loaded it in netbeans. It built and ran without a single issue. I was flabbergasted. If I leave my Xamarin Forms app for a month I come back to find failing builds, broken dependencies, dependency version mismatches, and OS related failures induced by updates. I spent countless hours hunting down solutions to these and it happened numerous times for different reasons. Visual Studio changes, OS changes, core framework changes, core language changes, library changes....omg. I'm working in my old crusty Java Swing project and I love it. Each minute I spend working on it moves the application closer to done. There are awesome open source themes available now and it looks great. My old code to remember window sizes and screen/monitor positions still works. Unfortunately, that was surprising as hell. I have the expectation it will work twenty years from now. Web app or mobile? Not a chance in hell.

burntoutfire 5y ago
Java is solid as hell. That's why (well that plus the ease of hiring) it's the default choice for most major corporations.
- datavirtue 5y ago
  Developers in corporations are moving away from java at a frantic pace. A lot of it has to do with remote functions (AWS lambda etc) being very slow with such a heavy standard library and the runtime startup. It's a mistake. As is the lemming-like rush toward remote functions for everything. Everywhere I go I see people hacking on the Lambda execution meta to improve initial start times--and eventually giving up--because the PM doesn't like a slight random delay. PM keeps complaining.

burntoutfire 5y ago

Java is solid as hell. That's why (well that plus the ease of hiring) it's the default choice for most major corporations.

datavirtue 5y ago
Developers in corporations are moving away from java at a frantic pace. A lot of it has to do with remote functions (AWS lambda etc) being very slow with such a heavy standard library and the runtime startup. It's a mistake. As is the lemming-like rush toward remote functions for everything. Everywhere I go I see people hacking on the Lambda execution meta to improve initial start times--and eventually giving up--because the PM doesn't like a slight random delay. PM keeps complaining.