News for hackers. Stuff that matters.
Re:Angry Birds maker apologizes for Android fragmentation is... by jrockway on Friday November 19, 2010 @07:51PM (#1923441)
Incidentally, the web has failed because there are 5 different major browsers, and personal computers have failed, because there is an infinite combination of available hardware.

How could anyone have tested on all those? How could anyone have ever developed a working web application? How could anyone have ever developed a working Windows application?

The non-sarcastic answer: most of the time, the differences are irrelevant. The rest of the time, you need to build an abstraction, and then the second case becomes the first! Forever!

(Android is open-source. If you need a function that only Android 2.2 has, backport it to 1.6! If you need an abstraction layer for dealing with 24-bit or 16-bit screens, write one and share it with the world! Android is open, and you have to exploit that fact to be successful. You can't go off into your own little Universe where there is one person with one phone running one app at a time. That may be the iOS strategy, but it's not what works for Android.)

Re:Angry Birds maker apologizes for Android fragmentation is... by fletchowns on Friday November 19, 2010 @07:57PM (#1923451)
The non-sarcastic answer: most of the time, the differences are irrelevant.

Clearly you have not had the wonderful experience of trying to get something working in IE the way it works in all the other browsers!

Re:Angry Birds maker apologizes for Android fragmentation is... by qeorge on Friday November 19, 2010 @08:24PM (#1923523)
He's still correct. Even with IE, you just learn how to deal with it and you move on with your life.
Re:Angry Birds maker apologizes for Android fragmentation is... by fletchowns on Friday November 19, 2010 @08:40PM (#1923554)
Tell that to the people that have wasted thousands upon thousands of man-hours because of IE. Surely if the history of IE had been written differently the web would probably be a few years ahead of where we are at right now.
Re:Angry Birds maker apologizes for Android fragmentation is... by mishmash on Friday November 19, 2010 @08:41PM (#1923561)
And for most, those hours were passed on to clients, so there's probably some meta-comment about impact to the economy that IE has had.
Re:Angry Birds maker apologizes for Android fragmentation is... by snowmaker on Friday November 19, 2010 @10:20PM (#1923742)
No, that is the "Broken Window" fallacy. A common fallacy in economics: http://freedomkeys.com/window.htm
Re:Angry Birds maker apologizes for Android fragmentation is... by tl on Saturday November 20, 2010 @07:44AM (#1924406)
It's only a broken window fallacy if the comment was implying that the impact was positive.
Re:Angry Birds maker apologizes for Android fragmentation is... by mishmash on Friday November 19, 2010 @08:10PM (#1923480)
> If you need a function that only Android 2.2 has, backport it to 1.6!

And this solves the problems of users not having it how?

Re:Angry Birds maker apologizes for Android fragmentation is... by fletchowns on Friday November 19, 2010 @08:21PM (#1923510)
Well obviously you just need to backport it to 1.6, update all the custom user interfaces that each of the device makers have made, hack into several different OTA update systems, and force an update for millions of devices. Piece of cake right?
Re:Angry Birds maker apologizes for Android fragmentation is... by GHFigs on Friday November 19, 2010 @08:22PM (#1923514)
You could do it in a weekend.
Re:Angry Birds maker apologizes for Android fragmentation is... by mishmash on Friday November 19, 2010 @08:25PM (#1923526)
the definition of open: "mkdir android ; cd android ; repo init -u git://android.git.kernel.org/platform/manifest.git ; repo sync ; make"

That should handle it.

Re:Angry Birds maker apologizes for Android fragmentation is... by nym on Friday November 19, 2010 @10:19PM (#1923738)
I could be incorrect, but I think he means implement the feature on top of 1.6, not the system itself.

The web example would be getElementsByClassName:

  function getElementsByClassName(node,classname) {
  	if (node.getElementsByClassName)
		return node.getElementsByClassName(classname);
	else {
		// your custom function
	}
  }
(example from quirksmode.org)
Re:Angry Birds maker apologizes for Android fragmentation is... by jrockway on Friday November 19, 2010 @09:46PM (#1923673)
You ship it with your app. When the users get your app, they get your abstraction layer.
Re:Angry Birds maker apologizes for Android fragmentation is... by mahmud on Friday November 19, 2010 @10:12PM (#1923719)
Thank you. The sensible answer of an engineer.

Compare this with the "lol" sub-thread of mockery, sibling to this. Online technical communities die when the incompetent substitute jokes for thought, in their haste to say something.

Re:Angry Birds maker apologizes for Android fragmentation is... by mishmash on Friday November 19, 2010 @11:10PM (#1923821)
I'm sorry but he said to "backport it to 1.6" which would mean taking code from a more advanced version and making it work on an older codebase. This would involve updates to the 1.6 release or forking, which is what the other two "lol" comments in the thread are making fun of. If he would have said "re-implement it in your own app" I wouldn't have asked the question, and regardless, there's no need for the personal insults.

A small part of ever community dies any time some random fanboy resorts to ad hominems.

:)

Re:Angry Birds maker apologizes for Android fragmentation is... by mahmud on Friday November 19, 2010 @11:58PM (#1923890)
I'm sorry but he said to "backport it to 1.6" which would mean taking code from a more advanced version and making it work on an older codebase.

Out of a few possible meanings, you chose the most baroque.

When writing portable code, you have a few approaches:

1) Target least-common denominator, and enable advanced features on richer targets ("Graceful Degradation").

2) Target one platform/version maximally, and bundle your own abstraction layer for incompatible targets (Cygwin.)

3) Create your entire application in an environment created solely from a few, universally available primitives (a la Java Swing) or create your own ultra-portable runtime (java itself, Flash.)

4) Co-bundle a bunch of versions of the app for disparate platforms into one container format (Mac fat-binaries) -- this is the ugliest form of portability, almost analogous to ad-hoc polymorphism.

5) There are also self-improving systems that boot off simple stub code, and load more functionality from remote hosts, possibly compiling themselves on the new host, possibly using partial-evaluation and specialization, etc.

As a programmer, your first instinct for making a piece of code portable should be along these lines. The idea of patching the world to accommodate your needs should never cross your mind.

I would have loved to make this discussion about Android portability strategies. I mean, if MS-DOS 5 and 6.22 were binary compatible for device drivers, even though they used completely different device "models", then I am sure we can bump heads and exchange tricks for Android, iOS and other mobile OSes that are about to shatter like champagne glass on tarmac.

Re:Angry Birds maker apologizes for Android fragmentation is... by mahmud on Friday November 19, 2010 @10:19PM (#1923740)
It's customary in software engineering to "wrap" and augment system infrastructure with your own portability layer. You can see this everywhere; the Linux kernel, for example, bundles its own little library for emulating floating-point processing, for x86 systems that don't have x87 (very rare!).

The whole point of the C compiler -D argument is to allow you to enable features at compile time. GNU Autotools exploit this by inspecting the host environment and enumerating the available "features", allowing the build scripts to selectively compile your portability layers when a feature is missing.

With Android, you can use runtime reflection to instantiate the right objects, based on system parameters. I.e. your compiled APK can behave differently on two systems, say, by enabling extra functionality on older OS versions.