Very cool project. Like others say, it can be a pain to debug generated code in opal, clojure, elixir etc. But that's also true of the code generated by the C compiler. This is a chicken-and-egg thing. Either consumer hardware gets so fast that it's feasible to implement the language vm's in javascript or browsers will support other mechanisms for implementing them. But only when these projects are used by many people, which will happen when the code is easy to debug.
Caching is always faster than any web framework, so I don't think a faster web framework add much value to most companies. Choose a framework that makes it easy to add caching.
I assume you mean reverse-proxy caching and not back-end caching. Not all use cases are suitable for reverse-proxy caching. Blogs, news sites, and the like are very suitable. Applications that are heavily personalized or work with private data are unsuitable for reverse proxying.
Our test cases are explicitly concerned with exercising performance when reverse proxying is not suitable, for whatever reason. If reverse proxying works for your use-case, definitely consider using it.
Which is quite significant I would say. Suddenly we can no longer talk about what is objectively true and false, only what is subjectively useful. That last sentence is of course also neither objectively true nor false, just like this one. See it's a mess :)
It really depends on what is meant by "objectively true or false".
You're right that some statements within a formal system are true or false.
However, the theorem does imply that the behavior of the "world out there" (and any explanation of it) is either contradictory or not following a fixed set of rules.
So yes, we can state something to be "objectively" true or false but only if we're willing to use a contradictory explanation - which we usually are in the name of usefulness, not in the name of "absolute objective truth".
