I think Visual C++ helps create the Microsoft Monopoly. When it came out in
....) They were definitely not a powerhouse in the dev market.
"Ajay" <ajaykalra@yahoo.com> ha scritto nel messaggio
news:cb4b6d67-63c4-481b-8b12-c9f30d01d9ef@z5g2000yqn.googlegroups.com...
They didnt try to catch up. They had a lead on MSFT(OWL). MSFT was
catching up. Its just the Microsoft monopoly killed the competition.
Sorry, but I don't buy this theory of Microsoft monopoly (or maybe I
misunderstood you?)
I mean: what monopoly? The Win32 API is public, and everyone (you, me,
everyone) can build an OO framework on that Win32 API layer, without
asking permission to Microsoft.
And also today, you can freely use QT or wxWidgets or other frameworks to
build Windows apps, without asking permission to Microsoft.
I have no idea about OWL, I've never used it, but if it did not take off
was probably due to some real problems, not Microsoft "monopoly".
For example, reading this thread here my understanding is that this OWL
was higher level than MFC. But probably with the hardware of that time,
being higher level than MFC (and more abstracted from raw Win32 API) meant
low speed in application execution, or too much memory required, so apps
built with OWL were not snappy and not competitive and not high quality if
compared to apps written with MFC?
Thanks,
Giovanni