An alternative question:
Why do we have to cache so damn much in Ruby and complicate the hell out of our infrastructure and code?
Because Ruby is slow.
An alternative question:
Why do we have to cache so damn much in Ruby and complicate the hell out of our infrastructure and code?
Because Ruby is slow.
What production website doesn't cache? You make it sound like it's a Ruby-only issue.
<!-- "breaking_news_1" background cached 07/16/2015 at 12:44 AM -->
So much for that theory.Just because we end up using that cached content to create a unique mix for each user doesn't mean that we don't cache. I think you misunderstand the process.
He's also mostly talking about our Elixir stack which is not our primary stack (though... we're hiring!). So it's a little bit of an edge case.
There IS less caching involved in our Elixir stack though - due to how it functions - so maybe that's where the confusion arose.
I don't think you should never do caching - just that is is non-trivial, especially once you move past a 15min-blog use case.
On the JVM, .NET, etc. statically compiled languages typically provide blazing performance, which allows you to selectively cache (i.e. where you really need it) vs. caching virtually everything because it's-just-so-damn-slow otherwise.