Yep. When you&#x27;re talking about &quot;web development&quot; and your first argument is about &quot;concurrency&quot;, your odds of doing it wrong are likely very high. Learn to profile, learn to cache appropriately, learn to set up data pipelines based on access patterns. Many of us who have learned the dangers of threading the hard way consider it a last resort, and just because you have wonderful primitives like goroutines and channels doesn&#x27;t mean you shouldn&#x27;t think first. I&#x27;m inclined to link to JRuby&#x27;s first rule of writing concurrent code: <a href="https:&#x2F;&#x2F;github.com&#x2F;jruby&#x2F;jruby&#x2F;wiki&#x2F;Concurrency-in-jruby#concurrency_basics" rel="nofollow">https:&#x2F;&#x2F;github.com&#x2F;jruby&#x2F;jruby&#x2F;wiki&#x2F;Concurrency-in-jruby#con...</a><p>Also, it&#x27;s relative newness combined with the fact that it is on the lower level of things means that basic tasks that have been iterated to precision on other platforms are still very raw around the edges and require quite a bit more boilerplate, which is not at all suited to almost all &quot;web development&quot;.<p>I know, I know. &quot;But it&#x27;s faster!&quot; I&#x27;d take a clean, cohesive system that can scale horizontally even if it takes me 5 times the servers of my entire-system locking clusterfuck that makes me guess about data.<p>There is probably an interesting metaphor to be made that is corollary to the adage about the hammer, something about how if you give that man a screwdriver he starts looking for nails to pound with it?