tivolo

There is a comparison between Live++ and Visual Studio's Edit-and-Continue here: https://liveplusplus.tech/faq.html

In our (and many of our customers') experience, E&C doesn't work for anything larger than simple toy projects. It just isn't reliable.

On top of that, I think its biggest shortcoming is that E&C doesn't work with optimizations at all (this is documented), and is tied to the Visual Studio IDE, which not everybody uses.

I would really like to make Live++ available for Linux one day - it's been asked for a few times already.

There is a comparison between Live++ and Visual Studio's Edit-and-Continue here: https://liveplusplus.tech/faq.html

In our (and many of our customers') experience, E&C doesn't work for anything larger than simple toy projects. It just isn't reliably.

On top of that, I think its biggest shortcoming is that E&C doesn't work with optimizations at all (this is documented), and is tied to the Visual Studio IDE, which not everybody uses.

Note that it's not exclusively targeted to game development, it's just that most companies using Live++ are in the gamedev space. There's no reason not to use Live++ on other non-games Windows applications, and we do in fact have customers outside the games industry.

Not having globals at all or restoring them on reload isn't exactly "don't need anything complicated for this", especially considering using a generic hot-reload tool on AAA 5M+ LOC projects.

There's no easy way to retrofit hot-reload into these large codebases. Sure, it's easier if you design everything up-front with hot-reloading in mind, but it's still going to be hard to convince developers that they cannot use globals, thread-local storage, function statics, or other inherently stateful things that just won't work with DLL reloading.

The latest post in the series finally goes into details about the lock-free implementation of the work-stealing queue.