Tatiana McGarry
Aug 31, 2018 · 1 min read

I am a Java developer who has coded in Node.js, and I did not find it joyful in the least. I found it rife with the fuzziness and community confusion that are par for the course in JavaScript (which I blame partially on JS’s multi-paradigm model and weak typing). And no help from a compiler, either.

Node’s best ORM, Sequelize, has documentation so poor I could not have navigated it had I not already known Hibernate. And Express has the same “papering over” issue you mentioned with Spring (admittedly on a smaller scale, but the Spring source code is there for you to see at will). As a low-level programmer at heart, I don’t like boilerplate code that obscures things either, but that’s just what frameworks do. Using a framework — any framework — requires either a leap of faith, or a lot of study of the internals.

Finishing that Node server and coming back to pure, precise coding in Java was, for me, a breath of fresh air!

    Tatiana McGarry

    Written by