3 ms·
Before going to Microsoft, I had used COM and OLE via VB, FoxPro, and probably a few other higher-level abstractions. Then I went to Microsoft and worked on OLE
by mikestew 8y ago
Before going to Microsoft, I had used COM and OLE via VB, FoxPro, and probably a few other higher-level abstractions. Then I went to Microsoft and worked on OLE DB, using C. O...M...G. CreateObject() suddenly turned into (what seemed like) a 1000 lines of almost-boilerplate. That ADO AddRecord() that was so easy in classic VB? Ugh, if only you knew what was behind that. COM was a clever idea to solve a hard problem, but if one had to work under the covers it was some sausage you were definitely better off not knowing the ingredients of. I mean, COM mostly worked and wasn't bad once you got the hang of it, just like pig snout in your sausage isn't bad for you. It's just kind of unappealing at first.
- pjmlp 8y agoThey finally learned with UWP. Microsoft WinDev always seemed a bit strange versus everyone else. Borland had very nice high level frameworks (still do as Codegear but alas), and then DevTools also had them as VB and later .NET. But WinDev had always to make everything low level, and if it wasn't for them we would have had AFX instead of MFC.
- thought_alarm 8y agoBackward compatibility is easier if the OS APIs are as terse and featureless as possible. Higher-level frameworks (VB, .NET, VCL, etc.) can then be distributed independent of OS releases with multiple versions installed simultaneously.
- pjmlp 8y agoThat is orthogonal to actually making OS APIs easier to deal with. Even with plain C there are ways to have higher-level usable frameworks.
- DaiPlusPlus 8y agoWinRT is so very nice - but it's insane how most of its benefits and services are exposed only to UWP applications.
- pjmlp 8y agoUWP is the future, Win32's long term roadmap is to join Win16. In any case, one of the points of April 2018 release and the upcoming Redstone 5 one is that those models are being merged. And yes, the next Office version for Windows 10 is store only and as usual in Office tradition, is the one responsible for many new UI controls (UWP Fluent Design) in the upcoming Redstone 5 version.