This is madness.
It’s tempting to prototype with it, but I can’t think of a single use case that wouldn’t be better served with another framework.
Django is not appropriate for production imo
Using flask and SQLAlchemy is worse in every way for example.
Django is the worst of both worlds. Not suited for small services, and not able to scale with large ones.
To your "load of crap" point, web development looked very different >10 years ago, Django was a lot better fit for that era. There is _zero_ reason to use it today.
Everything about Django is terrible.
The ORM is pretty trivially understandable and not magic at all.
The configuration is pretty straight forward and we'll documented.
The url routing is pretty good although it could be improved. It's a lot better than flask when you go beyond an MVP at least.
At a glance it seems to be effort directed towards the spirit of no-code, but the fact that people using these tools can code is the crux of this phenomena. It's a natural tendency to make things easier for ourselves and it's hard to know when to stop as a programmer.
As do some or many of the other competing technologies
I've been struggling to pick a stack that is super gd simple
But still let me do some SPA stuff for certain parts of the app
I might never actually write a line of code myself, but even so I want to easily be able to tell what my contractor is doing
And fix if necessary
Guide architecture
Maybe choose the initial stack in the first place
I'm overwhelmed at this point as to which stack I can use that will suck the least
Prob the biggest issue I have is just that '80%' number I often see thrown around with these new front end non-js js frameworks
That is, this will probably be able to handle about 80% of your use cases
Tf?
Noooooo
100%, please
At least, 100% of all up-to-medium-or-high complexity use cases
Not that I'm planning on rocket science
The question I want answered for any new tool like this is
Can it do basic UI interactivity like Duolingo?
Ok, then I'm in
Other than that
How to really compare this unicorn for django with livewire for laravel, inertia and or vue for everything, nuxt (which looks interesting), etc.
And my preferred contractor prefers rails, gd.
[1]: https://sockpuppet.argpar.se/ [2]: https://github.com/django-tenants/django-tenants
- why would you write every character to the backend? Do they really encourage storing UI state in the backend? - this approach fails greatly if a second user starts typing - it says "no need to learn an additional template language" but continues to define it in the input tag
It looks like the developers of this framework aren't too much into actual client development. Example code should be at least valid to a certain point.