With Windows 1.0 Microsoft had a lot of infrastructure behind it, but when we used it we just got a clock and a calculator.

It was not even a good replacement for SideKick.

Look where Windows 7.0 has come.

It may be that Oslo 0.3(?) today has Quadrant and modeling tools at the forefront, but it has a very sound infrastructure underneath; soon we will store our programs in the database (not just our models)and update them on-the-fly at customers' sites.

Microsoft always proceeds this way: they start with the trivial and then bang! The Unix world starts with the complex and stays there.

-Ciper

Thanks for your thoughts in this post and all your other recent ones too.

I wanted to add that storing programs in a database already is part of the "Oslo" concept. Models and "modeling"are meant to include both data and behavior, the latter meaning that some runtime takes those behavior models and turns them into a running program. And then, exactly as you point out, making updates to the behavioral models changes the application on the fly (so long as the runtime knows to do its appropriate refresh).

In short, to what extent a program can be represented in purely data, storing a program in the database (and not as compiled binaries) is a present reality. Admittedly, this part of the "Oslo" story hasn't been as clearly presented, but it's been there for a long time.

.Kraig

(Windows 1.0 had at least one hot program, which was Micrographix Draw, I believe. I remember using it on my father-in-law's work computer to make a chart for something I did in high school...)

Oslo is certainly more than meets the eye. Look at Quadrants metadata and the repository; there is a lot of foundation, thinking and engineering in it.

Developing software todayis much easier than in the windows 1.0 days; software back than might be labeled as 'simple'. Today there are so much possibilities, with so many powerful tools. There is also much more to learn now.

---

Performing my Final Project, looking into codename "Oslo".