3 ms·
Dynamically reloading classes is a nightmare in production systems. I'm not a .NET guy by any means, but one thing that it has that others could use it code sig
by delano 16y ago
Dynamically reloading classes is a nightmare in production systems. I'm not a .NET guy by any means, but one thing that it has that others could use it code signing. This is precisely the opposite of dynamic reloading and it's much more valuable.
The win-win is leveraging the power of a dynamic language at development time and the power of something like the JVM at production time.
- akeefer 16y agoYeah, I agree that it's a nightmare in production, but it's absolutely indispensable in development situations where you can tolerate the occasional weirdness or failure. If you're developing a server app (or a thick-client app), avoiding a sever restart every time you change anything is a huge, huge win. And again, it's not like it's not implementable: there's already an implementation, for the JVM, that works.
- delano 16y agoThat's true. It would be helpful to have dynamic reloading as an option with the JVM.