Hacker News new | ask | show | jobs
by trevordev 4021 days ago
1) I don't think any of those tools are dying, people are just sharing that other tools will work better in certain situations and each tool has it's place. I'm a fan of nodejs but I have found the dynamic typing and poor performance of JavaScript can hinder my recommendation when building a large, performance critical app.

2) The languages/frameworks I would recommend depends on what you want to build. The large amount of JavaScript libraries and its ability to work in the browser make me highly favour javascript and I have found that typescript provides a nice layer on top to provide sane typing and code auto completion for many of my needs. However, Typescript tools and the language still feel underdeveloped. I would use node to handle web requests and offload "heavier" work to c/rust/go if needed

3) I used to use c/c++ for a lot of my personal project but I have found tasks like managing memory can add unneeded complexity to the majority of my tasks. C still has it's place when certain requirements must be met.

1 comments

> use node to handle web requests and offload "heavier" work to c/rust/go if needed

Go's "net.http" package is fairly good for web requests.

agreed but I prefer to use the same language for front and back end to reduce the context switch cost when working on both ends.