Reconsidering Releasing DataCruxWeb

I've decided against releasing DataCruxWeb for now. I think something this big would generate a lot of email and I'd need to donate a ton of time to help people figure things out. I'm also not sure I want to add to the noise by releasing another persistence engine.

I've been taking a closer look at Rails, and it does a lot of stuff right. There are some things I'm not entirely sold on (particularly on the templating side of things), but it's good enough that it can't be dismissed out of hand.

One of the most critical points in this decision is that FastCGI seems to be in better shape than I thought. This makes Rails more practical than it looked at first glance, meaning there's less of a need for a PHP-based persistence engine. Depsite what I've said about the positive side of PHP, it lacks a lot of infrastructure. I can continue writing that layer myself, but it takes time -- time that could be better spent on applications.

To some degree, I'm trying to avoid a repeat of the DataCrux/Core Data situation. That is, I don't want to donate time to a project, writing code for problems if the solutions have already been deployed. I also try to not let the fact that I created something stand in the way of considering an alternative. Of course, if the existing solution doesn't work the way I want it to, then it makes sense to write something new.

For now, I'm going to continue to evaluate Rails. If I find it doesn't really work the way I want, I'll re-initiate a launch of DataCruxWeb. However, if you feel strongly that DataCruxWeb should be released, email me at my first name at treehouseideas.com and make your case.
Design Element
Reconsidering Releasing DataCruxWeb
Posted Oct 3, 2005 — 5 comments below




 

David Allison — Oct 05, 05 416

That's really unfortunate to hear - I was looking forward to trying out DataCruxWeb on a new project in the next couple months.

Any chance you'll reconsider and just put it up under the BSD license on SourceForge or something?

-David

Scott Stevenson — Oct 05, 05 417 Scotty the Leopard

A few people have asked about this. I might just release it with a "unsupported" label and let people do what they will with it.

What I'm getting at is I'd like to better understand why people want this instead of Rails.

Jesper — Oct 06, 05 418

I wrote to you as well. Like I said, I want this instead of Rails because it's made for PHP and to fill a need (just like Rails and Django) and is not just a port of Rails (like Trax and Cake). Nothing's wrong with porting but it's an awful lot of work to make it "feel right" compared to writing a new framework and letting it evolve like you did.

I've been trying Rails out but Ruby the language makes me cringe. There's also the matter that PHP5 is probably (perhaps sadly) offered on more hosting services than Ruby.

Abhi Beckert — Oct 07, 05 423

I'm not in a position to use something that isn't PHP based, and since DataCrux comes from a cocoa developer I'm keen to see how well it would integrate with my semi-MVC style of writing web apps in PHP.

Whatever you decide to do, please don't kill it without making the source code public!

Elliot Anderson — Oct 08, 05 424

I would still be intrested in seeing DataCrux even if it is unfinished and unsupported.
Design Element

Comments Feed




 

Comments Temporarily Disabled

I had to temporarily disable comments due to spam. I'll re-enable them soon.





Copyright © Scott Stevenson 2004-2015