Re: Borland's OWL was a much sensible approach than MFC
The one thing I remember about OWL is Borland changed everything between a particular pair of versions (was it 1.0 to 2.0?) They basically told developers to rewrite all their code and provided tools that did a rather bad job of automatically converting it.
In my book, if you're providing API you should keep the interface to it backwardly compatible - we felt betrayed by Borland and our small company shifted to plain Windows with MFC after that since we were going to have to rewrite our code anyway. Prior to that we'd used Borland from the days of Turbo C.