I know this is a dead thread, but I have a little experience in Smallworld arena.
In the mid 2000s I had briefly switched from Intergraph to Smallworld (version 3.something) for a data conversion gig, and it was fairly straightforward to understand, especially if you have someone give you a tour. There are a lot of analogs between all GISes, given the common underlying problems with geospatial data storage, manipulation, and representation. Similar ideas map easily, for example, versioning, geometry, rendering etc.
The data model was robust (many geometry properties allowed in one object!), the network actually worked, and so did versioning, and Magik seemed like a simplified javascript syntax before javascript got formal packages and requires. And it worked on a command line as well. I never understood how ESRI gained any traction in the utility space. Shows the good marketing efforts of ArcFM I guess.
Since Duke *is* a utility, Smallworld is a quite a good solution for that problem domain. Many of the "GIS" capabilities are similar, but the value-added is specifically for utility networks and GE has a long and successful track record in that space.
Utility networks are something that ESRI has only recently begun to address within its core products, delegating most utility-oriented functionality to 3rd party partners until now. Made a lot of consultants rich back in the day.
Since I left the Intergraph and Smallworld arenas to join the ArcGIS juggernaut, it appears Smallworld has added some java interfaces to attract more mainstream developers and has tried to plant itself firmly as a large-enterprise, big-data-center solution.
Keeping your ArcGIS skills fresh while actually using a different platform is difficult with the current ESRI offerings. (Licenses are way too expensive for hobbyists, casual users, or open-source geeks!) At minimum you need to keep a current ArcGIS Online subscription if you ever think you will move back to an ArcGIS shop. And integrating open datasets available from ESRI and other sources with whatever GIS platform you end up on is a necessity to keep your skills current.
The pace of architectural change ArcGIS has gone through in recent years is daunting, and especially now, given the new network, new versioning, new data service and container architectures, new APIs, 3D, and new ... well everything. I returned to the ArcGIS fold only recently, having left it at version 9.3, and playing catch-up is a full-time job in itself. And I was surprised how much COM is still involved...
Brad
