11 ms·
You would be surprised at how much cruft in Windows over the years has been directly due to Adobe. I had many bug triage sessions where Windows developers at Mi
by tomcam 10y ago
You would be surprised at how much cruft in Windows over the years has been directly due to Adobe. I had many bug triage sessions where Windows developers at Microsoft had to work around Adobe problems to keep Windows users happy. I always thought it was unfair and was quite impressed by Microsoft at their willingness to handle this so quietly.
- batter 10y agoDoesn't it makes you wonder why MS created that situation on the first place? MS have no one to blame except themself and their 'legacy code'.
- commandar 10y agoIt's hard enough to get enterprise customers to stay current when they do provide legacy support. Fighting with IE version compatibility, for example, is still a daily, very real issue for enterprise size organizations. Blame the customers. Microsoft never would have captured the marketshare they have if they didn't cater to them.
- DaiPlusPlus 10y agoMicrosoft does deserve some blame for deciding to support backwards-compatibility in-situ instead of introducing proper API versioning, packaging, isolation, and other proven techniques. Win32 wasn't versioned for processes until Windows 7 (using app.manifest) even though the need for such as system was blatantly obvious during the Windows 2000 days.
- commandar 10y agoSure, that's valid. But most of the real nightmare scenarios I've heard related to backwards compatibility have more to do with third-parties doing things they were never supposed to do. Things like hitting private, undocumented APIs. Or checking the Windows version with a "9x" wildcard, giving us the jump from W8 to W10 over a decade later. Microsoft has made their own mistakes, but supporting the mistakes of third parties has been absolutely vital to them keeping their core customer base.
- DaiPlusPlus 10y agoAll of those scenarios you describe can be solved with appropriate application sandboxing and shimming. I don't personally believe the "Windows 9" story - if a program is old enough to feel the need to check for Windows 95/98 then it should already be fine to run under Windows' own app-compat layer which spoofs the Windows version string anyway. I believe it's marketing-based out of fear consumers would see "MacOS 10 vs Windows 9" (like how it was PlayStation 3 vs Xbox 2 - hence "Xbox 360").
- nemothekid 10y agoMacOS 10 wasn't rebranded from OS X until 2016, a full year after Windows 10 GA - and I doubt anyone outside a select few at Apple knew that the OS X line was going to be renamed. In any case, your reasoning doesn't really make sense. I can run a program that was written for Windows XP on Windows 10 without the need from a app-compat layer. Given that a developer can hide/show all sorts of random functionality with an if-branch-on-version - the user will see a broken or strange app and it won't be clear (and MS probably didn't have the means to detect) that the app should run in compatibility mode. I still believe that MS wanted to ship an OS that "just worked" and did so under 10, than trying to compete in version numbers with an OS that has had 10 in its name for last 18 years.
- frik 10y ago> MacOS 10 wasn't rebranded from OS X until 2016 X means 10 in latin. Look at old MacOS X 10.3 books, X always stood for 10.
- talmand 10y agoEven your mac will say 10 if you get to speak out Mac OS X. But I have had many a people insist it was not pronounced as Mac OS 10, but as Mac OS X. I could understand the confusion.
- nemothekid 10y agoMacOS 10 wasn't rebranded from OS X until 2016, a full year after Windows 10 GA - and I doubt anyone outside a select few at Apple knew that the OS X line was going to be renamed. In any case, your reasoning doesn't really make sense. I can run a program that was written for Windows XP on Windows 10 without the need from a app-compat layer. Given that a developer can hide/show all sorts of random functionality with an if-branch-on-version - the user will see a broken or strange app and it won't be clear (and MS probably didn't have the means to detect) that the app should run in compatibility mode. I still believe that MS wanted to ship an OS that "just worked" and did so under 10, than trying to compete in version numbers with an OS that has had 10 in its name for last 18 years.
- UnoriginalGuy 10y ago> Microsoft does deserve some blame for deciding to support backwards-compatibility in-situ instead of introducing proper API versioning, packaging, isolation, and other proven techniques. They did, in Windows 8. It is called Metro/Modern/UWP. Everyone hates it.
- tjalfi 10y agoMy employer has an application that requires IE5 compatibility mode. We are a version behind and will be upgrading it this year. The sad thing is that the new version uses Silverlight.
- pc2g4d 10y agoMicrosoft's willingness to maintain backward compatibility has been key to their success over the years. With the importance of Adobe's products on their platform, it makes sense that they would go out of their way to ensure their continued functioning.
- guitarbill 10y agoFor enterprise customers, sure. For many consumers, now that they use more modern OS and browsers daily (iOS/Android), it's painfully obvious how terrible this strategy has been - even if they can only articulate that on a subconscious level. Honestly I'd love to see what Microsoft could do if they ditched backwards compatibility completely, except in the server OSes. While hardly revolutionary, Surface Pad Pro is a good indicator/example that there's at least potential there.
- m1sta_ 10y agoThey could create a new version of Windows to mark this retry. Maybe they could call it Windows RT.
- sorenjan 10y agoI bet it would be a huge success.
- derefr 10y agoRather than dropping compatibility entirely, I've always wondered why no modern OS has gone the route of creating a "compatibility layer" that's actually a (very-tightly-sandboxed) VM containing a [stripped-down] older copy of the OS. This would be perfect to re-add Win16 support to W10, for example. Try to double-click a 16-bit app? It opens with its handler, "Windows 3.1 Hyper-V Association Background Launcher". As long as no W3.1 apps are running, it unloads, and the rest of the OS can be completely free of 3.1-era cruft. You could deprecate features from your latest OS at a breakneck pace if you really took this strategy to heart. WinRT really could have been just Metro/UWP + a "Desktop" that's actually a Windows 7 VM with a high-level paravirtualized shared filesystem. (And it's not like Microsoft didn't do this themselves before; this is essentially how DOS applications ran under Windows 3.1, in a [hypervised!] DOS VM.) --- EDIT: let me clarify the specific point I was getting at. If you ship $OldOS as a VM within $NewOS, very tightly sandboxed, then you never have to update $OldOS again, nor do you have to keep the code from $OldOS around in $NewOS. The $OldOS VM is now a "static artifact"—something that will never change, but will continue to run old software perfectly. So, if $OldOS gains more security flaws, you don't update $OldOS; you update the virtualization software to make the sandbox stricter. And when you find that your $NewOS is now, itself, old—well, you just do the whole thing again, writing an emulator for $NewOS within $EvenNewerOS, and then your $OldOS programs run by launching a VM-in-a-VM. If you like, you can port the $OldOS emulator to run on $EvenNewerOS—but you could also just consider it legacy software of exactly the type your $NewOS emulator is built to run. The point of this is to decrease maintenance burden, by freezing the previous OS, so that you never need to think of it again. This wasn't what was done with "XP Mode"; Windows XP continued to receive updates as a component of Windows 7. The point here would be to EOL the older OS, and then virtualize it.
- zubat 10y agoNow imagine the world where Microsoft became Adobe's direct competitor and cut their oxygen supply.
- goldfire 10y agoThis is exactly what Microsoft were accused of doing to Lotus 1-2-3 back in the day. See [0]. TL;DR: wasn't true. [0] https://news.ycombinator.com/item?id=10432608 https://news.ycombinator.com/item?id=10432608
- eon1 10y agoI feel like you're implying that would be a bad thing when it could actually be preferable. I don't think MS is faultless or anything, but I'd be surprised if they could make themselves as much of a pain as Adobe does (especially given all the OS integration opportunity).
- santaclaus 10y agoDidn't they try that with Expression back in the aughts and fail? Doesn't mean it couldn't work now, though!
- at-fates-hands 10y agoI actually found out about Expression way after the fact and thought it was a viable alternative - but by then, MS was already in the process of sending it out to pasture. It's like a co-worker said, "Adobe's software is bloated and cumbersome, but they have a top notch marketing team that keeps it afloat." But yes, if there is a company that is ripe to have some serious competitors it would be Adobe.
- wvenable 10y agoAdobe effectively forced Apple to build the Carbon API for OS X delaying the release by a year or more.
- jomohke 10y agoApple used Carbon for a lot of its own built-in apps, such as Finder, didn't it? (edit: and iTunes) (Almost?) all other other major vendors at the time used it heavily too: Microsoft Office until 2011, FileMaker until 2010. If Apple released the OS a year earlier, but without any available third-party software (waiting for almost-rewrites to happen), would they really have been better off? At this time they were on life support and would have had difficulty convincing third-party vendors to invest heavily in their platform, or to convince users to adopt it without any major applications available. In either case, Adobe's sway clearly declined over the years, as Apple cancelled the 64bit version of Carbon while Adobe was still heavily built around it, forcing Adobe to switch (and an awkward year or two when the Mac, but not Windows, versions were stuck with 32bit memory limitations)
- wtallis 10y ago> Apple used Carbon on a lot of its own built-in apps (such as Finder), didn't it? Apple wrote the Finder in Carbon as a dogfooding exercise, to prove to third party developers that Carbon was a first-class fully supported framework. The Finder has since been re-written in Cocoa.
- DerekL 10y ago> Apple used Carbon for a lot of its own built-in apps, such as Finder, didn't it? (edit: and iTunes) iTunes needed to support both Mac OS 9 and X, so Carbon made much more sense than writing all of the UI code twice. Also, it started as SoundJam MP, which was written for Mac OS 8, so Carbonization was much less work than a Cocoa rewrite.
- simonh 10y agoRight, but the same logic applied to any popular app with users still on Mac Os.
- aswanson 10y agoI've heard that Adobe's poor software engineering has provided a huge malware/virus vulnerability surface for windows. Maybe MS should force them to break/rewrite.
- simonh 10y agoAnd push a large chunk of Adobe users on to the Mac.
- frik 10y agoFile metadata is not cruft. It's a very good thing. Vista's/Win7 Explorer.exe with its metadata columns is GREAT. Even better was Windows (Live) Photo Gallery. Sadly it's dead since Feb 2017, you can't even install it anymore, as only a now broken WebInstaller exists. Photo Gallery was hand down 1000 times better than Picasa/Lightroom/Photos/iPhotos for just browsing photos and videos. And it alo supported tags with hierarchy (eg "City/New York/Manhattan"). https://en.wikipedia.org/wiki/Windows_Photo_Gallery https://en.wikipedia.org/wiki/Windows_Photo_Gallery Sadly WinFS failed, metadata is nowadays often misunderstood and persived by companies contra productive in the age of cloud service strategies. Flickr is probably the only well known photo service tht keeps metadata. Facebook made it popular to strip metadata and keep annotations internally (as vendor lockin) - now common also with other services. I hope there will be a kind of come back of metadata. People need more education to understand the concept, that's all.
- mathw 10y agoSure it's not cruft when they're images in your image library and you need to find them and understand them using said metadata. It's cruft when those assets are now embedded into your compiled, bundled, distributed software and such metadata now has no purpose whatsoever, as is the case for the examples cited in the article.
- i336_ 10y ago> Even better was Windows (Live) Photo Gallery. Sadly it's dead since Feb 2017, you can't even install it anymore, as only a now broken WebInstaller exists. This sounds like a challenge. You're on. - Do some scratching around; discover sites hosting "wlsetup-all.exe" - Point the Web Archive at download.live.com - After some trial and error with broken pages find http://web.archive.org/web/20161130174327/https://support.microsoft.com/en-us/help/18614/windows-essentials http://web.archive.org/web/20161130174327/https://support.mi... - Follow the "Download options" link - Eventually land on http://web.archive.org/web/20161226002912/https://support.microsoft.com/en-us/help/17779/download-windows-essentials http://web.archive.org/web/20161226002912/https://support.mi..., and disable JavaScript so the page doesn't kill itself (remember on Chrome you just click the (i) to the left of the URL) - Ah, a "Download Now" link! $ curl -vv http://go.microsoft.com/fwlink/?LinkID=255475 Location: http://g.live.com/1rewlive5-web/en/wlsetup-web.exe $ curl -vv http://g.live.com/1rewlive5-web/en/wlsetup-web.exe Location: http://wl.dlservice.microsoft.com/download/C/1/B/C1BA42D6-6A50-4A4A-90E5-FA9347E9360C/en/wlsetup-web.exe Hmm... (note s/web/all/g) $ curl -vv http://g.live.com/1rewlive5-all/en/wlsetup-all.exe Location: http://wl.dlservice.microsoft.com/download/C/1/B/C1BA42D6-6A50-4A4A-90E5-FA9347E9360C/en/wlsetup-all.exe Can I...?... $ curl -vv http://wl.dlservice.microsoft.com/download/C/1/B/C1BA42D6-6A50-4A4A-90E5-FA9347E9360C/en/wlsetup-all.exe < HTTP/1.1 404 Not Found (...) <div id="header"><h1>Server Error</h1></div> (...) <h2>404 - File or directory not found.</h2> <h3>The resource you are looking for might have been removed, had its name changed, or is temporarily unavailable.</h3> Hmmm. - Try and load wl.dlservice.microsoft.com/robots.txt in the Web Archive - Get redirected to Microsoft homepage!! - Lookup wl.dlservice.microsoft.com/* in Web Archive - "805 URLs have been captured for this domain." - Search for "c1ba..." - get hits! http://web.archive.org/web/20170416220642/http://wl.dlservice.microsoft.com/download/C/1/B/C1BA42D6-6A50-4A4A-90E5-FA9347E9360C/en/wlsetup-all.exe http://web.archive.org/web/20170416220642/http://wl.dlservic... 137329840 bytes. There are other sites that have copies of the file, but a) this one is from the Web Archive and b) I've verified using a mixture of WA and still-live Microsoft redirects that this is the latest-ever release.
- comex 10y agoNot just Windows. Some choice strings from macOS system frameworks: AppKit: NSSavePanelOverRetainToCompensateForAdobe NSShouldWorkAroundBadAdobeReleaseBug Adobe Invener Fusion opted out due to odd event processing Foundation: com.adobe.Reader com.adobe.Acrobat com.adobe.Acrobat.Pro _allocWithZone:.do_adobe_hack (Though they're hardly alone. AppKit contains a huge number of bundle IDs scattered through the strings list, presumably for various special cases…)
- brongondwana 10y agoEveryone has hacks for the biggest products out there, it's a fact of life. My DAV server has hacks for Microsoft bugs and misfeatures, hacks for older Apple clients, hacks for Konqueror of all things, because I tested against it. And our current CalDAV code has just inherited two new hacks this week to work around weird bugs in shit that Google Calendar has been serving up: * years with only two digits or two leading zeros rather than 20xx. * unquoted TZNAMEs with :s in them. At least events from year "0012" are allegedly legitimate parsable ISO8601 times, and the events from year "12" are at least legitimate VCALENDAR. The broken TZNAMES parse legitimately, but DTSTART;TZNAME=GMT+10:00:20120101T01010101 needs to be fixed up pre-parse. Welcome to interoperability, where liberal in what you accept is the only choice when your communication partner is much bigger.
- l-p 10y agoExcerpt from the Radicale documentation: > The Radicale Server does not and will not support the CalDAV and CardDAV standards. It supports the CalDAV and CardDAV implementations of different clients (Lightning, Evolution, Android, iPhone, iCal, and more).
- brongondwana 10y agoYeah, I bet. The standards are getting better, but there are so many vendor specific things that you need to support to have a good experience that just reading the standards in isolation won't help you much. Contributing to devguide.calconnect.org on the other hand, helps everybody.