> To me that difference isn't in quality, it is in API 
> stability.

 I agree. The difference between an alpha and a 1.0 release is that when a
version number is cut, there is an implication of API stability and
maintenance of that API at least until the next major revision. For example,
even while Sun was developing JDK 1.1, they were making bug fixes to 1.0.
They were maintaining that interface. Even then they maintained that
interface in future releases.

 When it comes to an alpha, you don't even have a commitment to your model.
If I spend time now learning or having someone learn your model, it may
become extinct before the 1.0 release. I don't care to risk wasting that
time as we also have things to do.

> We are about
> to make a pretty major change to the API

A good example of why building on the current code would be costly.

> Regardless, even if I decide to roll a 1.0 today, it is just 
> as easy to roll
> a 2.0 tomorrow that totally changes everything yet again.

And if you continue to do so, I will lose faith in your direction of the
project; consider it too unstable and unmanaged to be worth the cost. I'm
not just talking the cost of refactoring, but the cost of research and
re-education.

> In other words, that "excuse" doesn't really hold up for me 

But it does hold up for me.

> 200+ other people don't have a problem using it.
> Why should you? :-)

Because >I< don't trust you :-) I don't know these 200+ people using it and
what >their< needs are. I have evaluated Turbine's status and do not feel it
is ready our core framework (that is the framework that all of our new
applications will be started on, and some older applications will be
refactored to). When I presented the status of your project to our CTO, he
reaffirmed my conclusions. And those conclusions are based on my experience
with alpha APIs.

James :-)


--
----------------------------------------------------------
To subscribe:        [EMAIL PROTECTED]
To unsubscribe:      [EMAIL PROTECTED]
Archives and Other:  <http://java.apache.org/main/mail.html>
Problems?:           [EMAIL PROTECTED]

Reply via email to