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
Django is perfectly capable. I'd use Phoenix for its scalability and performance, if it were me, but I've built large-scale projects in Django before, and it worked well.
TLDR: C++, WASM, and some form of GRPC with C++ on the server side as well. Because you need a language that's fast, can contain high complexity and large programs without collapsing (which is a short list of languages) and can work fast for the bits that need speed.
It really depends on how it’s used. I love Django in certain specific situations. You know that saying though about when you have a hammer, everything looks like a nail…
ffsm8|24 days ago
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
superze|11 days ago
spwa4|24 days ago
innocentoldguy|24 days ago
sgt|24 days ago
KingOfCoders|24 days ago
speedgoose|24 days ago
spwa4|24 days ago
TLDR: C++, WASM, and some form of GRPC with C++ on the server side as well. Because you need a language that's fast, can contain high complexity and large programs without collapsing (which is a short list of languages) and can work fast for the bits that need speed.
shimman|24 days ago
cbdevidal|24 days ago
_el1s7|23 days ago