Re: know about Storm?

On 08:06 am, [email protected] wrote:
>I just head about this new Python ORM from Canonical via Slashdot... 
>it looks a lot like Axiom API-wise.
>https://storm.canonical.com/

Yep.  I would definitely recommend it for anyone looking for a more 
"traditional" ORM, one that doesn't make all of Axiom's wacky 
assumptions.  In fact, I've spoken with the lead developer on Storm and 
we definitely want to have them converge, and possibly share some code.

(Unfortunately their decision to license under the LGPL means that any 
potential sharing has to go Axiom->Storm rather than the other way 
around, which is unfortunate technically because Storm is a bit "lower 
level" and seems to work harder to avoid putting a burden on your code, 
but so it goes.)
>It seems you guys know about it though....
>http://divmod.org/trac/wiki/DivmodNevow/Storm

Uh... to be clear, that page was created by someone who doesn't work for 
Divmod or commit to any of the Divmod repositories.  I love Duncan and 
all, he's been a very supportive voice in the community, but I have no 
idea what he was thinking :).
>What kind of integration are you planning? (I haven't used Nevow yet, 
>but just interested...)

I can appreciate many of the advantages that Storm has over Axiom.  The 
author of Storm was at least lightly inspired by Axiom's design when he 
created it.  I know the entire team that has worked on Storm, and spoken 
with its author about the potential for collaboration.

So, the two projects have the potential to be friendly, but in order for 
anything to actually *happen*, some members of the community are going 
to have to step up (and be aware of the aforementioned licensing issue); 
nothing is currently planned.  I can say for sure that I don't have the 
spare time to do anything with Storm, and having spoken with Gustavo I'm 
pretty sure that he doesn't have time for Axiom either.  In fact I'm a 
little surprised that they managed to release it as open source as 
quickly as they did - congratulations, guys!

That's our spare time.  For our work time, there would be no direct, 
immediate benefit to either Canonical nor Divmod for this to happen, so 
it's unlikely to happen there either.  It certainly decreases our 
overall maintenance burden and makes things easier for both of us in the 
long haul, though, so I doubt that patches to either project making it 
more directly integrated with the other would be rejected out of hand.

Again, I have no idea what Duncan was proposing as integration between 
Nevow and Storm ;).
>Anyway, I'm still a big Axiom fan :) One nice thing about Storm  though 
>is it seems you don't need to subclass anything to use it  (Item in 
>Axiom).

The major feature of Storm is that you can use it with an *existing* 
relational database, and existing schema.  Axiom's dependence on both 
SQLite runs deep, but its dependence on managing the schema run almost 
to its core.

Axiom is still a viable project in its own right, though, as its tight 
integration with Twisted is a huge benefit to a very different kind of 
application (for example, the integrated scheduler would be tricky to 
pull off in something like Storm).

So, for right now, I will be happily recommending Storm to anyone who 
asks "why doesn't Axiom support Postgres?"  At least, until someone 
somehow manages to make it do that :).