What issue do you have with Django?
This is not a situation where you'll have thousands of people editing the same document, that'd be insane with Django for sure - but at general collaboration tooling with <100 (random number I made up) editing, Django is unlikely gonna be the bottleneck
My issue is latency. Django is extremely slow.
Does it really need explaining why Office 365/Google Docs cannot be written in Django?
Yes
This is very obvious.
What part of your document editor needs to be backed by a relational database?
Why use an MVT system if you don't need the Model part of it?
https://github.com/suitenumerique/docs/blob/main/src/backend...
I see, in your broad and experienced mind, document editors don't have users, permissions, and the whole document management itself, comments on lines/threads, reactions on comments
Seriously, theyre all as cookie cutter perfect usecase for Django as you can get, but I guess you haven't actually thought about the domain and just wanted to take a dumb on other devs with intern-to-junior level insights
You don't necessarily need that to get these things...
Obviously, you don't need the model abstraction for any software, ever. It is just more or less suited for a domain.
And in this case, as would be obvious from thinking about it, the only part it's not suited for is the live syncing of the text edit on the frontend, which is one one small part of the whole.
Storing the text documents themselves in a relational database is itself a terrible idea.
It's not a bad idea, generally. it depends on the implementation. If you're updating it multiple times per second, then yes, it's a bad idea.
Now go check if they're doing it or you're just suggesting from the dunning kruger symptom.
Would love to hear that explanation why it is IMPOSSIBLE (not that Rust would be faster or use less resources but why it can’t be written)