4 ms·
> Make it web scale. Oh god whenever I read/hear that it reminds of the ridiculously funny video about nodejs and Apache servers. [1] [1]. https://youtu.be/b
by fzil 5y ago
> Make it web scale.
Oh god whenever I read/hear that it reminds of the ridiculously funny video about nodejs and Apache servers. [1]
[1]. https://youtu.be/bzkRVzciAZg https://youtu.be/bzkRVzciAZg
- xcambar 5y agoGlad you liked it! The reference to this series of videos was intended of course. The specific video I had in mind was actually https://youtu.be/b2F-DItXtZs https://youtu.be/b2F-DItXtZs Enjoy!
- fzil 5y agoOh yes! I’ve seen this before as well. Should’ve guessed it’s this considering we were talking about sql.
- usrbinbash 5y agoThis video is just gold. asyncio is probably one of the worst things that happened to programming in the last 2 decades. It's essentially a step backwards, to the technology of the 90s (cooperative multitasking), when a badly written text editor could cause an entire OS to freeze.
- joconde 5y agoCurious why you think that. We have an app that does computation using thread pools, and moving from manually-created threads to asyncio has made it much more efficient and robust. Some advantages: cancellation and error handling are trivial, there's no need for error-prone thread coordination, threads don't have to waste time waiting on locks (because we use asyncio sync primitives instead, so we don't submit work to a thread pool unless it's doable right now with no wait). Of course, it depends on the tasks being written correctly. But "don't block the event loop" is a much easier rule to follow than "don't deadlock these 10 different threads that share queues and locks". We didn't write an entire OS with it, but I don't think that was ever the point of asyncio, was it?