With regards to Deep Learning, a recently released Keras backend[0] actually supports OpenCL with direct validation on a few AMD cards. I've been playing around with it for the past week or so and so far have had no issues with it, though I'm admittedly not doing anything too serious.
Yes, in a cooperative async model anything which would block will stop progress of every coroutine, so you would need an async version of the ORM library for this to work. When you await something, you're telling the event loop to stop running this coroutine, and wait for something (usually IO) to happen before resuming execution. Because of this, if you block on IO without using await, the coroutine doesn't know to yield and will simply pause; thus execution of every single coroutine is blocked.
This leads to a sort of infectious need to make everything async as even a single non cooperating coroutine can bring the whole show to a halt. It's essentially the red vs blue function problem of Python. However, there is actually a nice alternative, gevent. gevent will monkey patch all functions in the standard library which would block, e.g. reading from a socket, attaching an implicit await to them. If the author has used gevent, the example Django code would actually work as expected, since the code would execute until the database connection was written to/read from and then immediately await.
Either way, async IO is still a somewhat tricky thing to understand and get right. It took writing a non blocking event loop with epoll in my case to really grok what was going on under the hood of something like asyncio.
Having used eBPF/kprobe for work, the main advantage over a precompiled kernel module is convenience. It's much easier to write a C file which hooks a kernel function, then reports that back up to a python script than it is to build and maintain a kernel module and have that talk to some higher level code.
Although I've never seen the Great Barrier Reef, I was recently in Belize and snorkeled around its Barrier Reef. It was painfully obvious that the reefs were extensively bleached(though still quite beautiful). It's quite shocking to think that 30 years ago the reefs looked completely different from now and in another 30 years may not even be around. I hope that in the future we won't be reduced to having to point to pictures in a book if people want to witness the beauty of nature but this seems increasingly inevitable. What a shame.
> Something I would write in Ruby in 10 days takes 2 months in Go.
Have you looked into Elixir? It has Ruby like syntax, but uses an actor model for concurrency(it runs off of the Erlang VM). For handling concurrent tasks it tends to benchmark around Go's speed, but is much nicer to do things in. While it is admittedly immature, the ecosystem still has a decent amount of packages and the tooling isn't bad.