Comment #13 on issue 3706 by renggli: In OB: Text in comment pane of Browser uses syntax highlighting
http://code.google.com/p/pharo/issues/detail?id=3706
Yes but if the maintainer of OB does not want to maintain the 1.2 branch when we are doing 1.2 alpha then what do we do? ( I never understood your position at this level).
The thing is that I cannot (and I never could) maintain Seaside, Magritte, Pier, PetitParser and Helvetia on a (shaky) not yet released version of Pharo.
We cannot play the platform evolution (vs the core) if maintainers of the packages do not play the game.
With Seaside, Magritte and Pharo we do not want to play such games (to be able to deliver the best possible first experience). With OB and RB I don't have the time to maintain two versions (I thought that people jumped in here for Pharo 1.2, but frankly the existing code is very broken).
It works really well with Moose.
I do not agree. From what I know, many Moose users stick with old versions of Moose (and Pharo), because the new versions do not work for them.
