That's what I was trying to express: when you already program with another language, you can easily understand a new language, but you have big assumptions that will slow you down. I just pointed out the most important parts that surprised me when I learned Smalltalk. On Sat, Feb 5, 2011 at 7:28 PM, Schwab,Wilhelm K <bschwab@anest.ufl.edu> wrote:
That comment requires elaboration or at least some examples of what one can/should do, but getting past that is a big hurdle in learning Smalltalk. Â Things old to us can be earth shattering: something as simple as creating a new package (or even just a new class or a new class method somewhere, etc.) vs. writing a whole new program in some other language.
________________________________________ From: pharo-project-bounces@lists.gforge.inria.fr [pharo-project-bounces@lists.gforge.inria.fr] On Behalf Of John McIntosh [johnmci@smalltalkconsulting.com] Sent: Saturday, February 05, 2011 5:33 AM To: Pharo-project@lists.gforge.inria.fr Subject: Re: [Pharo-project] Smalltalk for engineers
Casual mention of iPhone port, always helpfull
On 2/4/11, Geert Claes <geert.wl.claes@gmail.com> wrote:
James Robertson spotted this post:
http://unhandledexpression.com/2011/02/04/smalltalk-for-engineers/
I was especially interested in the statement "you donât understand what you can/should do ..." -- View this message in context: http://forum.world.st/Smalltalk-for-engineers-tp3261551p3261551.html Sent from the Pharo Smalltalk mailing list archive at Nabble.com.
-- =========================================================================== John M. McIntosh <johnmci@smalltalkconsulting.com> Corporate Smalltalk Consulting Ltd. Â http://www.smalltalkconsulting.com ===========================================================================