learndb VS django-ninja

I ran into the same problem while building https://learnawesome.org/ . Forget the broad class of "learning resources", even the "books" category doesn't have a usable unique ID. Not everything gets an ISBN for example. There's also the ambiguity between a "work" and an "edition" of a work.

This is probably why OpenLibrary supports mapping of books with 40+ identifiers: https://github.com/internetarchive/openlibrary/blob/master/o...

I loved using Svelte for these two open-source projects but haven't yet an opportunity to use it at work:

- An SVG-based graph dataset editor: https://codeberg.org/nilesh/grapher

- A curated collection of educational resources: https://github.com/learn-awesome/learndb

Compared to React, developing with Svelte felt like a breath of fresh air.

A couple of my tools that don't require signup:

- Grapher (a visual editor for graph datasets with features like nested nodes, custom attributes on nodes and edges, and export in Cytoscape JSON or SVG format. Accessible at: https://grapherx.netlify.app/

- LearnDB (A curated collection of links to educational resources organized by topics, formats, reviews and other tags). Accessible at: https://learndb.vercel.app/

For those who're curious, the app is mostly completed - although the dataset could be enriched further. You can try it online here: https://learnawesome.vercel.app/ but it's designed to work best when run locally: https://github.com/learn-awesome/learndb

Django Ninja [1], it forever changed how I write Django project, in a way so elegant and productive.

[1]: https://django-ninja.dev/

Django Ninja is a RESTful wrapper for Django, while UtilMeta Python Framework uses a more concise declarative ORM Schema for Django and other future-supporting ORMs like sqlachemy and Peewee to build RESTful APIs more efficiently, and supports not only Django but all Python mainstream frameworks like Django, Flask, Starlette, FastAPI, Sanic, Tornado, etc.

I can't recommend [django-ninja](https://github.com/vitalik/django-ninja) enough. It's an easy to use, extremely fast, typed API for django. I've found it to be better in almost all aspects when compared to djangorestframework.

It's gaining popularity but is still widely unknown.

> The only place I really see Django at large companies is as an api using DRF or something.

This is not a bad thing. Using Django as an API backend is amazingly fast in terms of development time, especially with modern frameworks such as django-ninja [1].

Just use the built-in ORM to create models, write your endpoints, and use the built-in admin interface to play with the database if you don't have endpoints for everything.

There is also a less known feature of Django called admindocs [2], which automatically generates a human readable, hyperlinked documentation for your models and relations between them.

[1] https://django-ninja.rest-framework.com/

[2] https://docs.djangoproject.com/en/4.2/ref/contrib/admin/admi...

Personally, I also prefer django-ninja to DRF.

Actually that's not fully true. If you mix async and sync codes in django-ninja there will be some errors. Where's the proof ? django-ninja doesn't support async auth

Subscribe to this issue :D

Also recommend Django-Ninja. It basically reimplements fastapi's type and decorator-based API construction, but embedded directly in django so you have access to django's ORM and middleware library.