Some pundits are calling on Samsung to fork Android. The move, in theory, would allow the Samsung Galaxy smart phone team to better innovate ahead of the potential Apple iPhone 5 launch in late 2012 or early 2013. Meanwhile, Amazon has already forked Android for its own Kindle tablet -- and we've all seen how wildly popular Kindles have become.
Unix All Over Again (Please Say No)But do forks mean incompatible versions of Android will emerge? Generally speaking, there's no cause for panic here folks.
Yes, we all remember the days of Unix -- where multiple variants emerged and big software vendors (i.e., Oracle) had to adjust their applications to run on each Unix variant (IBM AIX, Sun Solaris, HP-UX and the list goes on).
Software Forks ExplainedApply that example to Android, and will we soon wake up in a world where App developers have to re-write their code a bit to remain compatible across Amazon, Samsung and other Android devices?
The VAR Guy doubts it. In the case of Android, life looks pretty darn good for App developers. In the Oracle Java vs. Google Android legal feud, a jury decision issued today seems to ensure Android App developers won't need to rewrite their apps anytime soon.
In terms of the fork discussion... There are good forks, bad forks, successful forks and doomed forks. Open Source Expert David A. Wheeler points to four possible outcomes of a fork:
- The death of the fork (example: libc/glibc). This is by far the most common outcome; indeed, many forks never receive enough support to “die”.
- A re-merging of the fork (example: gcc/egcs); this is where the projects rejoin each other (though one or the other may be the dominant source of the combined effort).
- The death of the original (example: XFree86/X.org).
- Successful branching -- both succeed, typically catering to different communities (examples: GNU emacs / xemacs, OpenBSD).