Whenever i start a new web-app from a template or use some new development tool, one of the first things I do is disable or remove everything connected to “Hot Module Replacement”. I never wrote down every reason in one place before, but now that I am preparing to release a tool of my own, I need to document the decision appropriately. At the same time this article is a request to challenge my points in case i did not think of all use cases or reasons for HMR, so please do comment!

It’s weird that I hate js HMR…


I think that RPC protocols and REST protocols live on very different abstraction levels and should not be compared like alternatives. This is maybe the main problem I have with the current wave of REST criticism. If we just accept that no one will be happy to force an RPC kind of API through REST, a domain specific API that was made for resource synchronization, the discussion could be more productive.

As programming languages use functions and RPC is a way to use those through a network of some kind, of course RPC APIs are the most generic and transparent…

Jan Friedensreich

Get the Medium app

A button that says 'Download on the App Store', and if clicked it will lead you to the iOS App store
A button that says 'Get it on, Google Play', and if clicked it will lead you to the Google Play store