3 ms·
My theory is that JavaScript programmers who were forced into thinking this way for decades with their single-threaded runtime have infected other languages wit
by skywhopper 2y ago
My theory is that JavaScript programmers who were forced into thinking this way for decades with their single-threaded runtime have infected other languages with the idea that this style of coding is not only good but furthermore that it needs to be explicit.
Thank goodness we have wiser language developers out there who have resisted this impulse.
- Erem 2y agoDidn’t async/await originate in c#?
- explaininjs 2y agoF# first actually. Then C#. Then Haskell. Then Python. Then TypeScript. Parent just has an axe to grind.
- jerf 2y agoasync/await may have originated as keywords in C#, I don't know, but the programming style itself is ancient. Almost every GUI ever written is programmed in the style. Network servers were written this way back when threads were just a fever dream of academics yet. The entire Mac OS ecosystem prior to OSX had to be written in this style because time was cooperatively shared across the entire OS. This is one of the most blatent "failure to learn from our history" debates I know of, when people act as if the question started with Javascript just a few years ago, when in fact the programming community has experience with this style that predates when most of us were born. I'm getting to old fogey myself and it still predates my 1978 birthdate. I was never even tempted to get into Node because I'd already made an async/await-style mess in Perl before Node was even released, and the mess had everything to do with the programming style and little to do with Perl qua Perl, and the libraries I used were already old and well-established then, if not outright long in the tooth. There is nothing new about this, except keywords.