Hacker News new | ask | show | jobs
by pjmlp 646 days ago
This the bare minimum, https://liveplusplus.tech/

Also supports is kind of relative,

"CHR is very new and experimental feature of the engine, it is based on wildly unsafe functionality which could result in memory corruption, subtle bugs, etc."
2 comments
bendhoefs 646 days ago
Why is that the bare minimum?

I also think that doc page is a little old. The feature is over 2 years old now and hot reloading is inherently "unsafe" in any compiled language. It's just letting you know that Rust's safety guarantees might go out the window if there are bugs in the code that handles hot-reloading.

link
pjmlp 646 days ago
Because that is what existing game studios expect, as shown by their customer list.

Also that was only one example, there are other similar ones.

link
desumeku 644 days ago
Funnily enough, Mojang is on that list, and I remember recently watching a video[1] of Notch hot-reloading code while developing Minecraft, except it was with Java and I'm sure he didn't pay a dime for the ability to do that.

[1] - https://youtu.be/BES9EKK4Aw4

link
pornel 645 days ago
That live reload probably already works with Rust — they say they don't parse any source code, and instead analyze the compiled binary and debug info.
link