The pressure sensitivity of this is cool but lets not get ahead of ourselves with 'true innovation' - this isn't the tactile feedback multi-use touch surface we've been waiting for.
I own a Surface (journalist freebie hand-me-down), and after playing with it extensively I've determined Surface's only real contribution to society is as a physical manifestation of Microsoft's inability to commit to design decisions. Should it run classic UI or Metro? Should it to run ARM or x86 apps? Should it have a keyboard or a blade? Microsoft's answer to all of these is YES, and that means NO polish and NO market share.
This blade is another example of not committing - are there any launch partners where you can use this with any software you want? Doesn't look like it. So we're to expect musicians are going to drop the music software they've been using for years for a cut-down v1 Microsoft remix app? If not, then who's it for? The uber casual remixer who.. probably already owns an ipad? Pick a market, guys.
I feel bad for the undoubtedly smart folks who put together the blade and the remix app, but who are stuck working on a crappy platform. Building an array of 1000 pressure-sensitive sensors into a touch surface is cool (I'm impressed w new blade touch architecture), but its also something that a committed hacker could do. And after doing it, they'd have as much market share and software partners as Microsoft does with this blade on Surface. So... I wouldn't call it 'true innovation'. Lets leave that distinction to groundbreaking research projects or highly polished new-ish ideas that finally go big.
> Should it run classic UI or Metro? Should it to run ARM or x86 apps? Should it have a keyboard or a blade? Microsoft's answer to all of these is YES
Do you understand anything about how Microsoft works? Supporting everything is their thing, and it is one of the things that has made them big in the first place - for example, my parents (doctors) still use a DOS based program on their Windows 7 machines that has pretty much gone unchanged at its core for over two decades[1]. Now if that isn't vendor lock-in, I don't know what is.
> Supporting everything is their thing, and it is one of the things that has made them big in the first place
Supporting everything made sense when they built an operating system for something that was, for all intents and purposes, a legacy platform (doing ever so well, of course). I presume no one intends to run Promedico on their Surface table though.
Answering "yes" to every possible design question, just to make sure you don't piss anyone off, isn't a solution when you want to provide a well-integrated design. It leads to a messy UI with superficial metaphors and very little flexibility, because there are a million little things that aren't actually meant to work together.
It also complicates the API and the programmer's work, which is the last thing you want to do when you're playing catch-up with the rest of the market.
My commentary was not on how they work - its whether that strategy is competitive in this context. The numbers bear that out. And the fact that they're keeping both x86 and ARM in Surface 2 shows they still have no clue. When you're in 3rd place, last thing you want to do is introduce two entirely different SKUs and wind up in both 3rd and 4th place. That strategy may only work if you're trying to put pressure on chip makers to compete for your business, which requires you have a pretty dominant position in the market, which... they don't.
This has worked for them because the basic form factor of PCs hasn't changed in 30 years. They're still basically an evolution of a mainframe terminal but with the computer inside. Screen, keyboard, pointing device, etc. It's a very capable design but requires you either sit at a desk, or like laptops have a built-in desk that folds down and has an integrated keyboard and pointing device.
True mobile devices such as phones and tablets are very different beasts. They have highly restricted form factors and design parameters such as weight, battery life, screen size, finger-scale touch interface (as against more precise but inconvenient pen or mouse input). These restrictions demand a radical re-think of the UI that effectively closes off a lot of options. Trying to cram in those options anyway, no matter how inappropriate they are to the form factor or how much they compromise the user experience, shows an appalling lack of discipline.
Microsoft looked at the iPhone and iPad and completely failed to understand that it was the clarity and focus of the UI design that made them successful. That it was precisely the jettisoning of desktop UI metaphors and user interface cruft that made them so appealing.
So what Microsoft did was develop exactly such a no-compromises built-for-mobile UI in Metro, and then bolted it on to the side of a crufty old desktop UI, with an array of laptoppy peripherals. They also decided that while the system launches into he new UI, you actually have to figure out how to trigger the invisible gesture to get to the old UI to do anything useful like run Office or change basic system settings. I honestly don't know how they could have botched the whole thing more completely.
So yes, you're right that Microsoft have stuck to form an maintained backwards compatibility at all costs. The problem is that this time that cost is a viable place in the mobile market. The thing is, they don't need to do this. Desktops and laptops are having their market share adjusted downwards to make space for true mobile devices, but they're not going away. Anyone who wants to run traditional Office or legacy DOS applications can still buy a device to do so. There's just no need to the new generation of mobile devices to have to cater to a market that's already catered for. Suppose Microsoft had launched Surface last year with no desktop, Metro only and with a native Metro version of Office and Outlook. I think the situation now would be very different. Maybe that would have been impossible given the time constraints, but that's what needs to happen.
Is there a name for what happens when a vendor gets locked into the technology of its users? E.g. Microsoft basically getting stuck supporting ancient DOS software until the end of time.
This crazy compatibility and lock-in is Microsoft's biggest advantage, but it's simultaneously a huge weakness.
Yeah, sure, they support the Zune players, XNA game development, and Plays for sure music.
/sarcasm
They support lots of things, the things where they are or have been market leaders. But Metro doesn't seem to have the market share to make MS commit to them. Neither does blade.
So, there's no real reason for MS to support them in the long term.
Instead of making a sensor array to just replicate machines that already exist, it is a sensor array that adds a new dimension of creativity and expressiveness. Its these types of innovations we should really be celebrating. I imagine this will be the new norm for high end keyboards in the future.
I'm also skeptical of Tactus. If they would build a similar input pad with embedded actuators that could create the illusion of a click, I would think this could be made more robust. An e-ink display built into the surface, and this would be perfect.
The Microsoft thing is nifty, but it screams "planned obsolescence" to me.
A few years ago, I think around iPhone 4, there were many patents about touchscreen tactile feedback. Some thought it would be what Jobs wanted as the main new thing for the iP4 but it wasn't, and since it fell off the radar or maybe I'm not looking deep enough.
Has Windows improved it's audio latency yet? It's been a while since I did any audio programming for windows, but when I did, the 3rd party ASIO driver system was required to get acceptable latencies. That's not going to work on RT.
I own a Surface (journalist freebie hand-me-down), and after playing with it extensively I've determined Surface's only real contribution to society is as a physical manifestation of Microsoft's inability to commit to design decisions. Should it run classic UI or Metro? Should it to run ARM or x86 apps? Should it have a keyboard or a blade? Microsoft's answer to all of these is YES, and that means NO polish and NO market share.
This blade is another example of not committing - are there any launch partners where you can use this with any software you want? Doesn't look like it. So we're to expect musicians are going to drop the music software they've been using for years for a cut-down v1 Microsoft remix app? If not, then who's it for? The uber casual remixer who.. probably already owns an ipad? Pick a market, guys.
I feel bad for the undoubtedly smart folks who put together the blade and the remix app, but who are stuck working on a crappy platform. Building an array of 1000 pressure-sensitive sensors into a touch surface is cool (I'm impressed w new blade touch architecture), but its also something that a committed hacker could do. And after doing it, they'd have as much market share and software partners as Microsoft does with this blade on Surface. So... I wouldn't call it 'true innovation'. Lets leave that distinction to groundbreaking research projects or highly polished new-ish ideas that finally go big.