5 ms·
The last couple Google I/O events have been disappointing because it takes an above-average amount of effort to get any of the neat things shown off (even six m
by 27182818284 12y ago
The last couple Google I/O events have been disappointing because it takes an above-average amount of effort to get any of the neat things shown off (even six months or a year later). The most common example probably being that I don't know a single person running Android L. (Past examples might include Google Glass, and their Flagship phone, which someone I personally know was just recently able to order despite wanting to buy it since its announcement) Even taking into account that it was released after the announcement (November 2014, right?) It still seems awkwardly long. This isn't anecdotal either as can be seen in their dashboard: https://developer.android.com/about/dashboards/index.html https://developer.android.com/about/dashboards/index.html
- tdkl 12y agoGoogle recently ships tech-demos, not products and I/O is one event where the hype starts.
- 27182818284 12y agoIt is hard even if you're a developer. I wanted to write Google Glass apps. No dice.
- pjmlp 12y agoYes, I was always looking for something like ART to be presented, given the sore state of Dalvik, and still cannot use it. Also I don't have any hope for them to say anything about Java 8, treating NDK users (like myself) as first class citizens or any other alternative language. Specially given their attitude at Android Developers Fireside last year. So iOS has Objective-C, C, C++, Swift, Objective-C++, JavaScript with access to the whole platform. IDE supports all languages. WP gives me Javascript, C++, C++/CX, C#, VB.NET, F# with access to the whole platform. IDE supports all languages. With Android, Java 6, partial Java 7, limited C and C++ with exposure to some Android and POSIX APIs. Studio only supports Java, even Eclipse NDK is kind of broken. No support for Renderscript or GL shaders.