You are currently browsing the category archive for the ‘Gemstone’ category.

Norizzk.comToday, Johan Brichau of announced the launch of

 …a new web application built with Seaside in Pharo and deployed with GLASS in Gemstone/S was launched to the world: is an innovative platform for risk-based test management.

Watch the trailer on

Once again, the use of Smalltalk, Pharo, Seaside and Gemstone has proven to be a competitive advantage in the development of a stunning innovative product…

helperIn an episode of SmalltalkInspect graciously hosted by Marten Feldtmann; James Foster, Sebastian Heidbrink  and I talk about the upcoming (at the time) GemStone 3.2 release and the new Web Edition License terms.

Photo by / CC BY-NC-ND 2.0

The Glass Key by Dashiell Hammett (1931)With the release of GemStone 3.2, GemTalk Systems announces a new pricing structure for the GemStone/S 64 Web Edition and here’s my summary of the changes.

Photo by / CC BY-NC-SA 2.0

Dolphins and ShipGemTalk Systems announces the release of GemStone/S 64 Version 3.2.

Photo by / CC BY-NC 2.0

Cypress SwampJust released FileTree 1.0.5 with support for Traits and a couple of other bugfixes.

Photo by / CC BY-NC 2.0

Video of my talk on tODE at STIC 2013:

Link to my slides.

CalculusAs of this morning, builderCI supports Pharo-3.0 and GemStone

The total number of versions that can be automatically tested using Travis-CI and GitHub is now 16 (6 Pharo versions, 3 Squeak versions and 7 GemStone versions).

For information on using builderCI, see the project README.

Photo by / CC BY-NC-SA 2.0


I guess I was so busy preparing for my STIC talk I forgot to announce the availability of a podcast on GemTalk Systems that I did with James Robertson and David Buck. I have to say that James and David run a pretty smooth interview. It was fun and (I hope) informative.


Today GemTalk Systems announced the acquisition of the GemStone/S platform from VMware. Before anyone gets their knickers in a knot, this is a good thing:

GemTalk Systems plans to expand its 64-bit Smalltalk platform capability by designing and releasing new and innovative extensions to the core GemStone/S technology.

The entire Smalltalk team is moving intact from VMware to GemTalk Systems and I want to emphasize that both GemTalk Systems and VMware are being very generous and fair during the transition.

We are re-locating to another suite in the same office complex, up the stairs from our old location.

We are keeping all of the GemStone/S intellectual property including MagLev and all of the GemStone/S customers.

We are not keeping our old name (GemStone Systems) and we are not keeping the domain. I guess one can’t expect everything. I have also been assured that the URLs for GemSource and SS3 will continue to function for at least a year (if not longer).

From a technical perspective GemStone/S has thrived at VMware, the engineering team has been pretty much left alone and we were given all of the necessary resources to “get the job done”. From a technical and personal perspective, I have been very happy with my tenure at VMware.

On the business side, I would say that GemStone/S foundered a bit. The GemStone/S product never got fully integrated into the VMware universe (unlike GemFire), but then the GemStone/S product was not the  primary focus of the original VMware acquisition.

Now, with the GemFire team becoming part of Pivotal, you can imagine that the Smalltalk team is very happy to find a home with GemTalk Systems . 

GemTalk Systems is a privately held company led by Dan Ware.  Prior to the VMware acquisition in 2010, Dan had been an executive with GemStone Systems  for 17 years. For most of those years Dan was in charge of the Sales organization, so Dan knows the GemStone/S customer base, very well.

Dan and the investors love GemStone/S and want to see it continue to thrive.

This quote bears repeating:

GemTalk Systems plans to expand its 64-bit Smalltalk platform capability by designing and releasing new and innovative extensions to the core GemStone/S technology.

and from our transition FAQ:

Our core technology will be Smalltalk-based products, but they can provide infrastructure in other environments. We will continue to support GemBuilder for Java, and we will be revisiting MagLev for Ruby and GLASS for Seaside. New initiatives into other development areas are possible.

Frankly, I don’t think that I could have imagined a better home for GemStone/S.

Turning coffee into cash[1]


GemStone/S 64 was released August 28, 2012. This release fixes a number of bugs and we recommend all 3.x customers use this release. Be sure to review the release notes and install guides for this release.

GLASS 1.0-beta.8.7.3

GemStone ships with GLASS 1.0-beta.8.7.2 pre-installed in $GEMSTONE/bin/extent0.seaside.dbf, but there are a few minor issues that show up as test failures. GLASS 1.0-beta.8.7.3 has been released to address those issues.

You should update to GLASS 1.0-.8.7.3 when you start using GemStone

GemTools 1.0-beta.8.7

A One-Click GemTools 1.0-beta.8.7 for GemStone can be obtained from the downloads page or you can download GemTools 1.0-beta.8.7 for Gemstone/S all platforms directly.

You can build a custom GemTools image by following these steps on the glass db wiki.


Seaside should be used with GemStone/S 3.1.x. There are a few critical bug fixes included in that version.

Download and Installation

You can download the binaries from, use the script to download and install GemStone/S on your machine (highly recommended), or visit downloads page.

To use the script, your supply the GemStone version number as an argument to the script. The following downloads and installs the GemStone/S release:



If you are upgrading from GemStone/S 2.x, then be sure to read my post on GemStone/S 3.1.0 first.

If you are upgrading from GemStone/S 2.x or GemStone/S 3.1.0, you still need to run through the upgrade process described in the Install Guide for (Linux or Max).

Helper Scripts for Upgrade of Seaside

Let’s say that you’ve got Seaside installed in your GemStone/S 3.1.0 repository. According to the upgrade instructions you will need to define the BootstrapApplicationLoadSpecs for your application. For Seaside, that means you’ll run the following topaz script BEFORE running the script:

The important bits are that you are specifying GLASS 1.0-beta.8.7.3 and specifying the <path to seaside cache repository>. The seaside cache repository is a directory on your machine where you’ve stashed all of the mcz files needed to reload Seaside into your upgraded repository. You can use the following script to create the seaside cache repository:

Finally, as noted in Issue 354, you need to reload the ConfigurationOfGLASS and ConfgurationOfSeaside30:


[1] / CC BY-NC-ND 2.0

Enter your email address to subscribe to this blog and receive notifications of new posts by email.

Join 446 other subscribers


RSS GLASS updates

  • An error has occurred; the feed is probably down. Try again later.

RSS Metacello Updates

  • An error has occurred; the feed is probably down. Try again later.

RSS Twitterings

  • An error has occurred; the feed is probably down. Try again later.
March 2023