Category Archives: microsoft

microsoft, professional, windows

Windows 8 to be called Windows 8, no Outlook on ARM

5 Comments

Microsoft has announced the range of editions planned for Windows 8, which is now the official name (previously it was a code name).

Here is what I found interesting. Windows on Arm (WOA) is now called Windows RT and ships with Office included. However, Outlook is not included, confirming my suspicion that Outlook may gradually get de-emphasised in favour of separate email, calendar and task managers built into the operating system but with strong Exchange support – a good move since Outlook is perhaps the most confusing and over-complex application that Microsoft ships.

Windows RT is missing some features which are in the Intel versions, not least the ability to install desktop software, but has an unique feature of its own: device encryption.

I consider Windows RT as critical to the success of the Windows 8 project, and the only edition that may compete effectively with the Apple iPad in terms of price, convenience, battery life and usability. That said, the market will see the Intel version as primary, since it is the one that can run all our existing apps, but all the legacy baggage will also weigh it down. Users will suffer the disjunction between Metro and Desktop, and will need mouse or stylus and keyboard to use desktop applications. The danger is that Windows RT will get lost in the noise.

microsoft, mobile, silverlight, software development, visual studio

Windows Phone and Windows 8 convergence: a few more hints from Microsoft

9 Comments

The moment when Nokia is in the midst of the US launch for its Lumia 900 phone, which both Nokia and Microsoft hope will win some market share for Windows Phone 7, is not the best time to talk about Windows Phone 8 from a marketing perspective. Especially when Windows Phone 8 will have a new kernel based on Windows 8 rather than Windows CE, news which was leaked in early February and made almost official by writer Paul Thurrott who has access to advance information under NDA:

Windows Phone 8, codenamed Apollo, will be based on the Windows 8 kernel and not on Windows CE as are current versions. This will not impact app compatibility: Microsoft expects to have over 100,000 Windows Phone 7.5-compatible apps available by the time WP8 launches, and they will all work fine on this new OS.

Nevertheless, Microsoft is talking a little about Windows Phone 8. Yesterday Larry Lieberman posted about the future of the Windows Phone SDK. After echoing Thurrott’s words about compatibility, he added:

We’ve also heard some developers express concern about the long term future of Silverlight for Windows Phone. Please don’t panic; XAML and C#/VB.NET development in Windows 8 can be viewed as a direct evolution from today’s Silverlight. All of your managed programming skills are transferrable to building applications for Windows 8, and in many cases, much of your code will be transferrable as well. Note that when targeting a tablet vs. a phone, you do of course, need to design user experiences that are appropriately tailored to each device.

Panic or not, these are not comforting words if you love Silverlight. Lieberman is saying that if you code today in Silverlight, you had better learn to code for WinRT instead in order to target future versions of Windows Phone.

The odd thing here is that while Lieberman says:

today’s Windows Phone applications and games will run on the next major version of Windows Phone.

(in bold so that you do not doubt it), he also says that “much of your code will be transferrable as well”. Which is equivalent to saying “not all your code will be transferrable.” So how is it that “non-transferrable code” nevertheless runs on Windows Phone 8 if already compiled for Window Phone 7? It sounds like some kind of compatibility layer; I would be interested to know more about how this will work.

I was also intrigued by this comment from Silverlight developer Morton Nielsen:

Its really hard to sell this investment to customers with all these rumors floating, and you only willing to say that my skill set is preserved is only fuel onto that. The fact is that there is no good alternative to Silverlight, and its an awesome solution for distribution LOB apps, but the experience on win8 is horrible at best. And it doesn’t help that the blend team is ignoring us with a final v5, and sl5 is so buggy it needs 100% DEET but we don’t see any GDRs any longer.

What are these acronyms? DEET just means insect repellent, ie. bug fixes. GDR is likely “General Distribution Release”; I guess Nielsen is saying that no bug-fix releases are turning up are turning up for Silverlight 5, implying that Microsoft has abandoned it.

All in all, this does not strike me as a particularly reassuring post for Windows Phone developers hoping that their code will continue to be useful, despite Lieberman’s statement that:

I hope we’ve dispelled some of your concerns

Still, it has been obvious for some time that WinRT, not Silverlight, is how Microsoft sees the future of its platform so nobody should be surprised.

Update: Several of you have commented that Lieberman talks about WinRT on Windows 8 not on Windows Phone 8. Nobody has said that WinRT will be on Windows Phone 8, only that the kernel will be the that of Windows 8 rather than Windows CE. That said, Lieberman does specifically refer to “the long term future of Silverlight for Windows Phone” and goes on to talk about WinRT. The implication is that WinRT is the future direction for Windows Phone as well as for Windows 8 on tablets. Maybe that transition will not occur until Windows Phone 9; maybe Windows Phone as an OS will disappear completely and become a form factor for Windows 8 or Windows 9. This aspect is not clear to me; if you know more, I would love to know.

development, microsoft, software development, visual studio, windows

Run Metro apps in a window on Windows 8

1 Comment

I have been drilling into Visual Studio 11 beta recently. This includes a simulator for debugging Windows 8 Metro style apps and I was surprised by the way it works. Unlike the Windows Phone emulators, which are isolated environments for testing apps, the simulator is actually a window into your own machine.

image

You can do some strange stuff. For example, you can not only debug your app in the simulator, you can run up Visual Studio 11 on the desktop within the simulator and edit it as well. It will not let you run the simulator within the simulator though – I tried!

It occurred to me that the metro simulator accomplishes one of the things some users of the consumer preview have asked for. It lets you run Metro apps in a window, so that you can resize them, minimize them, and avoid the jarring context switch between full-screen Metro and the normal desktop with the taskbar.

image

What is the simulator? It is actually a remote desktop session into your own machine. Normally you cannot do this, as Windows client only allows one session at a time and you already have one running, but Microsoft has given itself special permission.

Running Metro apps in a windows is not its intended purpose but it is interesting to try as it shows how this might have worked if Microsoft had taken a more desktop-centric approach to the dual personality in Windows 8.

A further thought is to consider why the Visual Studio team decided to do things this way. Microsoft’s developers saw the necessity of working in the Visual Studio IDE while also exercising the Metro-style app.

Well, what if you are not a developer, but you still want to have Excel open while you check out, for example, the Bing Finance app? It is not only developers that may have good reasons to have a desktop and a Metro app running side by side.

Dual monitors accomplish this of course, and to some extent so does the “Snap” split view if you have the right screen resolution, but running Metro in its own window is a rather convenient solution.

development, microsoft, software development, visual studio

Developers dislike monochrome Visual Studio 11 beta

7 Comments

Microsoft is having trouble convincing developers that its new Metro-influenced Visual Studio user interface, in the forthcoming version now in beta, is a good idea.

To be more precise, it is not so much Metro, but the way Microsoft has chosen to use it, with toolbox icons now black and white. The change also affects menus such as IntelliSense in the code editor. Here is the new design:

image

or you can choose a “Dark” colour scheme:

image

and the old 2010 design for comparison:

image

Developers voting on this over at UserVoice, the official feedback site, have made this the single biggest issue, with 4707 votes.

image

They do not much like the All Caps in the toolbox names either.

Microsoft has marked this as “Under review” so maybe there could yet be a more colourful future for Visual Studio 11.

microsoft, open source

Microsoft open sources further ASP.NET Frameworks, publishes code with Git

Microsoft has released two further ASP.NET frameworks as open source, joining ASP.NET MVC which was already open source. These are published on CodePlex, Microsoft’s open source repository site, using the newly added Git support. You can find the code here.

The two additional frameworks are ASP.NET Web API and ASP.NET Web Pages. Just to recap, ASP.NET supports several frameworks:

ASP.NET Web Forms: the original framework shipped with .NET 1.0 and greatly enhanced since then. Excellent for quickly assembling a dynamic web site but somewhat heavyweight with its ViewState field and complex page lifecycle. Designed in pre-Ajax days.

ASP.NET MVC: A more elegant framework with separation of content from code, amenable to test-driven development, based on controllers and routing.

ASP.NET Web Pages formerly known as Razor: An alternative view engine designed to work with ASP.NET MVC. Uses .cshtml or .vbhtml extension in place of .aspx. A declarative language with codewords like @foreach and @if – though Microsoft’s Scott Guthrie says it is not a language but rather a template markup syntax.

ASP.NET Web API: formerly known as WCF Web API is a framework for building REST services. A key framework if you have a cloud + mobile target in mind. Now gets installed with ASP.NET MVC.

So why is ASP.NET Web Forms not open source? According to Microsoft’s Scott Hanselman:

The components that are being open sourced at this time are all components that are shipped independently of the core .NET framework, which means no OS components take dependencies on them. Web Forms is a part of System.Web.dll which parts of the Windows Server platform take a dependency on. Because of this dependency this code can’t easily be replaced with newer versions expect when updates to the .NET framework or the OS ships.

though it is not clear why this prevents the code being published.

Hanselman adds that Microsoft is not only publishing the code, but also taking contributions:

Today we continue to push forward and now ASP.NET MVC, Web API, Web Pages will take contributions from the community.

Why is Microsoft doing this? Within Microsoft, there have always seemed to be open source advocates like Hanselman, and others who pull back. One answer is that the open source folk are winning more arguments now.

Another take is that this is the outcome of industry-wide changes. Microsoft’s platform is less dominant than it was; it still reigns on the desktop, but Macs, tablets and smartphones are eroding its position on the client, and on the web Netcraft’s figures show steady decline since June 2010:

image

Most of the competition is open source and it is possible that this is a factor behind the latest moves. Microsoft is not open sourcing its IIS web server yet, though Hanselman does make the point that ASP.NET MVC runs well on Mono, the open source implementation of the .NET Framework, which is often used with Apache.

.net, microsoft, professional, software development, visual studio, windows

Developers: will you do Metro?

6 Comments

It is fascinating to watch the Metro-fication of all things Microsoft, from the Xbox 360 user interface to Windows Phone to Windows 8 to forthcoming versions of Office and other applications.

Future versions of Dynamics products were previewed at the Convergence 2012 event (which included a session called CRM goes Metro) and there are a bunch of screenshots here.

image

Microsoft calls Metro a design language and you can see its guiding principles here. Calling it a language does not seem quite right; the word “style” is more accurate, but it does have building block elements (and yes it is blocky) which I guess make it more than just a style.

A safe prediction at this point is that all Microsoft’s products will be touched by Metro influence, even though not all will become full Metro apps running on the Windows Runtime (WinRT).

In the past the style adopted by Microsoft for its own applications have strongly influenced third-party applications as well. Once Windows, Office, Dynamics and other apps have a Metro look, other apps that do not may begin to look dated or out of place.

Metro is controversial though, perhaps even more so than the Office Ribbon which replaced menus in Office 2007 and 2012. There is some connection: members of the Office team who worked with Steven Sinofsky on the design of Office 2007, including Julie Larson-Green and Jensen Harris, are now working with him on Windows 8. Harris has written extensively about the work on Office 2007 on his Office User Interface Blog, though the last substantial post was in 2008.

What’s not to like about Metro? Here’s a few arguments against:

  • Beauty is in the eye of etc; but the blockiness of the Metro style does give it a utilitarian appearance. In Windows Phone 7 it is nice to use, but not so great to look at.
  • The Live Tile concept, where shortcut blocks can be populated with current information, adds a random element to Metro start screens which does not always look good.
  • The emphasis on simplicity and immersion makes Metro vulnerable to the accusation that it wastes too much precious screen space.
  • Metro tends to be a horizontally scrolling style, though I am not sure if this is baked into the guidelines. This takes some adjustment since most of us are more used to vertical scrolling to see more content.
  • Metro seems to be optimized for a touch UI, and while its advocates insist that it is just as good with keyboard and mouse, that is a stretch. Metro seems to be a big bet on touch as the future of human-computer interaction.

On the other hand, the usability of Windows Phone 7 is a point in its favour, and some are convinced. Paul Greenberg, in a positive take on Microsoft’s strategy based on his trip to Convergence 2012, says:

They have nailed UX (a.k.a user experience). Nailed it. Their combination of the extremely well done Metro interface and their work on natural user interfaces involving voice and touch is the new gold standard – and I’m someone who loves Apple products. (please, Mac fanboys, spare my life.)

I would be interested to hear from developers whether you expect to embrace the Metro style in your apps, wither in WinRT or elsewhere.

business intelligence, microsoft, professional, software development, sql

What’s new in SQL Server 2012?

8 Comments

Microsoft’s SQL Server 2012 is released next month and available to download now (I am not sure what the distinction is). I have a high regard for Microsoft’s database server; it seems to me that the team mostly gets it right. The product has become somewhat diffuse though, especially as the Business Intelligence aspect has grown, and this may account for what to me is a rather unfocused launch for SQL Server 2012, even though its name suggests that it is the most significant release since SQL Server 2008.

The following slide summarises the new features, presumably with the type size suggesting the importance of each one.

image

But is the ODBC Driver for Linux really more important than the SQL Server Data Tools, for example? Not in my view; but that reflects how SQL Server represents different things to different people.

So what are the key new feature? Here’s my quick take.

Always On

A new feature called Availability Groups that is an improved version of database mirroring

Improved failover clustering which supports multi-site clustering across subnets – above to failover across datacentres.

ColumnStore Index

A new type of index for data warehouses. This is actually pretty simple: the name says it all. Here is Microsoft’s illustration:

image

and explanation:

A columnstore index stores each column in a separate set of disk pages, rather than storing multiple rows per page as data traditionally has been stored.

Why do this? Because it is more efficient when the query only requests a a few columns from the table. Microsoft claims performance improvements from 6X to 100X in cases where the the data can be cached in RAM, and thousand-fold improvements where the working set does not fit in RAM.

SQL Server Data Tools

This is my favourite feature, probably because it is developer-focused. These are the tools that were code-named “Juneau” and which install into Visual Studio 2010. There are some visual tools, but this is essentially a code-centric approach to database design, where you design your database with all its tables, queries, triggers, stored procedures and so on. You can then build it and test it against a private “localdb” instance of SQL Server. What I like is that the database project includes the entire design of your database in a form that can be checked into source control and compared against other schema versions. Here is the Add New Item dialog for a database project:

image

Data Quality Services

Data Quality Services (DQS) lets you check your data against a Data Quality Knowledge Base (DQKB), the contents of which are specific to the type of data in the database and may be created and maintained by your business or obtained from a third-party. If your data includes addresses, for example, the DQKB might have all valid city names to prevent errors. Features of DQS include data cleansing, de-duplication through data matching, profiling a database for quality, and monitoring data quality.

image

Illustration and more details are here.

Updated SQL Server Management Studio

SQL Server Management Studio now runs in the Visual Studio 2010 shell.

LocalDB

LocalDB is a local instance of SQL Server aimed at developers and for use as an embedded database in single-user applications. It is a variant of SQL Server Express, but different in that it does not run as a service. Rather, the LocalDB process is started on demand by the SQL native client and closed down when there are no more connections. You can attach database files at runtime by using AttachDBFileName in the connection string. LocalDB is intended to replace user instances which are now deprecated.

FileTables

This is the most intriguing feature in SQL Server 2012. It is described here:

The FileTable feature brings support for the Windows file namespace and compatibility with Windows applications to the file data stored in SQL Server … In other words, you can store files and documents in special tables in SQL Server called FileTables, but access them from Windows applications as if they were stored in the file system, without making any changes to your client applications.

and the purpose:

Enterprises can move this data from file servers into FileTables to take advantage of integrated administration and services provided by SQL Server. At the same time, they can maintain Windows application compatibility for their existing Windows applications that see this data as files in the file system.

Integration of the file system and the database is not a new idea, and Microsoft has tried variants before, such as the “M” drive that was once part of Exchange, the aborted WinFS feature planned for Windows Longhorn (Vista), and SharePoint, which can store documents in SQL Server while presenting them as Windows file shares through WebDAV.

That said, FileTables in SQL Server 2012 are not an attempt to reinvent the file system, but presented more as a way of supporting legacy applications while managing data in SQL Server. It is an interesting feature though, and it would not surprise me if users find some unexpected ways to exploit it.

Power View

Codenamed “Project Crescent”, this is a web-based reporting client for businesses that have embraced Microsoft’s platform, because it has several key dependencies:

  • SharePoint Server Enterprise Edition
  • SQL Server Reporting Services
  • Silverlight on the client

In fact, Power View is described as:

a feature of SQL Server 2012 Reporting Services Add-in for Microsoft SharePoint Server 2010 Enterprise Edition

Power View reports that I have seen do look good, and have an Office ribbon style designer for designing customising the report. That said, I would guess that Microsoft now wishes it had used HTML 5 rather than Silverlight for this – there are those Apple iPad and Windows 8 Metro users to think of, after all.

Microsoft emphasises that Power View is not a replacement for Report Designer or Report Builder, but an ad-hoc reporting tool.

Closing thoughts

There is more in SQL Server 2012, as a glance back at the initial slide will tell you, but the above is a starting point if you are wondering what it is all about. It is also worth noting that Microsoft still gives away SQL Server Express which supports up to 10GB per database and includes many of same features as the paid-for versions; it is the same product at heart.

Someone who finds that SQL Server Express actually meets all their needs asked me why Microsoft gives it away. My guess is that this is a consequence of all the other free database engines available such as MySQL, PostgreSQL, interesting  newer NoSQL options like mongoDB, and of course equivalent free versions of Oracle and IBM DB2. A proportion of customers who start with SQL Server Express will grow into the paid-for editions.

This does make SQL Server Express an excellent choice for smaller scale applications and small businesses, particularly since it integrates smoothly into Microsoft’s developer stack. Having said which, I am becoming something of an Entity Framework sceptic, but that is a story for another day – and fortunately you do not have to use EF if you do not want to.

microsoft, windows

Fixing a Metro-style app in Windows 8 Consumer Preview

4 Comments

I am a fan of Wordament for Windows Phone and Windows 8. This is a Metro-style app. I was annoyed though to discover that it was broken on my Windows 8 slate. That is, it could not be launched because it did not exist when searching the Start menu, nor in the “All apps view”, but it could not be installed because the Store considered that it was already installed.

I could go into Store – Settings – Accounts and see it listed under “View your apps”, where it also said it was installed.

There was some kind of warning of problems, in that from time to time Windows 8 had been offering to fix a problem with Wordament, usually after I had set the slate to sleep while the app was running. When prompted, I always accepted and let it do its stuff, but the result of the last effort was the app had disappeared completely.

How to fix this? I found one piece of official advice for a similar problem which suggested refreshing the PC. This is not much fun because you lose all installed applications other than Metro apps – ugh. I did a bit of digging.

My first thought was to try manually deleting the app to see if I could trigger a reinstall. I got a little way with this. I found that Metro-style apps are installed into the WindowsApps folder, which is a sub-folder of Program Files. However, if you double-click this folder you get an access denied message, though the message also invites you to continue.

image

I did not wish to trample all over the security features of Windows 8, though following a hunch I did try restarting in safe mode. You can do this by choosing Settings – More Settings and clicking Restart now under Advanced startup. The PC restarts and you get to a “Choose an option” screen where you can click Troubleshoot. Next, click Windows Startup Settings and then Restart. This gets you the familiar F8 options including Safe mode.

In Safe mode you have read-only access to the WindowsApps folder, and there I could see the Wordament install files.

image

Here you can verify that this is an HTML and JavaScript app, just as its creators said. The JavaScript is minified so opening it up is not all that rewarding.

image

Still, I could confirm that the app was in fact installed, but I could not run it.

I had another idea. If all I needed was a shortcut to the app, perhaps I could grab one from another profile on the machine. I restarted in normal mode, created another user (which must be one with a Microsoft Live ID) and logged in as that user (shutdown /l logs off without shutting down). I installed Wordament, and it ran fine.

So where are the per-user shortcuts? Easy, just go along to c:\users\[username]\AppData\Local\Microsoft\Windows\Application Shortcuts and there they are.

image

Again I had to grab permission to access this folder, but doing this in a user folder is not so bad as in a system folder.

I copied the shortcut to the same location in my normal home folder and lo, Wordament reappeared in the Start menu.

image

Not too bad; but it seems to me that Windows 8 should have a built-in way of fixing this kind of problem – perhaps it has, and I missed it.

linux, microsoft, professional

Microsoft deprecates Subsystem for UNIX, recommends open source instead

3 Comments

I am getting started with the Windows Server 8 beta and noticed this in the list of Features Removed:

The Subsystem for UNIX-based Applications (SUA) is deprecated. If you use the SUA POSIX subsystem with this release, use Hyper-V to virtualize the server. If you use the tools provided by SUA, switch to Cygwin or Mingw.

Cygwin and Mingw are open source tools which let you use some Unix tools on Windows. That said, my preference would be the virtualisation route, rather than installing these layers on Windows Server itself.

microsoft, Uncategorized, windows

Crisis in Microsoft land: what next after the mixed reception for Windows 8 Consumer Preview?

60 Comments

Microsoft will have expected some users to find the transition from Windows 7 to Windows 8 challenging, but I doubt it was ready for the reaction from its own community that it is receiving for Windows 8 Consumer Preview.

image

The best place to start is the comments on Building Windows blog here and here – at the time of writing, around 1300 comments, most from users who have downloaded and tried the Consumer Preview. It is worth browsing through them if this is something you care about; some are knee-jerk negative reactions, but some others are thoughtful and wanting Microsoft to succeed.

Overall, the message is: don’t make us use Metro, let us stay in the desktop if we choose.

I’m still waiting for an explanation as to why my 30" desktop screen has to look like a smartphone, that’s what my smartphone is for.

My users range from tech savvy to plant workers and truck drivers. Like all of us, the start button is baked into our DNA … How can I make the desktop the default UI?  I’m not going to deploy metro desktop to my users as the default screen. I would rather deploy a slew of ipads and I’m no ipad fan that is for sure.

In 17 years of using Windows I have never used the Windows key. Interestingly I’ve never seen any user of a computer use the Windows key. I don’t want to learn and remember key combinations to do things that I can currently do trivially using the start menu.

Let me tell you something, I always have a gazillion webbrowser instances and tabs open (rarely less than 50 browser tabs and as much as 100) – I often run 5-10 Visual Studio instances simultaneously (and I know your usage statistics says average is 1, so you won’t make it easier to distinguish between them, but this is a different matter..) – usually have 10+ explorer windows – and I absolutely love working this way, I am productive this way and that’s what counts for me. I run 2 big screens with 2560×1440 resolutions to give me as much working space as possible, so I can easily switch between a lot of my open applications, browser tabs and explorer windows. Even if I had a use for some Metro UI application, I would be looking for a desktop alternative, so I could have it running side-by-side with my other applications – let’s be honest, one application at a time might be great for the average joe, but it’s a horrible solution for professional users.

Part of the problem here is that the Metro UI Windows 8 is more about solving a problem Microsoft has – how to compete with the iPad – than a problem its users face. It has been clear since Windows 8 was first previewed that the tablet UI and new Windows Runtime was Microsoft’s main focus, and that desktop users would get less value than they might normally expect from a major release. The reaction to the Consumer Preview though is more serious than that: many users are saying that Windows 8 is, for them, a substantial step backwards.

I am writing this in Windows 8 on a desktop and it is not that bad. Apps are easy to launch once you get the hang of Windows Key – Search, and there are workarounds for the annoyances. There is no doubt though: if you are working mainly in the desktop – which is inevitable for most users upgrading – the “immersive UI” does get in the way at times. Since it must run full screen, a Metro app obliterates the taskbar and handy features like the time and date which shows bottom right in the notification area. If there were an option to run Metro apps in a window, I would grab it.

The irony here is that the name “Windows” refers to the ability to run multiple apps in windows, as opposed to the single application UI offered by DOS.

Another issue is that if you switch between Metro and Desktop, you have to learn two ways to do common tasks. For example, I tend to use the taskbar previews to find browser tabs, since if you have numerous tabs open it is the quickest way to find the one you want. If you are in the Metro browser though, you have to right-click to show the tabs. Right-click by mistake in the desktop browser, and you get a context menu. Add to favourites? Different. History? Different. All friction if you just want to get your work done.

If you have multiple monitors, Microsoft’s “Move the mouse to the corner” idea for raising the Charms does not work well. The “Corner” is on the primary display, but if you have multiple displays it is not a corner but the border between two screens. You have to position the pointer just so to make it work.

There is more; but it is not my intention to iterate through every annoyance. I am more interested in the reaction overall and in what Microsoft will do next.

I will add that I admire what Microsoft has done from a technical standpoint in the Windows Runtime and that Windows 8 on a touch device with the right screen size has great promise as a new tablet operating system. It is my first choice for travelling; iPad and Android tablets are too limited, and I am more than ready to leave the bulky, awkward laptop at home.

Needless to say, few of those commenting will have tried such a device, for reasons I have described before. Windows 8 in a virtual machine is a worst case, and it is a shame that so many (for good reasons) are trying it that way.

What next for Windows 8?

It seems to me that Microsoft now has, broadly, three options for Windows 8.

1. Plough on regardless. This, I imagine, is the plan as it stands currently. Microsoft has deliberately made Metro unavoidable in Windows 8, I presume to ensure that it will not be ignored. There will be some refinements in the final release, improved discoverability of features users are struggling to find, but no fundamental change to the design approach. The plan as stated last month is that there will be no further beta, and the next public release will be the release candidate.

The question: can Microsoft do enough tweaking to win over a majority of its own community? Right now my sense is probably not. A negative reaction on release will be costly for the company and for all those third-parties who depend on its platform; yes, Windows 7 will have a prolonged life, but there will be loss of momentum for the platform overall.

2. Delay Windows 8 for further refinement. Go through the reactions to this broad public beta test, and work out how to fix the issues without losing the vision behind this “reimagined” Windows. Delay would be painful, of course, but less bad than a failed release.

The quick version of this would be to do what many are asking for: make the Metro-style personality in Windows 8 optional. Would that be such a disaster?

3. Release Windows on ARM (WOA) ahead of the full Windows 8. Most of the objections users have to Windows 8 do not apply to WOA, where Metro is primary, where all devices are touch tablets, and where those desktop applications (mainly Office) and utilities that are included are there to fill the gaps which Metro cannot yet fill. As for x86, users are still happy with Windows 7. When Vista was the current version, users could not wait for the next release, but there is no such pressure with Windows 7.