Slashdot videos: Now with more Slashdot!
We've improved Slashdot's video section; now you can view our video interviews, product close-ups and site visits with all the usual Slashdot options to comment, share, etc. No more walled garden! It's a work in progress -- we hope you'll check it out (Learn more about the recent updates).
If you have to subsidize it, then it ain't culture; it's history.
Don't bring up the US car industry her. That's mean.
Doesn't matter. Just updating my image of Apple-users.
I think laptops will be next. Not only MagSafe -> MagSafe 2, but all laptops have too many different connectors.
Link to Original Source
I have to say I would welcome mini-computers in the range 15 - 30W. For notebooks this Tegra 4 would be interesting.
The main reason the Tegra 4 is in no tablet/phone, is because Tegra 3 real performance and power usage was worse than advertised/marketed, and therefore the tablet/phone makers did not trust Tegra 4 would be a good bet. Another (smaller) reason was that NVIDIA is quite pushing their own agenda and brand, whereas other vendors do not meddle with their customer's business so much. Unluckily they did not learn from their experience and suggest in their latest video (the face-demo) that Tegra 5 uses 2 to 3 Watts when under full load - truth is that the load was not given. NVIDIA knows a little too much about marketing...
There are several languages that are written on top of OpenCL - that is the whole idea of this API. But if your read the article, it seems this guy was the actual inventor of the wheel.
Same response happened when some guy made Rootbeer and let some marketeer write an alike article. It was suggested that you could just run existing Java-code on the GPU, but that was not true at all - you had to rewrite the code to the rootbeer-API. This Harlan-project is comparable: just beta-software that has not run into the real limits of GPU-computing - but still making big promises that in contrary to their peers they actually will fix the problem.
I'm not saying it can be in the future, but just that this article is a marketing-piece with several promises on future advancements.
Nvidia is not including OpenCL samples in the latest CUDA SDK, focusing more on CUDA instead. As a Khronos member with an excellent record in implementing and promoting standards like OpenGL, this is a surprising and unacceptable behavior from Nvidia.
We, OpenCL developers, humbly request that OpenCL samples again be included in the SDK. Industry standards like OpenCL help in building up a bigger market for GPU computing, and will be beneficial to Nvidia in the long term.
In a presentation for a small group the unofficial statement was that they want to sell chips *now*, and not wait for a standard to mature: "For NVIDIA OpenCL is not the answer". The remark that OpenCL can be extended to support these needs, was answered with that you don't want unportable code. Funny is that you can use #IFDEF in such cases, but not if CUDA-code needs to be mixed with OpenCL.
This is just a matter of increasing their profits, while making it hard for coders who want to make performance-code for all modern hardware."
Link to Original Source