What you described is not a feature. Speed, or anything involving time, is an optimization, not a feature. Features are easy to add on to an application, but ti

What you described is not a feature. Speed, or anything involving time, is an optimization, not a feature. Features are easy to add on to an application, but time, once lost, can never be regained. Optimization usually requires fundamentally changes to architecture, and in the case of Django it is well-known that it is not for building fast or highly scalable apps. Functional Reactive Programming is far better for building high performance apps. Specifically, you are asking about code swapping which is something that is only used by developers during development, not during production. Most developers deal with such problems by getting faster hardware. And finally, even if Django development stops today and it never gets any new features, it is still an ideal tool for building apps that are in its sweet spot. And it is easy to supplement with things like Celery or RabbitMQ to communicate with scalable non-Django backends. Nothing to fear here, move along.