←back to thread

160 points todsacerdoti | 1 comments | | HN request time: 0.001s | source
Show context
hresvelgr[dead post] ◴[] No.41900976[source]
[flagged]
davedx ◴[] No.41900995[source]
I’ve worked on some huge nodejs projects, it’s a great language for “serious projects”. It has costs and benefits like any other language. If you use TypeScript then IME many of the costs are mitigated.

What exactly makes JavaScript so unsuitable?

replies(3): >>41901085 #>>41901154 #>>41901238 #
rob74 ◴[] No.41901238[source]
> What exactly makes JavaScript so unsuitable?

If you look at JavaScript's history (especially for backend development), it reads like a series of accidents: First, the JS language was hacked together at Netscape in the space of a few months in 1995, and after that it was quickly baked in into all web browsers and therefore became very hard to change in a meaningful way. Then, Google developed the V8 engine for Chrome, and someone thought it would be a great idea to use it for running JS in the backend. My thoughts on that were always: "just because you can do something doesn't mean that you should"...

replies(1): >>41911866 #
1. wiseowise ◴[] No.41911866[source]
You didn’t list any issues of JS.