It is always an honour to interview people who have 'served' and worked on operating systems at the "golden" times of the operating systems, the '80s and pre-Win9x days. Today we interview Adam de Boor, who was the CTO at GeoWorks, developers of the GEOS, in the begining of the last decade. Adam today works for OpenWave Systems. We discuss about GeoWorks, its past, its future, where it should have been.
Permalink for comment
To read all comments associated with this story, please click here.
I don't know anything about the Commadore versions, but all PC versions were heavily object oriented. That's why all the apps are so small. 2.x had a LOT more functionality (I vaguely remember hearing 4-5x). I think 2.0 was optimized for at least of 2 megs of ram, although it still did work in 640k.
I don't see why Geoworks would want C++ experience, as you can't even use C++ with GEOS. My only guess is in the 1.x days, the SDK wasn't really ready for the outside world, so they limited who they gave it to to try to cut down the support they'd have to do. I didn't get interested in programming until the 2.x days. At that point, the SDK was $100, no questions asked.
I don't know anything about the Commadore versions, but all PC versions were heavily object oriented. That's why all the apps are so small. 2.x had a LOT more functionality (I vaguely remember hearing 4-5x). I think 2.0 was optimized for at least of 2 megs of ram, although it still did work in 640k.
I don't see why Geoworks would want C++ experience, as you can't even use C++ with GEOS. My only guess is in the 1.x days, the SDK wasn't really ready for the outside world, so they limited who they gave it to to try to cut down the support they'd have to do. I didn't get interested in programming until the 2.x days. At that point, the SDK was $100, no questions asked.