Obviously nothing is stopping me, that's not the point. I was just highlighting the fact that in my opinion the DX of parts of Django is inferior compared to the JS frontend ecosystem. As the Django community, I think this is something we should have an eye on.
I love Django and have been using it for many many years. Lately, however, I’ve been finding it increasingly difficult not to be annoyed by some aspects of the developer experience. For example I’d choose React + Typescript over Django templates any time of the day.
I have been meaning to develop the exact same thing (I was going to call it lastsforever.store), but just never found the time. Thanks for putting this out there. I'd say it's still a little rough on the edges, but should have potential.
What I honestly dislike, however, is to see all the google tracking going on there... is that really necessary?
I'm working on a webapp that enables people to include non-smart (i.e. pdf or paper based) data about their carbon footprint into https://north-app.com/.
The alpha version is available here: outsmart.superservice-international.com/
I studied agronomy and am well familiar with Berrey's work. Nonetheless, I was sucked into technology's vortex and am nowadays working as a software engineer. In my dreams I’ll go back to farming one day, but if I’m dead honest that’s probably never going to happen. We’ll all eat lab food pretty soon, hopefully at least for the better of the environment.
Similar experience. While the django rest framework is a joy to use, I’m almost inclined to call graphene a headache. Poor docs, lots of spread our third party extensions that really should be in the core... I have even found myself wondering if the stark discrepancy between drf and graphene reflects or hints at a decline of django as a framework.
Your app is very impressive from a technological point of view.
However, I would like to point out that while there are ~400 million dogs in the world, there are only ~200.000 wolves left. Things are getting out of hand.