Well, heh. I'm about to release a preview of it, possibly this evening; it is lacking in features and documentation an isn't yet alpha quality, but the examples and basic 3d stuff works. Describing it properly is going to require a full manual or me finding someone who gets it and is better at technical writing: the concept is fine, if you get something from "directed acyclic graph of audio processors", but otherwise needs informative examples/tutorials. It's honestly not that bad, and the Python examples I'm going to put up are pretty clean and informative. I've just spent so long thinking about graphs that I can no longer think of things like Libaudioverse in any other context, making writing about them in a less mathematical way difficult. It's incredibly easy to use, at least in my opinion, just hard to document without saying "here, have some sample code". In a sentence, it's basically Pyo but fast enough to be useful in games and not necessarily GPL. Commercial licenses will happen, as I've been careful to be the only coder. I wish I were a lawyer because then I'd have copyright agreements and could get help from others. I'm the only coder I know who knows DSP at all and would be interested so that's kinda a moot point anyway.
Django doesn't hide things, in that you can access most of HTTp. What Django is doing is providing a framework to say "if the user asks for /blog/posts/june2014, then call the get_archive function" and "whatever the get_archive function returns needs to go out as HTML". It's not quite that simple, in that you also use Django for web API creation (a whole second beast and I can't talk much about it for lack of experience). What's going on with Django is that Django speaks HTTP on your behalf, ending the connection appropriately when the function returns and figuring out what to call. It also gives you a *ton* of free web behavior, i.e. you've got a full and capable (and accessible, actually) database editor in about 5 minutes-just as soon as you define the models. It also provides a lot of nice stuff for database access/management and rendering templates-but neither is specific to HTTP. I don't believe Django uses Twisted or anything under the hood, but would need to read its actual code to check. In Twisted/whatever, you'd have to implement the HTTP protocol yourself; alternatively, call out to a library that accepts incoming data and interprets it for you.
Asyncio is built into Python 3. Python 2 versus Python 3 is a big topic, and I'm not going to judge you one way or another. There is a backport to Python 2 called Trollius that you can install. As far as I can tell, Asyncio gets the best of the Twisted world and the best of the Gevent world at the same time, plus a few nice things that neither of them offer. If you go far down the online game creation world in the direction of Swamp, you'll be writing your own protocol, so arguments about supporting Obscure File Transfer V 1.0 are kinda out the window. But yes, learning one of them is probably a pretty good idea. My argument about things like Pod6net is that they are lacking maturity: lots of people have used Twisted and Gevent, and the people who developed Twisted and Gevent brought a huge amount of "how we went wrong" to the Asyncio table. When you start talking about obscure packages like this, you can sometimes find that you're giving up a lot of nice stuff-for example, tutorials on how to do complex things and other libraries that complement the main framework specifically.
Also, Wysiwyg tends to be pretty inaccessible in my experience. Is this for browser games or actual MMO-style things? If the latter, you're going to hit the roadblock of not having a trimesh editor, I suspect. But I'm curious to see.
Twitter: @ajhicks1992