4 ms·
> I thought Rust had other, better ways to create non-blocking code so I don't understand why to use async instead. 'async' exists because Python has that GIL
by otabdeveloper2 7y ago
> I thought Rust had other, better ways to create non-blocking code so I don't understand why to use async instead.
'async' exists because Python has that GIL bullshit and so Python programmers had to invent that fifth wheel of 'async programming'.
Programmers in other languages then got jealous because they, too, wanted a complex, unnecessary framework that pollutes the whole runtime and serves to differentiate regular programmers from 'rockstar' programmers.
And so async got fashionable and barely-literate coders now think async is magic performance dust that will automatically make your program run 1000% faster.
TL;DR - it's just fashion, give it five years and we'll be reading posts about how async sucks and that it's stupid legacy tech invented by bonehead dinosaurs.
- atombender 7y agoPretty sure the async/await support in C# predates Python. C# introduced it in 5.0, which came out in August 2012. The Python proposal (PEP 3156) for an async library was posted in 2012, the proposal (PEP 492) for async/await syntax in 2015, and implemented in Python 3.4 and 3.5 respectively, I believe. So C# predates Python by about 3 years. From what I can gather, Python was influenced by C#. But C# doesn't have a global lock, and that's not why it has async/await. Edit: Added PEP reference.