4 ms·
It's not that caching itself is complicated, but rather one more layer to keep track of/thing that could break. On the JVM, .NET, etc. statically compiled lang
by virtualwhys 11y ago
It's not that caching itself is complicated, but rather one more layer to keep track of/thing that could break.
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.