On 3/10/14 22:13, Hilaire wrote:
I agree 100% with Thierry.
I wrote and complain about it months ago: we need consolidation in the
newly developed stuff we have.

This is what we are doing.
Look at spec we cleaned it.
Now we do not have 3 more years for TxText and Athens.
Keeping the old events is a door open for
    - more ctrl key does not work.....

So it may mean to slow down and
polishing. Because from my point of view, I don't understand where is
moving Pharo, but true it is moving.

Pharo is moving as
- more modularity (we are working on making the bootstrap part of the building of Pharo)
    based on conifguration of external elements

    - great infrastructure
            compiler
            text
            OS event + window
            more example
            cleaning menu

Stef


Hilaire


Le 03/10/2014 17:07, Thierry Goubier a écrit :
unsatisfying "now" situation. I'll carefully evaluate what new stuff is
integrated. New stuff I look to see if they are usable (libcgit
integration, TxText) and what I see is stuff that builds on unstable core
libs extensions (NativeBoost, Athens) on top of an already unstable version
(4.0), and I'm really not impressed by the software development process.

The end result is, when I see a bug, I'm already at least two versions
behind you guys... so there's nothing worth reporting. There is some
progress on the way things are being done (thanks Marcus for doing the
deprecation API backporting on 3.0) and not much on others (and I speak of
methodology, not of new features being added on).

If you have the feeling that I don't contribute the way I should or the way
you would like, step back and ask yourself if this is not my "unspoken" way
of me saying that I don't find a way to contribute, or that contributing
effectively is too costly.

And look! This is not a matter of resources, but maybe a matter of slowing
down a bit, so that the poor community members with limited resources like
me that are not full time on Pharo 4.0 development may catch up :) And
please, no more rejection of feedback, even negative. It just gives me the
feeling you are overstreched, and that Pharo has a problem setting its
goals.



Reply via email to