This is just a tooling problem and architectural pattern which can be done in Angular 2 and even…

I think this is not about whether it’s possible to do hot reloading with Angular or not — of course it’s possible. You can also make a regular JS/jQuery app hot-reloadable by leveraging the raw Hot Module Replacement API.

But the question is whether it’s readily available and easy to use or not.

With React, you enable a flag in webpack-dev-server and configure some Babel transforms, and it’s done (although that’s quite some work already). So I feel that for a new framework to compete, it should be as easy or easier to set up hot reloading.

Hot-reloading became a mainstream thing in React, and I now see that as a baseline for future JavaScript frameworks, and so I expect future frameworks to also have first-class hot reloading support.

Like what you read? Give Thai Pangsakulyanont a round of applause.

From a quick cheer to a standing ovation, clap to show how much you enjoyed this story.