4 ms·
And now we're stuck with decades old software and API stacks while Metro/Modern UI/UWP struggles to take off since about 5 years.
by Longhanks 10y ago
And now we're stuck with decades old software and API stacks while Metro/Modern UI/UWP struggles to take off since about 5 years.
- fygdttysf 10y agoThe day MS depracates WinAPI, they're control of the desktop is over, as every company which develops huge codebases will switch to an environment where their programs doesn't have to be rewritten at MS's discretion.
- derefr 10y agoIs there any platform an enterprise could switch to that would guarantee a slower rate-of-change than Windows? "One major rewrite-requiring breaking change in 20 years" sounds like—if not a good deal—the best one I could foresee getting anywhere.
- dispose13432 10y agoOnce you rewrite once, the red line is broken. I think joelonsoftware has an article about that.
- Someone 10y agoIBM (Oracle, too, I would guess). http://www.longpelaexpertise.com.au/ezine/IBMBackwardCompatibility.php http://www.longpelaexpertise.com.au/ezine/IBMBackwardCompati... has a very good observation, though: "The reality is that backward compatibility is only possible if there are enough users paying […] for it." It is the same for Microsoft. If, for example, several big customers would want 16 bit support on x64, I'm sure they would provide it.
- umanwizard 10y agoWhat platform is that?
- pjmlp 10y agoSure they will rather change to a platform in the hands of Oracle,Apple or Google.
- paulddraper 10y ago> stuck with decades old software "reap the rewards of mature software"
- fl0wenol 10y agoThe issue is that this is only of concern to application developers who don't want to use old APIs. Systems owners, managers, and users won't care if it gets the job done predictably and cost-effectively. And if the vendor is willing to keep that stack around and support it...