Miguel de Icaza on Longhorn changes

Interesting post by Miguel de Icaza on Microsoft's recently announced changes to Longhorn. Good to read if only to get a better understanding of the complexities of Avalon's implementation.

My prediction is that Avalon v1 will be a throw-away: it is not really the foundation on which you will build applications: V2 will likely not be backwards compatible, they will have to re-architect bits of it: which means that people will end up with two frameworks running side-by-side: Avalon V1 and Avalon V2.

The above problem is compounded with the fact that the CLR has not really sorted out a good model for sharing components across versions of the framework: the GAC solution today is a bit of a hack to keep things separate and allow for multiple installations, but does not solve

This is like cooking, you can not rush a good steak, or a cake or an omelette by cranking the heat. Some things just take time. [Via Miguel de Icaza]

No Comments