Linked by Thom Holwerda on Sat 1st Sep 2012 21:15 UTC
Windows The Verge published a video demonstrating how desktop mode and Office 2013 - a desktop application - work on Windows RT, the ARM version of Windows 8. The video showed a desktop mode that clearly didn't work well for touch, and even Office 2013, which has a rudimentary touch mode built-in, didn't work properly either. It looked and felt clunky, often didn't respond properly, and even showed touch lag.
Permalink for comment 533592
To read all comments associated with this story, please click here.
RE[2]: Window opportuniry
by foregam on Sun 2nd Sep 2012 12:54 UTC in reply to "RE: Window opportuniry"
foregam
Member since:
2010-11-17


* Ditching X.org for a working graphics stack (Wayland does look promising)
* Fixing the audio subsystem (ditch ALSA, Pulseaudio, and the rest of that mess and put your resources into OSS 4 which actually works)
* Providing API and ABI compatibility (yes, the Linux lovers say it's unnecessary but it damn well is necessary for commercial software)

BS. Ditch X.org for Wayland? I have very few good words to say about X, but ditching a thoroughly tested and working, though somewhat aged and quite clunky, system for some vapourware is plain stupid. Pulseaudio is a bitch, right, but no-one is forcing you to use it. OSS is already ditched for ALSA, so the chances that ALSA be ditched for OSS4 are quite slim. Re: ABI compatibility, it's right there. Install the libraries you need, load the modules you need and stop whining. I have, and occasionally run, programs from every incarnation of libc: a sourceless ZMAGIC roguelike, some Loki games, a commercial tape backup program from the 2.0 kernel days, some really old version of ApplixWare. That's pretty damn good for me. If you want to say something about GCC ABI compatibility, well, I feel your pain. APIs stay mostly compatible within those projects I track, can't say anything about the general trend.


* Stop trying to tell every commercial developer that they need to GPL everything or open source their drivers
* Thoroughly test all updates to insure that a simple software update won't result in the login screen of death
* Document all system APIs in a consolidated mannor and publish that for third party developers

Nagging vendors for open source drivers is actually useful in the long run — most of them eventually got the message, even Broadcom. The last two are good points, but this is not a single team with a single policy.

Edited 2012-09-02 12:57 UTC

Reply Parent Score: 4