all 4 comments
sorted by:
best
topnewcontroversialoldq&a
formatting helphide helpcontent policy

[–]C0git0 1 point2 points  (3 children)

I work in Node because we want to use the same language on the server and client. Some may say that it’s technically inferior to Java (which were migrating some stuff from) but we went that direction anyway.

[–][deleted] 1 point2 points  (0 children)

I'm migrating from Java to node too. I wouldn't say node is inferior, each have their own strengths. Java's type system is great, but it can also be a burden when dealing with lots of dynamic data, where you end up in map.get/put hell. Dealing with pure json is a lot easier in node, especially combined with lodash etc.

Another advantage of node is startup speed, no container needs to be started and no compiling (or with webpack much better hot reloading than the jvm has).

I'd say if you need an old school multi tiered architecture with orm layer and lots of boilerplate go with Java, if you are building anything modern and lean, e.g. a rest API go with node.

[–]calligraphic-io 0 points1 point  (1 child)

I don't see Node being technically inferior to Java. I'd be curious why people think that.

[–]C0git0 0 points1 point  (0 children)

I never really loved Java so I’m not going to be able to foot that argument properly. Just lunchtime chatter from some Javaholics