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:
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 not keeping our old name (GemStone Systems) and we are not keeping the gemstone.com 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.
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:
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.
WorldPulse is application for the iPhone and iPad, that shows live accurate cloud cover data, the day/night terminus, night lights, and in 2.0 weather data from all the weather stations in the world.
In John’s presentation:
GemStone/S 64 220.127.116.11 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.
GemStone 18.104.22.168 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 22.214.171.124.
A One-Click GemTools 1.0-beta.8.7 for GemStone 126.96.36.199 can be obtained from the seaside.gemstone.com downloads page or you can download GemTools 1.0-beta.8.7 for Gemstone/S 188.8.131.52 all platforms directly.
You can build a custom GemTools image by following these steps on the glass db wiki.
Seaside 184.108.40.206 should be used with GemStone/S 3.1.x. There are a few critical bug fixes included in that version.
You can download the binaries from ftp://ftp.gemstone.com/pub/GemStone64/220.127.116.11, use the installGemStone.sh script to download and install GemStone/S on your machine (highly recommended), or visit seaside.gemstone.com downloads page.
To use the installGemStone.sh script, your supply the GemStone version number as an argument to the script. The following downloads and installs the GemStone/S 18.104.22.168 release:
If you are upgrading from GemStone/S 2.x, then be sure to read my post on GemStone/S 3.1.0 first.
Let’s say that you’ve got Seaside 22.214.171.124 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 126.96.36.199, that means you’ll run the following topaz script BEFORE running the upgradeSeasideImage.sh 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 188.8.131.52 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:
The video of my STIC 2012 talk “Practical Git for Smalltalk” is available. You can view the slides on SlideRocket or as pdf.
GemStone/S 64 3.1.0 was released July 5, 2012.GemStone/S 64 Bit 3.1.0 is a major new version, including many new features as well as enhancements to existing features and bug fixes. A quick highlight of features is as follows:
- IPv6 support
- multi-threaded, highly performant backup and restore
- increased security for remote logins using SRP and SSL
- a new hot standby interface, providing continuous automatic synchronization
- powerful locale-specific collation using the ICU libraries
- full support for upgrade of Seaside applications
- API for secure SSL sockets from Smalltalk
Release notes, Install Guide and manuals are available here. Be sure to carefully read the GemStone 3.1.0 release notes, if this is the first time you have used GemStone/S 3.x as there are significant differences between GemStone3.x and GemStone 2.x.
Before attempting an upgrade you will want to make sure that your application loads into a virgin 3.1 repository (extent0.seaside.dbf) and passes unit tests before attempting the upgrade.
GemStone 3.1.0 ships with GLASS 1.0-beta.8.7.2 pre-installed in
You can download the binaries from ftp://ftp.gemstone.com/pub/GemStone64/3.1.0, use the installGemStone3.1.0.sh script to download and install GemStone 3.1.0 on your machine(highly recommended), or visit seaside.gemstone.com downloads page.
Once you’ve installed Gemstone in
/opt/gemstone/product, follow these steps to start and stop the stone:
- Define GEMSTONE environment variables ($GEMSTONE/bin and $GEMSTONE/seaside/bin added to your $PATH environment variable):
It is recommended that you add this step to your
- Copy the
extent0.dbffiles to data directory:
cp $GEMSTONE/seaside/system.conf \ $GEMSTONE/seaside/data chmod +w $GEMSTONE/seaside/data/system.conf cp $GEMSTONE/bin/extent0.seaside.dbf \ $GEMSTONE/seaside/data/extent0.dbf chmod +w $GEMSTONE/seaside/data/extent0.dbf
This step is performed as part of the installGemStone3.1.0.sh script.
stoneprocess is running:
A One-Click GemTools 1.0-beta.8.7 for GemStone 3.1.0 can be obtained from the seaside.gemstone.com downloads page or you can download GemTools 1.0-beta.8.7 for Gemstone/S 3.1.0 all platforms directly.
You can build a custom GemTools image by following these steps on the glass db wiki.
The original motivation for Kaliningrad was:
The FileTree project implements a Monticello repository type that is compatible with Cypress, it is easy to save Squeak/Pharo/GemStone Monticello packages on disk and use Git for version control.
Everything isn’t quite hunky dory:
- Metacello does not have Git/GitHub support, but there is a project underway to address that.
- Amber Skeleton is currently only implemented on Pharo, but Squeak and GemStone versions shouldn’t be too difficult to implement
- Currently there is no image-based tool support for Git/GitHub, but there is a project underway to address that.
Despite the limitations, I still think that you might find Amber Skeleton interesting.
During STIC 2012, we announced VMware’s new list prices for 4 & 8 core perpetual GLASS licenses. You can also purchase Tech Support from VMware for your GLASS deployments.
No Changes to the free version terms!
Bob Nemec responds to Dave Thomas‘ statement that object abstraction is too complex for the majority of programmers.
From Bob’s post:
Most programmers are constructionists. They have a job building and maintaining business applications. As Smalltalkers we ask ourselves: how can we get these programmers to use Smalltalk, to see how much more productive and enjoyable our environment is? The answer, I believe, is to reduce barriers to entry.