Bazaar and Eclipse

Alexander Belchenko bialix at ukr.net
Wed Aug 26 09:02:06 BST 2009


Ian Clatworthy пишет:
> Gary van der Merwe wrote:
>> On Tue, Aug 25, 2009 at 2:59 PM, Russel
> 
>> I didn't think the issue was about branding, rather reducing effort
>> required, by reducing duplication of feature. Where it make sense to
>> reimplement, e.g. to provide better integration, we should go ahead
>> and do that.
> 
> Precisely. It would be naive to underestimate the massive amount of
> engineering that has gone into QBzr's UI design and internal implementation.
> 
> What concerns me about starting from the "let's do everything native"
> point is that it can quickly become a huge amount of work. For
> developers working on stuff in their spare time, that can translate into
> a project that doesn't get completed (vs end user expectations), doesn't
> get maintained to a high level of quality, etc.
> 
> In comparison, the "reuse QBzr" policy can lead to very good results in
> next to no time. Explorer is an example of that IMO.

Here is some numbers from QBzr page on Ohloh.net 
(https://www.ohloh.net/p/qbzr):

Codebase  	 19,158 lines
Effort (est.) 	4 Person Years

(This estimates how much it would cost to hire a team to write this 
project from scratch). Of course YMMV.






More information about the bazaar mailing list