3 ms·
They don’t want people to keep writing COM/ActiveX code, and they don’t want search engines to point you to such pages, so why would a commercial entity spend m
by Someone 8y ago
They don’t want people to keep writing COM/ActiveX code, and they don’t want search engines to point you to such pages, so why would a commercial entity spend money to keep those pages around?
Hosting costs may be peanuts for them, but there’s also maintenance. Even if they don’t bother updating the look of the site, there’s the fact that old sites eventually run on no longer supported technologies that may only run on unsupported OSes, both potentially riddled with security vulnerabilities.
- ericlippert 8y agoI take your point, but VS twitter is this week running a series of short videos with Larry Osterman about how awesome COM is, which seems to argue against this theory. That said, lots of times Microsoft's left hand does not know what the right hand is doing.
- pjmlp 8y agoHi Eric, I also find this theory quite strange, given that UWP is COM.
- maxxxxx 8y ago"They don’t want people to keep writing COM/ActiveX code, and they don’t want search engines to point you to such pages, so why would a commercial entity spend money to keep those pages around?" That would just be nuts. There is a ton of legacy code that needs maintenance and therefore needs documentation. this is not the JS world where it's OK to break stuff twice a year.
- pjmlp 8y agoThe large majority of APIs introduced since Windows Vista are COM, even more so with WinRT/UAP/UWP. Win32 is mostly stuck in how Windows XP used to be.