> Helmar Rudolph <news@xxxxxxxxxxxxxx> wrote: > > * Consequently, to only _START_ coding R2 after an R1 release is > > stupid and short-sighted, because already being about 7 years > > behind, you don't really have a chance of ever catching up. I completely disagree. The Haiku developers only have a very limited amount of time to work on the project. Unlike other big OSS projects (Linux kernel, Gnome) they have no big companies backing them up, employing them to work on Haiku. By opening up coding for R2, while R1 is still in the making, you're spreading out that limited amount of time over more things to do. Instead of developer Xyz working only on parts A, B, and C, you're giving him parts D, E and F without giving him more time. While this in the end may give more functionality *overall*, the *individual parts* will be of lesser qualiy, and much more buggy. Secondly, one of the most important things in a project is to have a goal towards one can work. A clear goal keeps a team focused. Imagine an athlete who has to run a certain distance, but has no idea what that distance is, while all his competitors do know the distance. Do you think he will win? By opening up development on R2, you're making the goal too fuzzy, which leads to less focus and therefor less results. Thom Holwerda --- Managing editor at http://www.osnews.com, exploring the future of computing --- Read my blog: http://thom-holwerda.blogspot.com