Maybe Mozilla just doesn’t know how to work with Windows, or they have such junk code (which they keep saying they are fixing the memory leaks). Google had no issue with Metro. http://www.theverge.com/2012/6/12/3079985/google-chrome-metro-style-windows-8-hands-on and Google is about as “non-sanctioned” as you get. From: Steve Bogdanski [mailto:[log in to unmask]] Problems with the grand "unification" strategy from M$: - There will be too different kernels, one for x86 and one for ARM, this will inherently cause fragmentation as some programs are developed for only one platform or their feature sets vary. Office 2013 is a great example since I have heard both that the two versions will be feature-equal and that there will be differences (who to believe). - The new interface (i.e. the UI formally known as Metro) only works well with newly designed applications and M$ hasn't been too helpful with many developers in getting non-sanctioned apps to work (just ask Mozilla). Microsoft still allows for legacy apps, but pretty much deprecates them. The looks/feel of non-UI-formally-known-as-Metro apps is horrible and I am sure many of you out there have to run one or more legacy apps for the foreseeable future (try dealing with medical and research software vendors). - There are two drastically different hardware platforms Win8 covers, touch-based and traditional keyboard/mouse, literally forcing the same UI on both is stupid. Not giving end-users an easy way to revert to the traditional (non-UI-formally-known-as-Metro) desktop and start menu is just pig-headed. There is a reason Apple still runs separate OSes for their desktop/laptop and touch-based systems (and I do not care what people say, Apple knows UI). PS: I am having deja vu regarding a similar thread on the NAG list when Vista came out years ago ;) PPS: I won't bring out the "shiny ball" comparison again
|