> Look like you are afraid of competitors on Android market :)This is getting grotesque.
Your argument that Windows is the most popular OS is totally off. Can you show some proof that Windows is popular among alpha geeks that are actually passionate about their OS? That Windows is widespread among the general population doesn't really matter. Here is a photo of the last rails conference in Germany (but you can find many of those photos from other developer conferences, maybe except on Minesweeper confs): http://www.flickr.com/photos/scoop/2577830065/sizes/o/ If there is an active Windows-only developer community, let them step up to the plate, but don't distract the Android developers - the Android Market needs some serious fixing ;-) and there is enough work left to improve the current development process. Regarding svn: This is a nice product, but the world keeps turning and the advent of DVCS changed the game. As you like what's popular: http://www.google.com/trends?q=git%2C+svn&ctab=0&geo=all&date=all&sort=0 And what would you do with SVN anyway? Do you plan to contribute code to the Android project? Have you done that before? Or do you just want to have convenient access to the source code? Then work on that. It is not rocket science to get the source from git and provide it as a tar ball. On Wed, May 6, 2009 at 1:15 PM, AlexK <[email protected]> wrote: > > > You asked technology questions, and received technology answers. > > Surprising?. > > Not. I'm surprising that exists so "narrowed" view of the problem. > > > Distributed version control is much better suited for a project which has > > the > > magnitude of Android, where a lot of different partners want to have > their > > own repositories with a crazy number of branches and custom > modifications. > > > > If you think that a single SVN server can handle that, you're mistaken. > If > > you > > think that this can be managed by having several SVN repositories (e.g. a > > public > > one and various 'internal' ones), you don't know the nightmare that > properly > > synchronizing them can be at times (e.g. repeated merge conflicts) > > Not exactly true. Any big enough vendor will work on internal > environment which much better controlled, tested and etc. > That means that any vendor will have a problem of creating own > repository copy on own servers. > > > Maybe, maybe not, but nothing says these must be "Windows-exclusive > > developers". > > Look like you are afraid of competitors on Android market :) Too many > innovative technologies developed on windows os. > And open source can be everywhere. > > > At the current moment Android development request for developers with > high experience, and they cost a lot, so initial cost of the Android > development is still high. Make it lower and many good things appears > there. > > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Android Discuss" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/android-discuss?hl=en -~----------~----~----~----~------~----~------~--~---
