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 533615
To read all comments associated with this story, please click here.
RE[5]: Window opportuniry
by darknexus on Sun 2nd Sep 2012 18:50 UTC in reply to "RE[4]: Window opportuniry"
Member since:

darknexus: I don't know what OS you normally use, but you seem to be talking about Linux from years ago. I run Fedora on the desktop, and while I have run into some issues, none of them were ever bad enough to keep me from being able to use the system. Part of the issue is that Linux is constantly updating. Linux is under continual advancement.

You've just said it yourself. Most people don't want to be constantly updating, and they're quite content to have a few years between versions. The bleeding edge is called that for a reason, you know.

-While X is certainly a bit old, it has enterprise features that other OS's still don't support, especially when it comes to multi user systems, which Windows and OS X are NOT.

Hmm, where to begin? First, the home user doesn't care one bit if their os has enterprise features. What they se is this: graphics crashed, all my programs went down with it. They do not care if it's because of unstable half-implemented video drivers, nor that some enterprise-level feature is present. They want it to work and do so relatively reliably. X, due to a combination of age and driver instability, is not reliable enough on an unpredictable home user situation. Yes, you can do amazing things with it on the corporate desktop but, to 99% of users, those features will never see the light of day. The other 1%… well, they're already using aren't they? As for multi-user systems… you accuse me of talking about the Linux from years ago. I'll come right back and say you are talking about the Windows from years ago, and OS X? OS X was built on a UNIX userland (FreeBSD-based to be precise) from day one. You do not get much more multi-user than that and yes, I have administered Macs in a multi-user configuration. They are just as multi-user as Linux with, with the advantage of easy configuration in most situations. If you can claim, with a straight face, that OS X and Windows (at least the NT-based versions) are not multi-user, then I'm sorry but I have to take away your geek card. ;)

I have used pulse since it was put in Fedora. In at least the last 2 years I haven't had a single problem.

I'm going to go out on a limb and say that you don't do much audio recording or editing, and that you don't use VOIP software to keep in contact with people. Sure, you can play your music through Pulse and usually it will work, but for recording or gaming the latency is just staggering.

Your kernel API's are going to change. Its a fact of life. They do in Windows and OS X as well. Your user space APIs are stable. I can run software that was produced half a decade ago with no problems. (like Loki games).

That doesn't matter if distro x (Ubuntu, I'm looking at you) decides to patch glibc and break binary compatibility. It does happen. Add to that, drivers are not stable in Linux, by which I mean that I cannot simply download a driver and load it. No, it has to match the kernel version and compilation that I have in whichever distribution I'm running. That's ridiculous. I can run drivers, 32-bit ones at least, on Windows 7 now that were created when XP was released. It's not recommended of course, but there are times when it just has to be done. I don't care, and neither does the average user, about what happens to the internal kernel APIs. That's not what I'm talking about. If you are going to change those internal APIs though, you need to keep the external interfaces the same (a userland for drivers if you will). This is what Windows and OS X do, and guess what, it works. All the user has to do is download a driver for their version of the os (or the closest available if there isn't one), install it, and go. It's not that simple in Linux and, until it is, no one except developers and corporate IT departments will adopt it. It will never be that simple because maintaining such a stable external API isn't fun. It's that 20% that no one in the Linux community ever want to do because it doesn't have the shiny factor.

I won't deny that Linux has some issues to work out to get to the desktop. But its not as bad as you make it out to be. Half or more of the problem you listed will never affect normal desktop users anyway.

Come back when you've actually tech supported normal users on Linux as I have. Every problem I've listed is a recurring theme and has been for the last ten years, with the exception of Pulseaudio which is newer. It works for you. It can work for me. We both have the technical knowledge to fix it when something unexpected happens. Most people do not and, while both Windows and OS X can and do break, overall they break far less often. The breakage needs to keep to a minimum for a home desktop and, though programmers don't like to hear it, that means giving up new feature X and fixing old bugs in their programs. It's not fun. It's not rewarding. You'll never get recognized for fixing bugs and keeping stability. It is necessary, however, and this concept is fundamental to the desktop experience.

Reply Parent Score: 4