django-rest-framework

step towards supporting this is core, for over a decade now. If it’s a money issue I’d be thrilled to donate $5k tomorrow. I also have a JWT auth package that I could contribute. Unfortunately there appears to be little to no appetite for any of it. I've considered donating to encode, DRF's parent organization, most of their effort is directed towards Starlette, an async framework that competes with Django. It even powers FastAPI. Encode has put enormous effort into making everything but Django Rest Framework support async. I don't get mad about much in open source but this has been an obvious risk for over a decade. The steering council should should have spotted the iceberg and started turning the ship long ago. Removing the bug tracker and burying the announcement that the project is looking for a new maintainer in an unrelated PR comment is a too much: https://github.com/encode/django-rest-framework/pull/9186#is... > The issues backlog had become overwhelmed to the point that it presented as a smokey all-boys club. Unless we've got a welcoming & diverse environment to work in, there's no point in doing the work. It'd be damaging rather than constructive to allow that to continue. The project is open to new maintainership & genuine parties are welcome to reach out. [Two Hearts Emoji — https://emojipedia.org/two-hearts] At the very least I should have found out about this from an announcement, not by rummaging around after checking in on the status of a long-standing bug and getting a 404.

c support https://github.com/psf/requests - Top package for GitHub REST API, no async support https://github.com/PyGithub/PyGithub - …on and on… What’s the point of my nice FastAPI server if nothing internally can use async/await? How is everyone else doing this? /rant

a breeze, truely. Not only are there a ton of libraries that already do it, there are even SAASes that will do it for you for a fee. If you are really unable to come to terms with this, you can use react.js, which solve the SEO indexing issue completely. 2) If the only thing that you are doing on the site is measuring page loads then your site either lacks interactiveness completely or you aren't measuring everything you should. You aren't measuring to where a user left your site (and incredibly important metric) or any action he does (assuming there is any he can do) that isn't navigation. With Angularytics (and a thousand other libraries) adding analytics is maybe 5 lines of code, and you get declarative analytics on any link you want. 3) This site's js is neither minimized nor concatenated, so I'm not sure what build tools you need for angular either then the ability to serve static content? But in any case it's js, you are going to need to minimize and concatenate it at some point for performance, doesn't matter if you use a fat client or some custom jQuery plugin. Even with Grunt, though I don't like it very much, the build file is maybe 10 lines long, and the build process takes miliseconds. 4) And the alternative is what? using manual QA on every build? You have a website with even minimal interactivity you are going to need to use a browser based testing solution. Karma is a breeze, and with the new setup, the only thing you need to install is node and karma. Takes exactly 3 seconds, and you get one of the best isolated unit testing framework for client side code. Angular is actually built around the ability to unit test it. 5) So your saying that the solution to slowness is to have 43 unique resources loaded and rendered on every navigation? Page reload slowness is one of the major hassles that Ajax, and fat clients as a consequence, are trying to overcome. Your site takes, to me, about 3 seconds to load from page to page (6 seconds to finish rendering), there is obviously no wait time indicator that you can add and no tricks to minimize this. Not to mention that rendering is slow, and server-side rendering is not only extremely slow it can also cause parallel load which will make things worse. If you don't care about your speed it doesn't matter what framework you use. For the sake of this you are losing interactiveness, speed and lower bandwidth to name just a few.