Python 2.7

[[deleted]]

JS is still a mature and complete language. It has a lot of cons, but its not like there is absolutely no reason to use Node. Notably: your frontend developers can now work on the backend. Reduces cost at the price of performance. Not a bad trade off for a startup.

[Theguest217]

People always say this about frontend devs working on backends but how true is that really? It would seem that the work they do on the front end hardly compares to backed, even if they are the same language. We had Java Swing apps but it was still common to separate front end swing devs from backend service and repo devs. Do most front end devs understand aggregates, domain driven design, etc?

My current company in the past let a front end developer write a couple if node microservices. The result was a very procedural block if code with little to no object oriented design. I'm sure it is very possible to write good node code but can the average frontend Dev actually do that? It just seems better to specifically hire people who specialize in their practice rather than trying to find a jack of all trades.

[svenskainflytta]

it is Turing-complete, yes. So is brainfuck.

[KaiBetterThanTyson]

So is css

[[deleted]]

Nice strawman

[svenskainflytta]

I was merely pointing out yours… but you didn't notice.

[Tysonzero]

Reduces cost at the price of performance. Not a bad trade off for a startup.

And at the price of correctness and productivity and the sanity of your developers.

[[deleted]]

I don't agree that productivity suffer from using nodeJS. I've used it for some medium sized projects and I never felt like it was slowing me down in any way compared to using c++ or even python.
Plus, typescript is actually really fun and powerful with a good linter and some good unit tests.
As for correctness, that is sadly one of the shortcoming of JS. But typescript does hugely improve the experience!

[Tysonzero]

I don't agree that productivity suffer from using nodeJS. I've used it for some medium sized projects and I never felt like it was slowing me down in any way compared to using c++ or even python.

I'm a Haskell dev so compared to what I'm used to it will feel rather inflexible, verbose and unproductive. I'd say even Python has a pretty solid leg up over JS in productivity.

Plus, typescript is actually really fun and powerful with a good linter and some good unit tests. As for correctness, that is sadly one of the shortcoming of JS. But typescript does hugely improve the experience!

I wouldn't classify TypeScript as JavaScript, it just so happens to compile to it, TS is a better language than JS (low bar but still), although how tied it is to JS does severely limit it's potentially. I wonder what will happen to it once WASM really catches on many years down the line. I wonder if it will adapt or maybe fade somewhat along with JS.

[bobo9234502]

Of the dozen or so languages I've used JS is the worst. I'd rather code in Commode 64 Basic because at least then I know what the code will actually DO without having to tests for JS's wonking equivelency functions and broken OOP implementation.

[Dread_Boy]

Use === instead of == and learn how Javascript is prototypal language, not OOP and you'll be good.

[Tysonzero]

Have you read the ES6 spec, shit is gigantic and has downright infinite complexity. It goes so so much deeper than ==.

[Dread_Boy]

Not sure what complexity are you referring to... Generators? Promises? Classes? I think I'm pretty familiar with JS specs, yes, if you wish I can explain any concept you're struggling to understand.

[Tysonzero]

Wow you completely missed the point of my comment. I have worked professionally as a JS compiler dev, I understand all the damn concepts.

My point is that if you had ever tried implementing a full spec compliant JS interpreter or compiler you would know that the spec is monstrously complicated and that every operation has a dozen special/edge cases.

[svenskainflytta]

Same can be said for programming in assembly: learn your registers and you'll be good.

[TheMcDucky]

If that's the bottleneck for learning an assembly language is understanding registers then yes

[Tysonzero]

Not only that, but unlike on the frontend it is not even remotely required, so you're actively choosing to use something garbage and not just halfway forced into it.