3 ms·
The only reason I say that is that every project doesn't need hot-reloading. It's one of those things that is only recommended where you need it. Just think of
by brightball 9y ago
The only reason I say that is that every project doesn't need hot-reloading. It's one of those things that is only recommended where you need it.
Just think of it in the same way that you don't need every available jar file for a Java project. The capabilities of the system are expansive, but not always called for.
Distillery is the main deployment related library out there for Elixir and reduces hot reloads to a an argument on the build.
https://github.com/bitwalker/distillery/blob/master/docs/Walkthrough.md#building-an-upgrade-release https://github.com/bitwalker/distillery/blob/master/docs/Wal...
- KallDrexx 9y agoHot reloading also adds a ton of hidden complexity to your projects, since you essentially have to be very careful about every module boundary (as my understanding is that every time code goes from one external module to another non-OTP module it uses the new version of that new module, and thus any non-backwards compatible signature change will crash the process). You can't really casually support hot reloading and need to fully commit to it, unless you don't care if things fail when you hot reload at which point you might as well just do a full reload and keep confidence in the system.