Linked by Kostis Kapelonis on Sat 14th May 2011 15:43 UTC
General Development Application stores are growing everywhere like mushrooms. While users have initially embraced application stores because of the ease they offer with application installation, developers have several complaints. Division of profits from paid application and ineffectiveness of the screening process are among the major issues. Are application stores the best distribution channel possible? Can they satisfy both developers and users?
Permalink for comment 473095
To read all comments associated with this story, please click here.
WorknMan
Member since:
2005-11-13

Repositories are a defining and competitive attribute of the distribution. Customer service, product quality control, available software.. all there.


IMHO, that's a pretty bad way to differentiate distros, and a pretty bad reason to have so many different ones. If we're going to play this game, I'd rather see 3 different distros with very solid repositories, rather than 900. Or better yet, how about 1 distro with 1 repository? One of the points made in the article is that having a single app store exposes a single point of failure, but if each distro has its own repository, how is this any different? Sure, maybe you can edit your apt.sources file and add in a couple more, but do you really want to explain to my mom how to do that?

Versions of programs are not the latest and greatest (Debian Stable), consider a distribution that provides more bleeding edge with resulting less stability (Ubuntu forked from Debian Testing/Unstable branches).


Yeah, good luck explaining that to the average iPhone owners. This kind of bullshit is EXACTLY why Linux on the desktop never gained any significant marketshare.

If a device is branded as an "Android device" it should be able to easily take Google's core distribution firmware through a standard flashing process; let manufacturers provide a small separate blob image for device specific drivers if they must. Really, they should be providing the drivers back to the core distribution's kernel but the add-on blob is an acceptable compromise for the moment.


Agreed 100%.

Vendor's who must fork Android into there own one-off version, as has been sadly popular, should indeed be providing there own repositories. They fork the distribution away from the parent distro, they accept the responsibility of managing there own repositories and loss of use of the "Android" branding.


That is the way it works now, in fact. If you deviate too far from 'the standard', you lose the ability to call your product Android, and you lose access to the Android marketplace. Of course, some people would argue that it doesn't go far enough, and I'm one of those people.

Reply Parent Score: 2