Everyone sees the world through their own eyes, filtered by what their past and what know. A peculiar perspective of Smalltalk programmers is to consider that "code in files is dead code". External tools are needed to…
> * Tests are now common and considered a good thing. A new contributor can write code without worrying about breaking rarely-used functionality. btw, xUnit testing originated with Smalltalk.…
Check out... "Zinc" - It used to be an external package later integrated into Pharo. To check it out, download Pharo 5 from http://pharo.org/download then try the tutorial...…
Having said that, coming to Pharo from a C programming background, one area that for "a while" I found over complex was use of the visitor pattern and double-delegation. This was facilitated by Smalltalk's duck typing…
> criticisms I've seen of OOP, that it too easily results in overly-complex software With respect to other languages, many don't do OOP well ;] Indeed in the OP video Alan Kay said "Object oriented programming never…
> it was not what I would call clean. That's given you a false impression. The .st file is only an the export/transfer format to be loaded into another Smalltalk system. Smalltalk code is best read using its System…
> How anyone could possibly be productive in such an environment. What is it that's so attractive about it to Smalltalkers? Now you've probably heard that in Smalltalk everything is an object. Sure its an nice…
> SBE is so far out of date Pharo By Example is being revised for Pharo 5. The first 13 chapters are done... https://github.com/SquareBracketAssociates/UpdatedPharoByExa... The whole book can be downloaded from...…
> The colorful Playskool environment That was likely Squeak, not Pharo. Pharo has muted a lot of the UI colours to be more appropriate for a business environment. > How anyone could possibly be productive in such an…
Everyone sees the world through their own eyes, filtered by what their past and what know. A peculiar perspective of Smalltalk programmers is to consider that "code in files is dead code". External tools are needed to…
> * Tests are now common and considered a good thing. A new contributor can write code without worrying about breaking rarely-used functionality. btw, xUnit testing originated with Smalltalk.…
Check out... "Zinc" - It used to be an external package later integrated into Pharo. To check it out, download Pharo 5 from http://pharo.org/download then try the tutorial...…
Having said that, coming to Pharo from a C programming background, one area that for "a while" I found over complex was use of the visitor pattern and double-delegation. This was facilitated by Smalltalk's duck typing…
> criticisms I've seen of OOP, that it too easily results in overly-complex software With respect to other languages, many don't do OOP well ;] Indeed in the OP video Alan Kay said "Object oriented programming never…
> it was not what I would call clean. That's given you a false impression. The .st file is only an the export/transfer format to be loaded into another Smalltalk system. Smalltalk code is best read using its System…
> How anyone could possibly be productive in such an environment. What is it that's so attractive about it to Smalltalkers? Now you've probably heard that in Smalltalk everything is an object. Sure its an nice…
> SBE is so far out of date Pharo By Example is being revised for Pharo 5. The first 13 chapters are done... https://github.com/SquareBracketAssociates/UpdatedPharoByExa... The whole book can be downloaded from...…
> The colorful Playskool environment That was likely Squeak, not Pharo. Pharo has muted a lot of the UI colours to be more appropriate for a business environment. > How anyone could possibly be productive in such an…