HackerReposA FIELD GUIDE TO OPEN SOURCE
ProSponsor the shelf♧ 0
← Back to top all-time
encode
django-rest-framework
Python2012–2025
encode / django-rest-framework

django-rest-framework

Web APIs for Django. 🎸

Web Development
Explore on GitHubRead Hacker News discussions
13Distinct people
16Mentions
1Explicit recommenders
30.2KGitHub stars
REPOSITORY AT A GLANCE

What to know before exploring

What it is

Web APIs for Django. 🎸

GitHub

Where it is used

No documented product use was verified in the last source check.

What people are saying

I love Django but the REST API situation is embarrassing. I’ve been moving projects along for decades and the only things that have ever had to be completely rewritten are the…

miiiiiike used a recommendation phrase. One indexed comment matches. This is a phrase match, not a verdict.

No classified warning is attached to this page. Read the discussions before treating silence as approval.

Also in these discussions

No other repository is repeatedly linked in the same discussions.

This week on Hacker News

Nov 7–Nov 14 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/14/2026, 6:01:08 PM UTC.

No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.

Mentions over time

HN mentions by year16 dated mentions

Observed mentions: 2012-04-15 04:21:09 UTC to 2025-03-28 22:42:32 UTC.

01232012-01-01 00:00:00 UTC to 2013-01-01 00:00:00 UTC (exclusive): 3 mentions; 0 submissions, 3 comments20122013-01-01 00:00:00 UTC to 2014-01-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments2014-01-01 00:00:00 UTC to 2015-01-01 00:00:00 UTC (exclusive): 3 mentions; 1 submissions, 2 comments2015-01-01 00:00:00 UTC to 2016-01-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2016-01-01 00:00:00 UTC to 2017-01-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments2017-01-01 00:00:00 UTC to 2018-01-01 00:00:00 UTC (exclusive): 2 mentions; 1 submissions, 1 comments2018-01-01 00:00:00 UTC to 2019-01-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments20182019-01-01 00:00:00 UTC to 2020-01-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2020-01-01 00:00:00 UTC to 2021-01-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments2021-01-01 00:00:00 UTC to 2022-01-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2022-01-01 00:00:00 UTC to 2023-01-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2023-01-01 00:00:00 UTC to 2024-01-01 00:00:00 UTC (exclusive): 3 mentions; 0 submissions, 3 comments2024-01-01 00:00:00 UTC to 2025-01-01 00:00:00 UTC (exclusive): 1 mentions; 1 submissions, 0 comments2025-01-01 00:00:00 UTC to 2026-01-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments2025

Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.

View mention counts and date ranges
UTC ranges include their start and exclude their end. Select a period to filter the source evidence.
PeriodStart (UTC)End (exclusive, UTC)MentionsSubmissionsComments
20122012-01-01 00:00:00 UTC2013-01-01 00:00:00 UTC303
20132013-01-01 00:00:00 UTC2014-01-01 00:00:00 UTC101
20142014-01-01 00:00:00 UTC2015-01-01 00:00:00 UTC312
20152015-01-01 00:00:00 UTC2016-01-01 00:00:00 UTC000
20162016-01-01 00:00:00 UTC2017-01-01 00:00:00 UTC101
20172017-01-01 00:00:00 UTC2018-01-01 00:00:00 UTC211
20182018-01-01 00:00:00 UTC2019-01-01 00:00:00 UTC000
20192019-01-01 00:00:00 UTC2020-01-01 00:00:00 UTC000
20202020-01-01 00:00:00 UTC2021-01-01 00:00:00 UTC101
20212021-01-01 00:00:00 UTC2022-01-01 00:00:00 UTC000
20222022-01-01 00:00:00 UTC2023-01-01 00:00:00 UTC000
20232023-01-01 00:00:00 UTC2024-01-01 00:00:00 UTC303
20242024-01-01 00:00:00 UTC2025-01-01 00:00:00 UTC110
20252025-01-01 00:00:00 UTC2026-01-01 00:00:00 UTC101

What Hacker News says

1 sources
miiiiiike¡Mar 28, 2025Recommendation phrase
I love Django but the REST API situation is embarrassing. I’ve been moving projects along for decades and the only things that have ever had to be completely rewritten are the REST APIs and their tests. Piston, Tastypie, a custom framework, Django Rest Framework, and now what? Ninja? Shinobi? Each one has stalled out in its own way and all have failed to keep up with the rest of Django. (e.g. async REST API views should NOT require another, fourth-party, library.) I’ve been beating this drum for a decade now. Django needs “django.contrib.rest”. REST API frameworks have always been too important to leave to third-party maintainers. They need to be maintained in the core. I just want something that feels like Django and doesn’t change. Unfortunately I think Django has been debating something as fundamental as content negotiation, the first
Read the rest
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.
In Django's REST (Framework) Problem

MAKE YOURSELF AT HOME

A few shortcuts

/
Search the collection
?
Open this guide
Esc
Close dialogs and navigation

Your saved repositories and interests stay in this browser.