The capability exists, any dev team can take advantage if reqd of it, I am sure many may have in rare occassions. On the remote on the same LAN it will not be any different than debug is for eclipse / VisualStudio in dev.

In Insurance, Banking in my experience, it will be the last resort, unless it is critical and there is no other alternative to it but with production data set.

As I reiterated the reflection based data gathering that can enabled along with the superb exception handling capability it is something that is leveraged by smalltalk in production ( Unicycle reports in VA) and that is terrific for resolving bugs.

Reflection based tools like in Groovy can bring any Java system close to Smalltalk offers also in production as I have done in my work place.

On Thu, Apr 24, 2014 at 9:50 AM, askoh <askoh@askoh.com> wrote:

Thanks for reply. Are there cases of Java/Eclipse running in Production?
Similarly with VC++ / Visual Studio? They would be very very slow wouldn't
they?

I am referring to real use case of live debugging in Production servers. I
agree that this capability might not be attractive from point of view of
security and safety. But there are insurance and financial companies that
use Smalltalk. How do they view this capability? Do they forbid it totally?
If they allow it, how do they prevent abuse?

The pros is of course the easy of finding bugs and inspection of states
during production.

All the best,
Aik-Siong Koh

--

View this message in context: http://forum.world.st/Debugging-in-Production-Servers-tp4756136p4756141.html

Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.