Smalltalk and Python
Aaron Jon Reichow
reichowa at tcfreenet.org
Wed Dec 13 18:07:03 CET 2000
On 13 Dec 2000, Erno Kuusela wrote:
> In article <Pine.BSF.4.10.10012122310510.48551-100000 at tcfreenet.org>,
> Aaron Jon Reichow <reichowa at tcfreenet.org> writes:
> | On 13 Dec 2000, Erno Kuusela wrote:
> || the thing that struck me as a little foreign was the apparent
> || isolation of the smalltalk image from the rest of the operating system
> || and the filesystem. i want to be able to grep code!
> | While I'm not a proponent of Smalltalk isolationism, grep is a useless
> | tool (more or less), simply an artifact, ye, a symptom of the
> | sickness known as file-based development.
> point was that it's valuable to me to be able to manipulate stuff via
> the filesystem. version control, editors, access control, locking,
> backups, and all the rest of the universe works with files (same
> critique goes for zope).
I think there's definate value of a more unix-ish, script-aimed side of
Smalltalk. I, personally, would like to have Smalltalk scripts (GNU
Smalltalk is OK, but something more full featured) that I could use in
place of bash and python scripts. But beyond that, files are largely
obsolete. Not in practicality, but in how we should represent data.
There's a CVS interface to Squeak, so I don't think that the rest of the
things you listed quite apply.
Aaron Reichow :: "In essence, Smalltalk is a programming
Twin Ports ACM Vice President :: language focused on human beings rather
http://www.d.umn.edu/~reic0024/ :: than the computer." - Alan Knight
More information about the Python-list