Re:NYPD is canceling its Palantir contract
by rnprince on Saturday July 01, 2017 @06:41PM
(#14679474)
After working with MUMPS for some time, getting to use Node.js has been a religious experience for me. I feel as if an incredible weight has been lifted off my shoulders.
I know the feeling. Four years ago I got done working on some truly terrible tech stacks and got to use NodeJS for the first time and it felt like a huge weight had been lifted off my shoulders too. Then I left that company and I'm doing Java now, and I realized that leaving NodeJS behind has also lifted a huge weight off my shoulders, but of a different kind.
What about Java makes you like it more, or about Node.js that made you particularly frustrated?
I wish JavaScript were statically typed, but I'm not convinced about switching to TypeScript yet. I can see other ways Node.js could be frustrating.
While the prize for Worst Tech Used in a Professional Setting might go to InterSystems Caché ® (syntax errors will bork your entire runtime, with no undo). And it's all downhill from there.
Nodejs (javascript + libuv, aka control flow obfuscation framework) is a strong contender. I've never worked so hard to make so little code reliable, robust, deployable. And there is no Right Way to use nodejs. Everything changing all the time, every day is a do-over.
As for Swing. Remove (or ignore) it's goofy MVC and it's just like Qt. State of the art UIMS for desktop when they both came out.