monticello

Trying to integrate thing that are not Smalltalk code into monticello is a pain.

Modern Smalltalks (Squeak, Pharo) have Monticello for code management, and Metacello for dependency management.

There's a slow transition from Monticello to Git but tools are still subpar.

For version control, you need to use systems such as Monticello or Store, both of which make me cringe just thinking about them again.

A $10 bottle of gabbiano tastes almost nothing like a $10 bottle of monticello rioja and neither will taste anything like your jug of wine.

When I looked again to Smalltalk, Squeak was already around and Monticello was being used.

At the time of his death, he had freed a grand total of about 7 slaves, but 130 slaves were sold from Monticello after his death.

If you can tell the difference between grapefruit juice and orange juice, you can tell the difference between a gabbiano, a monticello rioja and a generic merlot.

I can then fire up my _local_ Pharo environment, materialize the error, debug it with all its context, fix whatever code I need to and push the changes to my monticello repo.

SmalltalkSyntaxInaPostcard The hardest part is wrestling with the class libraries and getting used to the hermit kingdom that is the image-based environment, though the community behind Pharo and other modern Smalltalk environments have done some interesting advances when it comes to bridging the gap, such as the Monticello VCS for snapshotting code state to a regular file system in the form of an archive.

It's too late for an edit, but looking at the article again, especially the conclusion, I wonder even more about the seeming dismissal of Smalltalk: > * storing code in a networked database with version control and realtime sync This sounds a lot like Monticello and/or what Lively Kernel does over Webdav?

"read the source" is pretty useless when the source is scattered around various Monticello repositories, which never seem to work for me thanks to the Smalltalk community's epic linkrot.

The development environment is the same as the runtime environment, it has its own source control (Monticello), its own editor and a very regular language.

Combine that with powerful IDE, VC support (Monticello, Metacello) etc.

Bitkeeper, Mercurial, Git, Subversion, Perforce, tla, Monticello, Bazaar, darcs, Fossil, Monotone, and TFS are all maintained on their own systems.