Comments on: Smalltalk a world of living Objects http://isaiahperumalla.wordpress.com/2008/06/10/smalltalk-a-world-of-living-objects/ Thoughts on Object Oriented Design, Smalltalk, Behaviour Driven Development and .NET Thu, 26 Nov 2009 06:23:54 +0000 http://wordpress.com/ hourly 1 By: mo http://isaiahperumalla.wordpress.com/2008/06/10/smalltalk-a-world-of-living-objects/#comment-56 mo Wed, 05 Nov 2008 04:03:01 +0000 http://isaiahperumalla.wordpress.com/?p=11#comment-56 Wow! What a great introduction to Smalltalk. I'm really interested to read more about it. Especially from an OO perspective, and how lessons from Smalltalk can be brought in to the realm of .NET. Thanks, Mo Wow! What a great introduction to Smalltalk. I’m really interested to read more about it. Especially from an OO perspective, and how lessons from Smalltalk can be brought in to the realm of .NET.

Thanks,
Mo

]]> By: Matt Dunn http://isaiahperumalla.wordpress.com/2008/06/10/smalltalk-a-world-of-living-objects/#comment-54 Matt Dunn Thu, 14 Aug 2008 16:47:01 +0000 http://isaiahperumalla.wordpress.com/?p=11#comment-54 Kent Becks seminal quote on image-based vs file-based development was "Imagine, putting source code in files! How quaint.", says it all really :) Cheers, Matt Kent Becks seminal quote on image-based vs file-based development was “Imagine, putting source code in files! How quaint.”, says it all really :)

Cheers,
Matt

]]> By: Srikrishna http://isaiahperumalla.wordpress.com/2008/06/10/smalltalk-a-world-of-living-objects/#comment-52 Srikrishna Thu, 03 Jul 2008 14:14:32 +0000 http://isaiahperumalla.wordpress.com/?p=11#comment-52 Wonderful article. I was a smalltalk developer for long time over 10 years. Currently i work on java application which is rewrite of smalltalk. We still use smalltalk to refer code and for other purposes. I still love to do work smalltalk because of ease of development and debugging a big time booster. We write code in debugger which gets picked up immediately. That saves lot of time to compile and deploy cycle which is needed for java. The best example of image and smalltalk objects never die is: Recently, i had to debug something in smalltalk, i had breakpoint in the middle of the process and forgot to resume. I went back to smalltalk image after 3 or 4 days and i could resume the process which worked beautifully. Also, it is a big time confidence booster for any developer. I believe it forces to learn more into internals and makes you think of objects which is very good thing in long term. Today, i was talking to my long time friend who was a smalltalker. Now he works in .NET and flex applications. I asked him how he was doing with flex development and told him it is kind of difficult to fix problem without external help. He told me, most of things can be fixed after working in Smalltalk. I think the reason, you are allowed to see the code even the system code except for VM (Virtual machine). lubos -- I guarantee, It will be a good experience for you. Wonderful article. I was a smalltalk developer for long time over 10 years. Currently i work on java application which is rewrite of smalltalk. We still use smalltalk to refer code and for other purposes. I still love to do work smalltalk because of ease of development and debugging a big time booster. We write code in debugger which gets picked up immediately. That saves lot of time to compile and deploy cycle which is needed for java.

The best example of image and smalltalk objects never die is: Recently, i had to debug something in smalltalk, i had breakpoint in the middle of the process and forgot to resume. I went back to smalltalk image after 3 or 4 days and i could resume the process which worked beautifully.

Also, it is a big time confidence booster for any developer. I believe it forces to learn more into internals and makes you think of objects which is very good thing in long term.

Today, i was talking to my long time friend who was a smalltalker. Now he works in .NET and flex applications. I asked him how he was doing with flex development and told him it is kind of difficult to fix problem without external help. He told me, most of things can be fixed after working in Smalltalk.

I think the reason, you are allowed to see the code even the system code except for VM (Virtual machine).

lubos — I guarantee, It will be a good experience for you.

]]> By: lubos http://isaiahperumalla.wordpress.com/2008/06/10/smalltalk-a-world-of-living-objects/#comment-45 lubos Wed, 11 Jun 2008 14:48:59 +0000 http://isaiahperumalla.wordpress.com/?p=11#comment-45 Wow, thanks for this introduction. I'm going to research about this language right now, it's kind of refreshing concept when you compare it to Java or C# Wow, thanks for this introduction. I’m going to research about this language right now, it’s kind of refreshing concept when you compare it to Java or C#

]]> By: markus http://isaiahperumalla.wordpress.com/2008/06/10/smalltalk-a-world-of-living-objects/#comment-42 markus Wed, 11 Jun 2008 07:02:18 +0000 http://isaiahperumalla.wordpress.com/?p=11#comment-42 But the biggest difference is that Ruby is a "scripting" language (in the sense that you can use it for tasks perl used to be) and came from a very different area. I don't think it will thus ever become similar to Smalltalk, no matter the VM part (though its cool) It is interesting to see the two worlds converge in practise (not only about objects & messages) But the biggest difference is that Ruby is a “scripting” language (in the sense that you can use it for tasks perl used to be) and came from a very different area. I don’t think it will thus ever become similar to Smalltalk, no matter the VM part (though its cool)

It is interesting to see the two worlds converge in practise (not only about objects & messages)

]]>