Linked by Thom Holwerda on Mon 23rd Sep 2013 16:53 UTC
Windows

While on stage, Microsoft Vice President of Surface Panos Panay explained how the teams have worked hard in making the next generation of Surface tablets cooler, lighter, quieter, more efficient and have longer lasting power reactors. The Surface Pro 2 was up first and is all about power, with new covers and better components to further improve the user experience. If you're after the premium Surface experience, this will be the correct choice.

[...]

The Surface 2 is lighter, has a faster CPU and now sports a 1080 display with ClearType. Powering Windows RT 8.1, the Surface 2 brings new exciting features to the table, without bumping the price above the competition.

Specification bumps all around, and thinner, lighter, and changes borne from customer feedback, such as the adjustable kickstand. I like the full HD display on the Surface 2 (the ARM version of Surface), and the Haswell improvements to power and battery life on the Surface Pro 2 are substantial.

Still, as a Surface RT owner, the hardware has never been the issue. My Surface RT is a very enjoyable piece of hardware to hold - well-built, sturdy, solid, and very well designed. Specification-wise, it packs more than enough power, too. Sadly, Surface was let down by software; Windows RT and the Metro interface are simply not of decent enough quality, and the applications for it are even worse - slow, jittery animations, crash-prone, rarely updated. All the hallmarks of side projects; things developers may work on when they're not working on Android or iOS applications.

Windows 8.1 seems to have fixed little of those issues (although Surface RT owners are still waiting for the final release), and with Microsoft's notoriously slow development pace, I hardly see that change any time soon.

Thread beginning with comment 572913
To view parent comment, click here.
To read all comments associated with this story, please click here.
acobar
Member since:
2005-11-15

I will keep on solving problems for my employer using it. I really don't like it when people slag off .NET because tbh you won't find a better designed core API.

And I am still waiting for the big project that will make use of all the potential .NET, XAML and all provides. I see lots of small projects that are great to interact with MS business backends, though. Perhaps, I have my fingers burned by the first iterations and should try it again but most of my things are on Linux/Android camp right now.

Reply Parent Score: 2

lucas_maximus Member since:
2009-08-18

I really like questions that are loaded, because they are easy to debunk.

ASP.NET and the .NET if you actually followed any of their blog posts or correspondence of any sort are basically trying to let yo load stuff up like Lego ... i.e as a set of components.

This attitude is generally present now in the ecosystem.

Reply Parent Score: 2

Nelson Member since:
2005-11-29

He's obviously never used OWIN, its pretty much awesomesauce for webdev

Reply Parent Score: 3

moondevil Member since:
2005-07-08

And I am still waiting for the big project that will make use of all the potential .NET, XAML and all provides. I see lots of small projects that are great to interact with MS business backends, though. Perhaps, I have my fingers burned by the first iterations and should try it again but most of my things are on Linux/Android camp right now.


Well, at my employer we have lots to choose from.

Just as an example, the last .NET project I took part on, was a two year project, with more than 30 developers on average, scattered in three development sites.

It made use of IIS, ASP.NET, App Fabric, SiteCore, SQL Server, SAP, REST/SOAP, jQuery, TFS, partial deployment in Amazon EC2.

In terms of project costs and profit, you could buy a few houses.

There are plenty of big C++/Java/.NET in the Fortune 500 consulting world to choose from.

Reply Parent Score: 4