Re: my $.02 - ignore at will

> > I can't see how v1.1 would install as easily as 1.0 - you're
> > going ot have to setup postgres, and then run the cdbadmin
> > utility (or whatever) to get the tables created.

This should be very easy to script, given the proper db design.

> >
> > Yep, its added complexity. Yep, it'll get worse with the proposed
> > apache/mod_python engine that I hope will be the focus of 1.3.
> > The question that remains unanswered for everyone that is a
> > Current user is, is the added complexity worth the additional
> > features and scalability that the complexity will provide.
> >
> > Anyone?

Current's audience is system administrators.  I personally don't see 
setting this type of thing up as too much of a burden.  Admittedly, I 
haven't worked with Postgres, but I've worked with tons of other 
databases, so I'm not overly stressed about setting that up.  
Apache/mod_python might take a little more work, but it's pretty much 
worth it when you consider that not only does this make Current 
scalable, it makes it INCREDIBLY scalable.  The change is dramatic, 
the cost, in terms of complexity, is not.

Another way of looking at it:  I didn't choose Current because I like 
the way it 'currently' works.  I got involved mainly due to the 
Roadmap and because the developers have done some good work so far.  
If I found Current in a state of not being maintained, I would have 
probably moved on.  

'Don't ask is the benefit worth the complexity, ask if the project 
will still generate interest without the benefit' :)


-- 

Brian K. Jones
System Administrator
Dept. of Computer Science, Princeton University
[email protected]
Voice: (609) 258-6080