The fiber optic cables will offer same bandwidth as the current copper solution. They only lower the latency over longer distance and kick off substantially less EM interference. They are no faster. Just longer. That's it.
Intel already said it will allow for increased speeds when the controller supports it.
I wouldn't bet on the upcoming fiber cables to work either. Note that TB puts electronics in the cables ( transcievers on both ends). In order to shave costs it would not be surprising if that modules in the upcoming units were fixed to current bandwidth/latency requirements. It isn't just fiber (or copper) you are buying it is electronics which can be as fixed as the core controller chip is.
I'm pretty sure the transceiver is passive, so it shouldn't be a huge issue.
Regardless, Intel has mentioned future implementations will be fully optical, eliminating the transceiver entirely.
And Linux is a step up?? Folks who fear change tend to fear all changes. Their excuses just get more lame when they get into situations where they discover they never had as much control as they thought they did.
Linux is actually usable for pros.
This really isn't about "cell phonification" or "pro commitment". It is mainly about "XXXX won't do things my way, so I will move to a new sandbox". It is rather a stretch to label that "pro" behavior. I see much more of that with 4th graders than pros.
This isn't "new way" vs. "old way." This is "Microsoft only lets you use a full screen view to open a new program." If Apple started shipping Macs with iOS, would you say that's "unusable for pros" or "just people not wanting to do things the new way"?
What is going to happen is the noisy, "fear of change" folks will yelp for a while until other folks go out and encode, document, and teach new workflows/methodologies. Most of them will move on to newer things over time at their own pace. The intransigent will hunker down in their cave with tech stack that is stuck in time and eventually get left behind.
Again, writing an ass backwards interface and calling it "new", and then saying that people who don't like it are "fearing change" and should suck it up isn't acceptable.
If it's not usable it's not usable. Even Windows veterans are livid.
1. Microsoft has no future Rosetta retirement problem because they aren't inserting a work-around. Besides, a x86/ARM virtual translator would just soak up more battery. ARM isn't a powerful as x86 and making it emulate an x86 will only make it slower. Nor is Microsoft abandoning the x86 platform.
I wasn't talking about translating existing apps. You cannot create a brand new ARM app using the classic Windows interface. Even if Adobe wanted to port Premiere to ARM they simply can't recompile it. You
have to port to WinRT which leads me to...
2. They designed a new API for multiplatform apps WinRT. That's what people can use. Win32 is still there for those who don't want to do multiplatform apps.
WinRT is crap for pro apps. Unusable. It would be like Apple slapping an iOS interface with iOS 2.0 APIs on the Mac and telling people to recode their pro apps in that.
Full screen only pro apps? Please. A system that can't have a Photoshop window and a Premiere window open at the same time is not a pro system.
iPhone shipped for over a year with no "native apps". It did just fine.
I'm not sure what the point is. How many pro apps did the iPhone have during that year? (How many pro apps does it have now, for that matter?)
We're talking about pros here.
I really don't think most software vendors are going to be interested in shipping two versions of cross compiled Win32 binary and keeping up with all the mismatched cross platform issues as much as Microsoft will for the first couple of years. They never were all that interested back when NT ran on more than x86 before. Not sure why folks expect that to change.
Great. So everyone will be forced to port to the crappy WinRT layer. Great news for Pros!
Pros don't need these crazy "window" things. And they definitely don't need more than one app at a time.
Microsoft is taking a gamble with WinRT. But they aren't letting go of their Win32 empire either. Depending upon how popular the more mobile apps become they will follow that trend. But if it falls short they haven't kill off goose that lays the golden eggs.
You just got done telling me everyone will have to port to WinRT. So you're telling me... people are going to drop Win32, port to WinRT, and if that doesn't work out port right back to Win32?
Right. WinRT and Win32 are extremely different. It's not an easy port job.
It is completely not a bizarre workaround for those who have been using Windows 7. It is not a new feature. Nor is it an unpopular feature. I suppose those who have snored on top of XP for the last decade might have to break down and learn something new, but this really about learning Windows 7 features, not 8.
First, it doesn't do anything to fix bigger complaints like WinRT only running one app at a time with no Windows (which is the name of the system to begin with.)
Second, the very need for such a workaround shows that it's not ready for Pros. Remember, we're talking about Pros here, not Joe six pack at home.
Basically you can use the task bar like the OS X dock if you wish. For those who have 4-6 programs that they spend their entire day inside of .... it works just as effectively as the dock.
....4-6 programs?
Looking at my dock right now, I have way more than 4-6 programs pinned and open on it.
But again, the very need for this says a lot about Windows 8.
Look, obviously we're in a Mac forum, and we're here because we like the Mac. But go to a Windows fanboy Pro forum. That they're also rejecting Windows 8 is very telling.