| HN Mirror

This reply hit so very many of my buttons - it's either a brilliant trolling, or incredibly unfortunate. But either way, my (entirely too detailed) response:

> why is that comment either a) at all credible

First off - rather than address the content of the original commenter I quoted, the first thing you do is go after his credibility. An ad hominem attack, right off the bat?

I don't know the poster. I don't know you either - initially, you're both equally credible to him. But he at least talked the talk - all the things he said made complete sense in the context of someone working cross-device with GL. They dove-tail in a technical manner with the more abstract high-level picture being painted.

Could he be bullshitting? Of course. But the only folks who benefit from pseudo-anonymously posting bullshit are griefers and fanboys. And since the level of technical discussion exceeds what most griefers and fanboys are capable of, I'm giving him the benefit of the doubt.

Do I want to believe him? Hell no. But do I believe him? Yes.

> or b) informative

What? He EXPLICITLY STATES some of the very specific technical problems he's encountered. Problems that a 3rd party can verify for themselves to trivially determine the veracity of his statements. The issues he mentions, assuming they're real, are major technical hurdles for multi-device development. And now I know to look for them if-and-when I start hitting issues. Drivers and APIs lying are a huge deal. And, unfortunately, entirely too common when doing graphics work.

So I have to ask - what, exactly, is the criteria you're using to judge "informative"?

> The problem with this discussion -- it is ostensibly an iOS versus Android discussion

Like fuck it is. I generally try to keep a civil tongue, but that sort of platform apologism is an insult to every Android developer. Framing it as iOS vs Android debate? iOS is a red-herring. IF iOS DIDN'T EXIST, THIS PROBLEM DOESN'T GO AWAY - developers would still be hitting these pain points.

It looks like Android has a problem, and acknowledging it is the first step in correcting it. Pissy GL drivers exist - as anyone who touched a linux box in the Bad Old Days is probably entirely too aware.

> as if developers have the luxury of just developing for iOS and the market will follow (hint: ha! Android made most of its gains when there little to no apps for it. Apps like Netflix and others followed but didn't lead. Now you could fill your day trying out new games and apps)

WTH? How is this even related to the comment I quoted? But I'll bite - Battleheart's developer confirms that they has the luxury of just developing for iOS. And by making this cut, they're signalling they no longer care if the Android market follows him. Just like anyone can author a game in DirectX that just targets Windows can comfortably ignore OS X and still be profitable. It's sad, but a developer has to be pragmatic if they want the to survive long enough to release the next product.

And if you really want to be pedantic - the iPhone made all it's initial gain when there were no apps for it. Remember, on release the iPhone did not have a native market. Developers and users had to cajole Apple into it. But hey, now iPhone users can "fill [their] day trying out new games and apps". I'm not sure what the hell this has to do with anything, though.

> there are a lot of very, very strongly biased individuals and parties, and the discussion gets completely crowded out by what often ends up being bullshit (though it takes a lot of legwork and endless excluding to actually discern that). What I like to see are specifics, but they are shockingly hard to come by.

HOLY FUCK. This quote calls out BROKEN APIS YOU CAN EXPERIMENT WITH RIGHT NOW. The base discussion itself flows out of a developer expressing why he's leaving the platform, with specific reasons stated. There is NOTHING here that can't be verified. And I don't know where the fuck you get off characterizing a studio that's spending time and money desperately trying to support a platform to share their work with as many people as they can (which is why most indie game devs I know do this) as "strongly biased individuals and parties" against Android.

> In this case of the linked story the vendors used Unity 3D -- why they were even writing specific shaders (double shocking given that their top-down sprite graphics, if I am understanding their apps right, are the most bog standard shaders going) is a mystery.

And now you're attacking the developer's competence. :/ Let me twist your statement around - only an incompetent developer wouldn't use fragment shaders. They're a great way of providing compelling visual effects without incurring a substantial performance hit. By using more than just "bog standard shaders", the creators of Battleheart are demonstrating they're trying incredibly hard to create a satisfying experience for their end user - a step up from your cookie-cutter game developers.

Now, getting back to the actual topic - what are some short-term solutions to this problem? The only thing I can think of is a bunch of developers banding together and creating a "reference application" that thoroughly exercises the API on a device (sort of an android-esque Futuremark). And if a device fails to pass "certification", developers right-off supporting that hardware. It'd be great if a company with clout like Rovio pushed this, for example.

A longer term fix would be if Android started incorporating something akin to the Windows Experience Index. As the platform grows, I fully suspect Android will have to include something like this to help developers sanely handle the growing performance gap between devices.

Does anyone know if Google does any driver certification?

And a completely unrelated question - huggyface, may I ask who you are? You've got a karma that doesn't match your listed contributions (A 60-day-old account with 12 comments, no submissions, and over 420 karma), which has me terribly curious.