socketify.py VS Django

Try BlackSheep | Kore | socketify | baize

When I see that: https://github.com/cirospaciari/socketify.py/blob/main/bench...

It's kind of hopeless, Python still needs to fork per core to get any performance? So if you have 8 cores you're actually running 8 processes, so 8 DB pool etc ...

The Bakery Demo project uses pip from Python for package management, and the Wagtail dot org website uses Poetry. The differences in connecting both were very subtle, with the bakery demo being the easier of the two. The overarching requirement was that you would have cloned the most recent version of Django from its GitHub repository. For the Bakery Demo, you would need a virtual environment and an installation of Django pointing to your local editable version via pip install -e /path/to/django. This virtual environment would contain your Django, editable version of Wagtail, and Bakery Demo website. For a poetry-based installation, modifying the project's pyproject.toml to point to a locally editable version of Django (or mounted volume of it, as in a potential case of containerization)

"settings.py" is your local configuration. The global default is still Chicago:

* https://github.com/django/django/blob/main/django/conf/globa...

Python + Django/Flask (rapid development, lots of libraries)

Tools: ChatGPT (free), Claude, Django, FastAPI, Node.js ChatGPT is great for planning and scaffolding. Claude shines when working with multiple files or complex refactoring. Together, they can spin up routes, models, authentication, and even database setup in record time.

Django framework: a powerful framework for building full-stack websites.

Django MVC done right (and battle-tested)

Django

Django, for example, has a template engine that allows you to define a template in HTML and render it with a context -- data usually sourced from the database via the Django view. However, with its filters and helpers, it is almost too powerful -- undermining the core idea of templating. The same goes for Ember.js, as well.

I am maintaining a Python codebase that is based on Django and Django REST Framework (DRF). The codebase uses Nix for development, testing, CI/CD and packaging.

In the world of Python web development, Django is considered a powerhouse. It is one of the oldest, yet most actively developed web frameworks with a vibrant developer community. Technically speaking, Django is a third-party Python framework for creating web applications that run on a server.