> So ironically the backwards compatibility MS offers it users come at the expense of backwards compatibility for developer skills. im not sure this follows ne

> So ironically the backwards compatibility MS offers it users come at the expense of backwards compatibility for developer skills. im not sure this follows necessarily: whats to prevent ms from say, writing a wrapper that packages up said legacy apps and supplies the libraries they need, so they can keep running and ms can still dump thier old frameworks and stop supportimg them in newer os's? basically, what im saying is, for legacy apps, they can be "bottled up" and still run on newer systems without harming developer compatibility and modernizing (wine proves this imo) but maybe im missing some important detail...