And they also do so much more than the rrb.
And they also do so much more than the rrb.
To affirm otherwise only reveals lack of experience on the matter.
No Smalltalk environment has ever shown an error message about not being able to do edit-continue/hot-reload/whatever.... after doing a code change in a debug session.
Nor are they capable of transparently exposing their internal structures in the debugging session.
It's also something that you should probably never do, so not really that useful or worth considering as a major advantage.
https://www.jrebel.com/blog/limitations-of-hotswap
https://www.jrebel.com/learn/does-jrebel-support-my-framewor...
On the .NET, I will let Microsoft's own words speak for itself,
https://devblogs.microsoft.com/dotnet/introducing-net-hot-re...
> No matter how you use .NET Hot Reload please be aware that some changes are not supported at runtime and will prompt you with a rude edit dialog and require you to restart your app in order to apply. We’re still working on the feature and the documentation to detail what edits are supported. For now, start by reviewing our existing list of Edit and Continue (EnC) equivalent capabilities. Since Hot Reload is powered by EnC this will give you a good starting point for better understanding this new feature. For details see: EnC documentation.
In Smalltalk environments since the early 80's, it always works, there are no buts and ifs, or extra products to install.
As mentioned on another replies, it only shows you never used Smalltalk in production.
So... moving the goal posts now.