I think the article misses one of the central points behind having a compiler: It's not about managing memoization in an automated way - even though that's als

I think the article misses one of the central points behind having a compiler: It's not about managing memoization in an automated way - even though that's also very nice - but rather the ability to compile closures and package them. This way you can automate hydration. The main pain point with SPAs is that you're generating huge packages since you have to ship all of your code at once. Having a compiler gives you the ability to do tree shaking on a per-component basis.