Don't disagree with you overall, but I do have one nitpicl. There is nothing proprietary about the Boost license. Boost license is quite similar to MIT license.
About the N9, there is almost no relationship between Meego+Maemo hybrid on N9 and Tizen, except for use of the Linux kernel, despite some claims otherwise. APIs and most of the libraries appear to be very different. For example, Qt was the primary native API the N9 but is not supported in the official SDK for Tizen. Tizen is instead supporting Bada's native APIs.
Further, the critically acclaimed UI on the N9 was a proprietary solution developed by Nokia and Tizen has a different user interface.
The submitted title is somewhat non-sensical. Google Now smartphone makes it sound like there is a company/team called Google Now building a smartphone.
Which BLAS though? The reference BLAS implementation? That will have terrible performance. Would be interested to see if something better like ATLAS or OpenBLAS can be compiled for it. Recent versions of ATLAS do work on ARM Linux, so wondering if those can be easily ported to Android.
I was using galaxy s2x. A variant of s2 with a 4.5 inch screen. That was hard to use single handed. This is my first blackberry so no idea how it compares with previous blackberry handsets.
I got my Z10 yesterday and I can confirm that the phone (and all the gestures) are completely usable with just one hand.
The phone size was selected pretty intelligently. I don't think the UI design would have worked with a bigger phone.
Qt Quick has many advantages over traditional Qt widgets:
1. It provides a simple JSON-like declarative syntax for defining UI layouts, and is quite easy to write new layouts for different use cases (desktop, tablet, netbook etc)
2. Very easy to do animations
3. Qt Quick is fully OpenGL accelerated in Qt 5 and beyond. While this KDE release is not using Qt 5, it provides a good transition path for the future.
Hi. Author here. Your name is quite famous in the GPGPU community, and it is great to hear that you now work on RSC. My experience does not compare to yours and I do hope my post is seen in a positive light. Would love to discuss the issues in depth sometime.
Anyway if you were to ignore everything in the post except one item, that would be to please fix gather/scatter in RSC. A parallel computing API without proper gather/scatter is simply not very useful, irrespective of whether it is on desktop or mobile.
I will keep following RSC and look forward to the developments you are hinting at.
Well it is about to be available in about 2 months. From Intel: "The Intel Xeon Phi coprocessor 5110P is shipping today with general availability on Jan. 28 with recommended customer price of $2,649."