Earlier quoted context omitted.
Java/Swing isn't even a data format, it's the interface tech. Nor is it outdated. Like, if you'd said COBOL it might be a valid point. It's as ignorant of basic technology as saying my car runs on a particular type of rubber so I can't use batteries. Honestly, for a tech site I'm ashamed this is the top comment, just seems to be an excuse to rag on Palantir and decry not using the present FOTM.
I moved from a "sexy" NodeJS stack at my last job to a staid Java 7 stack at my current job (we can't move to Java 8 until App Engine supports it). The code at my current job is much better written, is more thoroughly tested, and is more pleasant to continue development on. The codebase at my previous job was a rat's nest, caused primarily by lower-skilled developers, no time allocated to technical debt or refactorin…
NodeJS leverages the advanced V8 JIT and async operation in its crudest form. It's good for certain classes of tasks (a lot of I/O with simple logic around it), but not as great for the more general case.
OTOH Typescript can alleviate many of the problems of JS proper, the execution model is still a bit uncomfortable. I'd rather take Erlang /Elixir for the typical Node case.