In the original article, he indicates Swift, Rust, and Go are tomorrow&#x27;s languages.  The issue really is that the level of support in the various frameworks, the eons of bug-crushing and feature additions, and the libraries available, are going to be behind for some time.  This is why I&#x27;d still gladly pick Django today.<p>What is &quot;the future&quot; isn&#x27;t really so interesting as what is productive.<p>Yes, performance matters a bit, but development time is usually much more expensive than adding a few nodes to an autoscaling group, and not worth the cost of using less fleshed out libraries.