4 ms·
I'd love to hear your suggestions for changes we could make while keeping it somewhat WSGI-compatible. It took a few years to refine it to where it is now, so i
by andrewgodwin 7y ago
I'd love to hear your suggestions for changes we could make while keeping it somewhat WSGI-compatible. It took a few years to refine it to where it is now, so it's not like we just threw something at the wall.
- 904baf11 7y ago> while keeping it somewhat WSGI-compatible There's the problem. WSGI is fundamentally flawed too - it could also be using generators for a two-way communication channel instead of stringly typed callbacks. In a world where Python has optional static type hints, it would be nice to have concrete objects passed too.
- orf 7y agoCan you expand on the stringly typed callbacks? Where are they required? Are you referring to string keys in a callback dictionary, in which case stringly-typed seems a bit of an odd choice of words.
- 904baf11 7y agoCalling the receive async function gets you a dictionary with a string type key, which defines the layout of the dictionary. It's not nice.
- jxcl 7y agoIt's much easier to say stuff sucks than to actually get a huge project like this shipped. Thanks so much for your hard work Andrew + team!