Le betaguy est très bien informé !
Florilèges:
[...]
For Windows Vista, Microsoft had to change their design and development strategy in order to comply with the DoJ and EU regulations regarding the anti-trust issues present in previous versions of Windows; specifically, the integration of assistive applications such as Internet Explorer and Windows Media Player into the core operating system. Competitors complained that offering internet and media solutions with the operating system harmed competition in the marketplace (despite other operating systems such as Mac OS X and Linux apparently being immune from such criticism).
[...]
shifting more towards modular designs rather than the monolithic processes used in previous versions of Windows. This increased amount of componentization, while satisfying the DoJ and EU, also led to performance issues due to the increased number of libraries which comprise the operating system. On traditional hard drives, the more separate files which the operating system has to load, the more seeking across the hard drive is required, and therefore overall performance takes a hit.
[...]
Windows 7 takes a different approach to the componentization and backwards compatibility issues; in short, it doesn’t think about them at all. Windows 7 will be a from-the-ground-up packaging of the Windows codebase; partially source, but not binary compatible with previous versions of Windows. Making the break from backwards compatibility is a dangerous proposal but a dream for software developers. Performance of native applications can be increased, distribution sizes can be cut down, functionality can be added without the worry of breaking old applications, and the overall end-user experience can be significantly improved.
[...]
In Windows 7, Microsoft will break from the Windows’ norm by breaking previous API compatibility, offering new API frameworks as a native solution, and providing support for legacy frameworks (COM, ATL, .NET Framework, etc) through monolithic libraries designed to provide the functionality of all previous revisions of the modules in question. This extends/replaces the WinSxS philosophy, providing every single function, past and present, in fully comprehensive libraries. This should allow the majority of legacy applications to run perfectly, while still retaining native performance for applications compiled specifically with the Windows 7 platform in mind.
On peut déjà se réjouir de la migration sur Microsoft Window 7. La question de la compatibilité backwards sera centrale ! Mais pour un saut qualitatif, je pense en effet que tout le monde sera prêt à faire le pas…
