4 ms·
A lot of businesses I talk to have a lot of legacy applications which work well under XP, but break for whatever esoteric reason (for example, an old Access dat
by rubberband 13y ago
A lot of businesses I talk to have a lot of legacy applications which work well under XP, but break for whatever esoteric reason (for example, an old Access database, or VB6 app) under Windows 7/8. An equally large pain the ass is a ton of intranet sites break when switching to IE9 and above (heck, a lot of companies still force IE6/7 and below with Group Policy). It's difficult to make a case to management when everything is working well (it's hard to explain the nuances of "end of support life cycle" to someone who needs help "getting to the Google").
Also, there are a fair number of desktop software products which don't even support Windows 8 yet. Hard as it may seem for the crowd here, most of the software world is not on the HTML5/Ruby/OMGMVCJAVASCRIPTBRO bandwagon yet.
- EvanAnderson 13y agoI can't speak to the websites having problems with IE9 and above, however the desktop application compatibility situation has ended up being overblown in my experience. Sitting down with "Process Monitor" and weakening permissions or spending a few minutes figuring out how to apply the existing Application Compatibility shims the OS provides has sorted out almost every problematic desktop application. For the few applications that failed to yield the "Windows XP Mode" VM (which comes with Windows 7 Professional licenses) has worked fine (albeit the multiple users per PC "story" for "Windows XP Mode" is terrible and having a bunch of XP VMs to support adds complexity).
- obituary_latte 13y agoWhat's wrong with the OMJB framework? I've written hundreds of large-scale multi-optional dynamic polymorphic backend front-end GUI shell's on legacy mainframe infrastructure with it.
- deleted 13y ago[deleted]