Thanks so much for the advice fellas.  That's a really thorough break
down and I appreciate it a lot.  I'm going to think it over and talk
to everyone involved about it.    If there is any chance that we could
go with pylons or python, where's a good place to find open source
developers that want to work with a non-profit team?  I know a lot of
people like contributing to things in the public interest, should I go
to the Software in the Public Interest?  And they'd work with the
community?  Or do I start something like a window for developers to
interact in a repository like git or some other ticketing, tagging,
system?

It's just new territory for non-profits to work with the community so
it's difficult to know how to get a development community going of
happy coders. :)  I can design shirts, posters, and merch like that
(all related to airships) that can be made for contributors, kinda
like a gift bag of airship stuff.  I dunno, do people like steampunk?
It's all a bunch of cool looking steampunk airship merch. :)  Very art
nouveau and Maxfield Parish stuff, fantasy art supplied by Tom Kidd.
It's going to be a fun project so I'm excited to bring it to the
community as I've had my head in new media and programming so I
subscribe to a lot of threads.

If anyone is interested you can see my funny video on youtube at
airshipleague.com.  :)  And of course contact me at
[EMAIL PROTECTED]

Thanks and all the best,

Paul

On Fri, Jun 20, 2008 at 8:06 PM, Jonathan Vanasco <[EMAIL PROTECTED]> wrote:
>
> The differences in speed on webapps are usually entirely due to
> blocking at the database level.  I think a good comparison would be
> someone driving a 40yr old cadillac and a new sports car in a 5mph
> school zone lined with cop cars-- it doesn't matter what's under the
> hood, you're going 5mph.
>
> Pylons and RoR are very similar, and also very not.  Pylons is very
> 'extensible' and allows for more interaction/control of the
> developer.  RoR has a lot of 'magic', which translates to things
> needing to be done in certain ways.  Rails apps are often slow -- not
> because of Ruby, but because of Rails.  I think Pylons might be a bit
> more similar to Merb.
>
> In any event , my suggestion is this:
>
> - if your lead guy is a Rails programmer, find a new lead guy
>
> - if your lead guy is a Ruby programmer, and he thinks that the app
> makes sense in Rails or Merb - stick to them and avoid the pitfalls of
> learning new stuff.
>
> - in all other situations, Pylons or Django might just be a great
> fit!  maybe they want to try something new, or they know that its
> going to be a PITA to get rails to do what you want.
> >
>

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"pylons-discuss" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/pylons-discuss?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to