Reflexx
New member
- Dec 30, 2010
- 4,484
- 4
- 0
I stopped reading after "fox news"
Reputable and legitimate news agency. Don't know why people get all weird about it.
I stopped reading after "fox news"
this!!!!! i could never use on a phone much less on a tablet because i found it annoying to navigate though menus. and if comes in a computer that's the first thing im taking off my computer ( good thing i build my own ) i never liked google bloatware/malware and i never will"Scare the heck out of Microsoft?" Why? At the very least they'll still be the primary OS on the laptop, and android will be a secondary gimmick. Face it. If I get myself a nice Galaxy S4... I will likely reach for that to play Angry Birds then go through menus to boot up a flaky emulator.
I don't see any revolution against Microsoft. Revolution was threatened by OEMs when the Surface launched. Instead convertible tablets suddenly sprung up everywhere. The supposed revolution against MS turned into an evolution of consumer electronics. I'll be straightforward. If any OEM installs an Android emulator app on my next PC, I'm uninstalling it. I've used Windows 8/8.1 with both a touchscreen and a mouse and keyboard. I've found out one thing. I prefer both over a generic touchpad interface.
Why they didn't do this in the first release is beyond me. It's like MSFT *wanted* Win8 to fail. I imagine most people look at a Win8 computer and ask, "where's my Windows?" (i.e. the one they're familiar with). Then they realize that if they're going to need to learn a completely new UI, they might as well give non-Windows systems a try or wait to see what happens with Win8. Either choice is lethal to MSFT. It will be a much smaller company in 5 to 10 years unless they come to their senses and refocus on the so-called "Desktop" Windows....
This is how MS can fix W8 (technically, I'm not sure the perception of W8 can be saved):
...
If MSFT is dead set on attempting to force the Metro UI on users then they should adopt your plan. If they want to actually succeed then they need to sh*tcan the entire RT effort and do the following:
Why they didn't do this in the first release is beyond me. It's like MSFT *wanted* Win8 to fail.
Windows RT's main problem has little to do with APIs. While I agree that much of the new-fangled APIs are too concerned with looking modern rather than being efficient, scalable, flexible and robust, the bigger reasons for concern are market perception, consumer acceptance, the lack of tablet optimized software for WRT, and the big question revolving around what a touch based interface is doing on people's desktops who use nothing but a keyboard and mouse. If existing customers had welcomed Windows 8.x with open arms, and everyone agreed that it was a must-have update over Windows 7, then the developers would have put up with the API related shortcomings and delivered the apps. Developers always go where the paying customers are.
Anyway, as far as I can tell, Windows RT is already dead. It will disappear and be replaced by an upcoming version of WP, which will replicate many of the features currently exclusive to WRT.
The modern UI is here to stay however. MS was right to somewhat forcibly expose users to the metro UI. Change never happens without some force. Like I said, MS just needed to keep the navigation and window arrangement paradigms separated... that mistake was far more consequential than anything MS could have screwed up with the APIs.
I don't know what W8 would have looked like if I had designed it without any of the knowledge we have today. The people who worked on it probably were thinking a bit too much about where they wanted to be... not enough about the current customer base and where they are. Considering the pressure they must have been under to catch up with the mobile revolution that was underway, that mistake isn't completely incomprehensible. Hindsight does make a lot of things look obvious, much of which probably wasn't at the time.
Unfortunately, Windows 8 has turned out to be counterproductive... at the worst possible time.
What's hilarious, in a sad way, is that WinRT is a better implementation of the RT concept than WinPRT!Anyway, as far as I can tell, Windows RT is already dead. It will disappear and be replaced by an upcoming version of WP, which will replicate many of the features currently exclusive to WRT.
Metro is dead on large screen devices (not phones). Also, the APIs played a large part in the Win8 disaster. I won't port my Win32 programs to WinRT because I would have to maintain two completely separate code bases, not to mention that it's basically impossible to produce a complex RT program. If they had simply extended Win32 with a simple scalable UI API and backported it to Win7, I would have happily converted my programs over to it. Why? Because I could have covered phones, tablets, laptops, desktops, and XBox with one code base. It would have been fantastic for both devs and users.The modern UI is here to stay however. MS was right to somewhat forcibly expose users to the metro UI. Change never happens without some force. Like I said, MS just needed to keep the navigation and window arrangement paradigms separated... that mistake was far more consequential than anything MS could have screwed up with the APIs.
Lack of time or resources is NOT an excuse for a company with 90,000+ employees. And maintaining backwards compatibility was always the number one concern in the Windows group. I don't know how many times I had to modify my Win95 code to maintain backwards compatibility (even to the point of zeroing specific locations on the stack to cover up uninitialized variables in third part programs!). They knew that completely breaking backwards compatibility was a disaster in the making. My guess is that the business side of MSFT got greedy and thought they could profit from the 30% cut of WinRT app sales.I don't know what W8 would have looked like if I had designed it without any of the knowledge we have today. The people who worked on it probably were thinking a bit too much about where they wanted to be... not enough about the current customer base and where they are. Considering the pressure they must have been under to catch up with the mobile revolution that was underway, that mistake isn't completely incomprehensible. Hindsight does make a lot of things look obvious, much of which probably wasn't at the time.
You're being too kind. Disaster is a better word. As I've said before, Win8/RT/Metro may end up killing the entire company. MSFT needs to fire everyone involved in the Metro/RT debacle. The CEO and Windows chief are already gone. Now they need to root out the PMs and SDEs who designed and implemented it.Unfortunately, Windows 8 has turned out to be counterproductive... at the worst possible time.
I don't have a problem with them charging a percentage of the sales prices ... but 30% is *way* too high (even the high volume 20% rate is too high). They're just copying AAPL and GOOG's stores. If small Win32 resellers can get by on 5-7% I don't see why MSFT can't. I'd support a 10% cut since MSFT handles the certifying, updating, etc.I do think the 30% cut is too large; especially for expensive products. There really should be a cap on how much MS makes from a sale. Maybe around $30. Right now, a company that makes $800 software isn't ever going to make an RT version; even if it wad as easy as hitting a magic "Convert" button.
The latest rumors from Thurrott and Foley say that WinRT is basically dead and that MSFT will grow WinPRT instead. If that turns out to be true then we'll see a "Revenge of the Desktop in Windows 9. What's interesting is how this somewhat parallels the Windows-vs-OS/2 debacle in the late 1980s/early 1990s. Win16 was in widespread usage but MSFT deemed it a "legacy" API. The OS/2 API was the new way and both MSFT and IBM poured resources into it for several years. Unfortunately, users had a death grip on Win16, Windows 3.0/3.1 exploded on the scene, and Win95 (with its highly Win16-compatible Win32 API) finally buried OS/2. Changing to a completely new and incompatible API didn't make sense back then and it doesn't make sense now.WinRT can still succeed, but I agree that they need to open up more APIs.