"Patrick Casey" <[EMAIL PROTECTED]> wrote... > I've actually bitten the bullet a couple of times on commercial apps and > done huge rewrites (usually between 2.x and 3.0 versions) and I've been > burned by my user base virtually every time. > [clip] > > Which isn't to say that you're necessarily going to make the same mistakes I > did on that particular app (failing to provide backward compatibility for > the APIs was a big one), or that Hivemind won't allow lots of cool new stuff > that'll make me jump for joy. Right now though I haven't yet heard of what > the Hivemind integration is going to do for me as an end user, so I have a > fear, based on my own experience, that it's going to be a "developer" > release.
True, but sometimes the code gets too messy and too complex to be able to add the features or change things in the ways the users want. So, in order for forward progress to be made, you have to take a moment to pause, clean things up, regroup, and then start moving forward at full force. That is I think what's happening with Tapestry 4.0. It does seem to be a developer-focused release, but I've looked at the 3.0x code, and this step seems necessary if you want to see accelerated progress on user-focused features. -Nathan --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
