Linked by Thom Holwerda on Fri 24th Jan 2014 20:17 UTC
Windows

One more tidbit about Windows 8.1 Update 1 from my aforementioned source: Update 1 may feature some of the work that Microsoft has been doing behind the scenes to reduce further the memory and disk space requirements for Windows. This would allow Windows 8.1 Update 1 to run on cheaper small tablets.

Windows 8.1 Update 1, screen shots of which leaked earlier this week, is expected to allow users to pin Metro-style/Windows Store apps to their desktop task bars. Thumbnail previews of these Metro-style apps will be available from the Desktop task bar, according to additional screen shots. Windows 8.1 Update 1 also is expected to include close boxes for Metro-style apps.

Seems like some welcome changes, but it's going to take a lot more for people to warm up to Metro. The biggest problem to me is that since there aren't any compelling Metro applications, there's simply no reason to put with its idiosyncrasies, especially on desktops. I cannot think of a single Metro application that is better than its desktop counterpart, nor is there any Metro application that is better than similar applications on competing platforms.

Developers need users, and users need developers. Right now - Metro seems to lacks both.

Permalink for comment 581685
To read all comments associated with this story, please click here.
RE: Comment by Nelson
by dpJudas on Sat 25th Jan 2014 13:29 UTC in reply to "Comment by Nelson"
dpJudas
Member since:
2009-12-10

You solve the developer/user catch 22 with a lot of money and patience, which Microsoft has. They solved it with Windows Phone.

I don't think it is this simple. Money and patience only goes so far.

In my opinion Microsoft made a lot of strategic errors in how they would lure developers to their new platform.

First they overestimated how many .Net developers would adopt it. The entire new WinRT system was designed to make it as easy as possible for C# devs to migrate, but this move seem to have failed. I think part of the reason has been that the typical C# developer does web applications and they didn't switch to App development over night as Microsoft had hoped.

At the same time they made it annoyingly hard for the traditional Desktop developers to adopt their new platform. A mixture of dropping all older API's (GDI, common controls, MFC, winforms, etc.), blocking LoadLibrary usage and not having Windows 7 support for C++/CX meant that they effectively asked any existing Desktop player to rewrite their entire user interface, and sometimes part of the backend as well. The end result has been that virtually all of them decided to wait and see. The fact that Microsoft themselves had to make an explicit exception for Microsoft Office shows just how much work they were asking to be rewritten.

Money and patience will only fix these problems when Windows 8 gains a significant marketshare (by forcing people to invest like happened with Objective C and Cocoa Touch), but even this assumes people won't simply begin to ignore the Modern section of Windows 8.

Reply Parent Score: 4