4 ms·
The issue is that many developers that are coming from synchronous programming don't get asynchronous programming. They could both improve the code by not writi
by markandrewj 7y ago
The issue is that many developers that are coming from synchronous programming don't get asynchronous programming. They could both improve the code by not writing blocking code, and also using something like the cluster module (https://nodejs.org/api/cluster.html https://nodejs.org/api/cluster.html).
- crazygringo 7y agoI get that. What I don't get is how nobody treats it as an issue when developers coming from Python or Java to C don't get pointers. The assumption is that you learn. But for some reason, people think it's "OK" to not get async, that it's the language's fault rather than the programmer's. That's what I don't understand. It's like a different cultural standard gets applied.
- markandrewj 7y agoI agree with you, but I think many developers get reluctant to change when they have been doing something one way for a long time, especially if they feel that one way works fine. I can also understand the position, as sometimes it can be fatiguing when technologies are constantly changing. For this project though, if they are actively going to avoid asynchronous programming, they may have been better off choosing a synchronous language.
- ubu7737 7y agoThere is simply no excuse for this. You are a software engineer or you are not, the cadence of change is part of the technology aspiration. I have no patience for persons who don't belong to the discipline.