Poaching the lead dev to work on your own fork is a hostile move, and in my book, it provides a reasonable excuse for the delays, since nobody was able to take his succession immediately.
The guys at Lucid also barely communicated for long periods of time, making collaboration impossible.
> Poaching the lead dev to work on your own fork is a hostile move
That's an argument one can use when asked to spend more time with kids.
> it provides a reasonable excuse for the delays, since nobody was able to take his succession immediately
Huh?!? Open Source model not working or what?
>> it provides a reasonable excuse for the delays, since nobody was able to take his succession immediately
> Huh?!? Open Source model not working or what?
I guess its only illusion and crazy lawyers who like to add anti-poaching clauses in employee contracts. If a company can't handle loosing their top engineers, clearly its the the proprietary model that is not working.
Funny, I had the opposite view. I guess your opinion of the personalities really does change everything.
Re:Bzr is dying; Emacs needs to move
by hamburglar on Thursday January 02, 2014 @03:26PM
(#7002032)
There is one (and only one) other possibility, which is that you and I both read the conversation with flawless objectivity, and that you are wrong. :D
I also read the argument about the redesign of the event system and was pretty flabbergasted. The argument seems to reduce to "lucid emacs decided to design a proper event datatype because having an event be entirely represented by a simple integer keycode both lost information and made it impossible to represent certain keystrokes" versus "but ints are simple and backward compatible!"