rsinger87
Joined 8 years ago
Joined 8 years ago
I connect online articles into discussion graphs and intersperse the top tweets about them. There are feeds that filter the discussions in different ways (exchanges among top authors, most discussed articles). It's also possible to see a specific discussion graph in its entirety, e.g. the discussion around Marc Andreessen's "It's Time to Build" essay: https://www.disqors.com/discussions/36672
I connect online articles into discussion graphs and intersperse the top tweets about them. There are feeds that filter the discussions in different ways (exchanges among top authors, most discussed articles).
It's also possible to see a specific discussion graph in its entirety, e.g. the discussion around Marc Andreessen's "It's Time to Build" essay: https://www.disqors.com/discussions/36672
Any feedback is appreciated!
Regarding other commentary on DRF: I wonder how many pain points result from trying to squeeze non-CRUD operations into DRF's ModelViewSet/ModelSerializer constructs? My company's approach has been to use that DRF magic for dumb CRUD resources and use plain function-based views for everything else, with the freedom to use Pydantic/Marshmallow/etc. This has made us very productive and I can't image having to write create/update/delete/get/list operations one at a time.
That said, I'm sure there are use cases that DRF isn't suited for and I would definitely look at FastAPI for new projects.
(Partly inspired by FastAPI)
I've borrowed ideas from the original API Star (https://github.com/encode/apistar) (before it was an OpenAPI toolkit) and FastAPI (https://fastapi.tiangolo.com/). Instagram engineering also had a recent blog post about how they do something similar with Django views (https://instagram-engineering.com/types-for-python-http-apis...).
Django's ecosystem (mainly DRF and django-filters) makes it very productive for me, but I find Django core to be lacking for developer ergonomics in certain areas.