3 ms·
Fashion hunting and window shopping are things script kiddies look for. People actually building products and solving read world problems dont stress over that
by austin-cheney 2y ago
Fashion hunting and window shopping are things script kiddies look for. People actually building products and solving read world problems dont stress over that stuff because their attention is consumed elsewhere.
My suggestion is to just build what you want to build. If the thing you build is slow refactor it to be faster. If that thing misses some new cool kid feature then write the new feature. Never does tool fashion come up.
- bronlund 2y agoThank you. And yes, I agree. My theory is that when node became all that and all the young people went all-in, they learned how to solve everything with that mindset. And now, when they all grew up and went corporate, they took with them this way of solving problems and now, we are kind of stuck with it.
- austin-cheney 2y agoI love Node. It does a good job of exposing an OS level API of just about everything at kernel level, except file system which has an OS API for kernel level file management operations. It’s nice because of that API and it’s fast, but has its limitations. If you need to do large recursive operations Node will likely fail. If you need memory conservation for device specific operations Node is not the tool. If you want to go faster than a garbage collected language allows Node is not the tool. I think the bigger problem with Node id that most people writing JavaScript struggle to write JavaScript.
- bronlund 2y agoYeah, I think I'm in that category - I do struggle with JavaScript. The reason why though, is not just about how to do stuff in it, but the fact that I think it's an awful language for so many reasons. I kind of figured that some people have to love it for it to be so popular, but that makes me curious about what other languages you have used and how you think they compare?