4 ms·

After so much on MFC,OLE,COM/DCOM=>ATL, ADO, DAO, c#,.net,silverlight and now html5, I am not MS fan any more and has zero interest in any MS stuff.

pjmlp 14y ago
Name one single technology company that does not keep changing the developer tools all the time. edit: typo
- bryanlarsen 14y ago
  The Linux Foundation, the Apache Project, et cetera.
  - pjmlp 14y ago
    Those are not commercial vendors. Still, if you want I can post all the Linux kernel ABI changes. The changes done in Apache during the 1.x to 2.x transition. Or many other examples, as they are quite easy to find.
    - bryanlarsen 14y ago
      compared to the differences between win32 and WPF those are trivial. Also, the kernel ABI is considered an "internal" ABI, for better or for worse, the kind you wouldn't be able to access without an NDA and signed contract in the commercial world. The kernel's stable interface is its system call interface, which is remarkably stable.
      - pjmlp 14y ago
        Go tell that to the guys coding device drivers, so now device drivers API are private?! Nice to bend the reality to fill into your argumentation.
        bryanlarsen 14y ago
        Companies give out NDA's like candy, so that's hardly private. I've written Linux device drivers. They're easy to write, and API changes are not a concern at all.
        pjmlp 14y ago
        > Companies give out NDA's like candy, so that's hardly private. private as "private/internal API" nothing to do with secret. > I've written Linux device drivers. They're easy to write, and API changes are not a concern at all. The whole point is that it changes! So it is ok for Linux to change the Kernel ABI, but for companies not?!
WayneDB 14y ago
And which one of those doesn't work anymore?
- jasomill 14y ago
  In Metro-style/Windows Store apps? MFC, ATL, ADO, DAO, and Silverlight, large parts of .NET, and COM components not written against the subset of Win32 supported by Metro.
  - WayneDB 14y ago
    Those kits still do work for the platform they were built for though. New platform, new kits. Same as any other company.

pjmlp 14y ago

Name one single technology company that does not keep changing the developer tools all the time. edit: typo

bryanlarsen 14y ago
The Linux Foundation, the Apache Project, et cetera.
- pjmlp 14y ago
  Those are not commercial vendors. Still, if you want I can post all the Linux kernel ABI changes. The changes done in Apache during the 1.x to 2.x transition. Or many other examples, as they are quite easy to find.
  - bryanlarsen 14y ago
    compared to the differences between win32 and WPF those are trivial. Also, the kernel ABI is considered an "internal" ABI, for better or for worse, the kind you wouldn't be able to access without an NDA and signed contract in the commercial world. The kernel's stable interface is its system call interface, which is remarkably stable.
    - pjmlp 14y ago
      Go tell that to the guys coding device drivers, so now device drivers API are private?! Nice to bend the reality to fill into your argumentation.
      - bryanlarsen 14y ago
        Companies give out NDA's like candy, so that's hardly private. I've written Linux device drivers. They're easy to write, and API changes are not a concern at all.
        pjmlp 14y ago
        > Companies give out NDA's like candy, so that's hardly private. private as "private/internal API" nothing to do with secret. > I've written Linux device drivers. They're easy to write, and API changes are not a concern at all. The whole point is that it changes! So it is ok for Linux to change the Kernel ABI, but for companies not?!

WayneDB 14y ago

And which one of those doesn't work anymore?

jasomill 14y ago
In Metro-style/Windows Store apps? MFC, ATL, ADO, DAO, and Silverlight, large parts of .NET, and COM components not written against the subset of Win32 supported by Metro.
- WayneDB 14y ago
  Those kits still do work for the platform they were built for though. New platform, new kits. Same as any other company.