The reason I tend to prefer this sort of thing to many of the other templating solutions is that it uses native code instead of custom tokens, which are limiting. It does make for less readable code and muddies the distinction between presentation and implementation. I think it works well, though, for startups building applications in which the majority of people building it are developers. It's just a very quick and powerful way to get the thing doing what you want. The designers can then be free to do more blue-sky design work (without templating code) that can be backported into the project. That being said, it can be very helpful to have a backing object in which to hide the majority of the heavy lifting. Then you can just sprinkle a little code in the template for the final polish.
You may be interested to know that bittorrent.com runs on Myghty. It's definitely scalable.
- mike, interested to see links from ycombinator in his referrer logs
But this suite of tools (pylons + mako + others) seem more flexible.. thanks for the advice.
I think I'll still investigate rails, but I have reservations.
I'm wondering if people have strong opinions on higher level web packages. Here's the field as I see it:
- Java + GWT
- Python + Django
- Ruby on Rails
- PHP + raw javascript
- Flash (or Apollo?)
Since I'm a hacker, I don't really like hacking things other people have done already, so I'm leaning against the php route, but it seems to be the beaten path.
Opinions? Other options I haven't found yet?
My advice is to spend a week on each of them and decide for yourself. Even if you you don't like them, it'll be a good learning experience. I'm tackling Django next...
Whatever package I choose should:
1) be cross-browser with minimal special code.
2) abstract out most database operations when possible.
3) involve writing very little html.
4) be well documented and have some history of real use by users other than the creators.
I'm not afraid to code through any of these issues, however, if someone else has done the work, why should I?
ObUseful: The separation between view, model, and controller is a driver of simplicity. Check out: http://stringtemplate.org/
+ Database ORM: DBIx::Class http://search.cpan.org/dist/DBIx-Class/
+ HTML Templating: TT2 (Template Toolkit) http://www.template-toolkit.org/
TurboGears http://www.turbogears.org SQLAlchemy http://www.sqlalchemy.org/ Elixir http://elixir.ematia.de/ Genshi http://genshi.edgewall.org/