What do you mean "finally"? Ebay, Amazon etc have a plethora of ARM-based mini-PCs with 4GB under $99. Well under. Typically sold with Android as set-top boxes, they can be used for web browsing, office PCs, etc. Some will work with Linux, but remember there is no Linux/ARM version of full Chrome.
I am one of the first owners of the of Jetson TK1 board. The benefits of this board are a) it runs Ubuntu out of the box, b) it has more powerful GPU, and c) it is supported and well documented by Nvidia. There is a native build of Chrome on ARM - see the Acer Chromebook 13, which also uses the TK1 SoC - and it runs quite well. However, I never did get that build for my Jetson as Google limited its distribution. There may be a way around that these days. I did however get Chromium to work like Chrome through some additional software. The browser ran well on top of Ubuntu with 2GB of RAM. It would however run out of memory and crash if one loaded multiple tabs with heavy content. Double the memory should some that issue.
On the Mac you do not even have to do that step. Or, for that matter, know about the existence of VLC. That is the entire point. Also, QT is better than VLC, and the Mac also comes with a video EDITOR.
Pick your poison. I'd rather sudo apt-get install VLC then have to fuck around with the Apple land-mine-ridden quasi-linux-dev environment.
How about nVidia's Jetson TK1 board? It has a great 192-core Kepler GPU, a nice quad-core ARM CPU, on-board gigabit ethernet, all the ports you're likely to need and comes pre-installed with Ubuntu Linux.
I have one, and it is a great little Linux box for the most part. The x86 compatibility issue pops-up every once in a while, and 2GB RAM is a little tight, but after that it's all roses. Thanks to Raspberry Pie, ARM support for Linux is surprisingly complete, and the Tegra K1 graphics vastly outperformed the GPU on any Intel CPU that cost less than the entire JetsonTK1 board. Video cam, Google Hangouts, LibreOffice, Gimp, Inkscape, Java, Webstorm, etc. all work very nicely. My son uses it for his development computer, and it is attached to a 240GB SSD and a 32" 1920x1200 monitor. Libreoffice launches in 2s cold.
Remember how I said the future might make a fool of you? Seems Google thinks that desktop quaility gaming has come to mobile. And the demo certainly looks impressive. Probably not on QC chips in the near future, but certainly on the Nvidia K1 and Erista. Remember, both of these are (or will be) >= Intel HD4400 Graphics. That is more power than most people on Steam have.
The potential answers to your question are "yes" "of course" and "how stupid are you to even have to ask?"
There was no call for such a nasty response. I provided a nice post that I thought you might find useful, and you belittled my points like some arrogant prick. Does that brighten your day? Unfortunately, the future might just make a fool of you.
One would have to be pretty stupid to miss that ARM and x86 markets are converging. Servers are going ARM. x86 is going mobile.
One would have to be pretty stupid not to see that ISA does not dictate audience or sales strategies. Any current association is correlation, not causation. The montetization strategy is driven by the the target market. If ARM and x86 are converging to compete in the same markets
One would have to be pretty stupid not to see that Porting to ARM, while sometimes tedious, is not nearly as arduous as one might think:
One would have to be pretty stupid not to see that porting to Nvidia ARM with great hardware and excellent drivers might be less trouble than trying to get shitty AMD drivers to work with SteamOS. I wouldn't be surprised if folks over at Valve had the same thought, judging by their impression of AMD's drivers. (hint: they are Vendor "B"). Adding weight to this, I have it on good source that a "consumer" variant of the Jetson TK1 board should come to market "soon". Sounds awfully steambox-ish.
Let's not be stupid, ok? You might want to drop $192 and get up to speed on ARM yourself.
Fact is however, that when it comes to bang for a buck or just plain bang in one chip, there really are no alternatives for AMD. That's why console manufacturers went with it.
Depends on if they require x86. The Tegras are full SoCs, with the K1 beating i3 parts on a number of compute benchmarks. It also performs similar to HD4400 graphics, with OGL4.4 support and a power draw <10W (<3W for most uses, ~0.6W idle) @ 2.3GHz. It looks to compete well against the Mullins chip.
This of course would require more Steam games ported to ARM, which I admit is probably a serious PITA.
I suspect it will be one of the more powerful AMD APUs under the hood. It's about the only way today to have a significant graphical power without having a discrete card.
I think that is wishful thinking for someone who really is rooting for the Red team
At present, the consensus is that AMD GL drivers are severely deficient in performance, capability, and stability (see posting about GL vendors provided by Valve engineering manager). Now this company could work with AMD to greatly improve their GL drivers. Or they could simply use a Tegra K1 (or the subsequent Erista chip) and get everything they need with top-notch driver and Valve support. Given that Shield already runs Portal and Half-life 2, and that Valve and Nvidia have collaborated on the Steam Box, and that NVidia GL drivers are consistently better
I wrote: "Webkit probably remains OSS only because the KHTML foundation requires it."
You wrote: "That is bullshit and you know it."
No, I don't know that it is bullshit. Is it speculation? Of course, that is why I wrote the word probably.
Of course, if Apple had closed Webkit, they wouldn't have benefited from the enormous investment of Google to its development. So in the end, I guess they are thankful for the LGPL license.
You wrote: "If you don't support the right to fork [...] you don't support open source."
Yes Webkit was always a fork. But the KHTML devs were led to believe that there would be collaboration - and apparently there was up until Apple got what they wanted
You wrote: [...] and why they open source most Apple-originated projects.
How in the world do you come by that metric? Everywhere I look in Apple I see proprietary hardware, software, and services that are designed specifically for lock-in.
This is a formatted version of my previous comment.
Summary
Webkit is an excellent example of how Apple takes and does not give. Apple is within the law to behave as it does. Consumers can decide not to like it and refuse to buy their products. It's our call.
Background
I remember when KHTML was selected by Apple for the basis of Safari. KHTML had gotten so good that by 2005 I was Konqueror as my primary browser, with Firefox on standby for more troublesome sites. It's speed and integration to the desktop was compelling. The KDE folks were ecstatic about Apple's choice. "Yeah!, we can work with Apple to make KHTML even better" seemed to be the sentiment. The Apple engineering manager wrote a nice letter to the KDE folks to tell them what a bang-up job they did developing the code, and how it saved them perhaps two years of development time.
Shortly thereafter it became apparent that Apple had no interest in helping to improve KHTML - quite the contrary. They just converted KHTML to Webkit and never looked back. Patches to KHTML were received in nearly indecipherable tarballs. Communication became hostile and then non-existent. Webkit probably remains OSS only because the KHTML foundation requires it.
Apple seems to consistently like to take from a project and not give back to the fullest extent of the law. Their mantra seems to be "Great artist steal, then use the massive time savings to add and patent silly "non-essential" features, and then sue everyone on the planet for using something resembling said features." Example: With the estimated two years they saved using KHTML, the were able to get to market faster and add and patent "non-essential" features like bounce-back scrolling[1]. And then they sued other smart phone suppliers for use of that feature in their browser (Nokia, Sammy, etc). Bravo Apple!
OSS and proprietary software both have a place. OSS is successful for many products because companies have realized that for core services, it is less expensive and better for them to collaborate on standards-based solutions. Luckily, consumers also benefit. This is similar to how automotive manufacturers have standardized on placing the gas and brake pedals. Apple doesn't seem to like that game, instead preferring the oft-mentioned walled garden[2] approach. But they are happy to steal the benches from the city park to put on their garden path.
Footnotes
"We want to create puppets that pull their own strings." -- Ann Marion "Would this make them Marionettes?" -- Jeff Daiell