4 ms·
Looks like it's great for building the things the authors thought you might want to build. Just like every other "SuperMagic" framework, I suspect there's a lo
by jasonkester 16y ago
Looks like it's great for building the things the authors thought you might want to build.
Just like every other "SuperMagic" framework, I suspect there's a lot of pain to be had once you step just a little outside of what it expects you to do with it.
We've all re-written Django inside of Django at least once, and thus have been burned by this sort of thing before. Personally, I think I'll wait to see some big projects written by people other than the framework designers before I agree that this is indeed the "best" web framework.
- cmelbye 16y agoI don't know much about Lift, but I believe foursquare.com is using it.
- vdm 16y agoA framework's website needs a list of links to sites that are using it.
- realugglan 16y agoYou mean like this web framework's website has? http://www.liftweb.net/ http://www.liftweb.net/
- bad_user 16y agoI've been using Django for a lot of projects, but have recently converted to Rails 3 for a personal project. What I like about Rails is that plugins are mostly pieces of infrastructure, not ready-to-use mini-applications that are hard to customize. And Rack plugins (pieces of middleware, done in a standard/reusable way, contrary to Django's middleware) are just awesome. I also like about Rails that authentication and admin are not built-in. Lots of plugins available for a quick-and-dirty job anyway. I also like that defining models and even querying has been abstracted away in different interfaces, and that you can use MongoDB in a similar way as you would use a relational database. Also, in case you need to decouple the request validations from the models (i.e. forms in Django) without HTML-rendering logic attached (useful at times, but completely getting in your way once you try doing anything complicated); in Rails you can, and it looks and feels cleaner because the field types don't have to be related to stuff you're rendering in the HTML response (i.e. field = forms.MultipleChoiceField(widget=CheckboxSelectMultiple)). Django is awesome in case you ever thought about using Drupal for a project: much more flexible and dev friendly. But it completely got in my way so many times that I actually thought about writing my own Python web framework; which I shouldn't because people have been working on web-related stuff for the past 20 years.
- jasonwocky 16y ago>And Rake plugins (pieces of middleware, done in a standard/reusable way, contrary to Django's middleware) are just awesome. I think you mean Rack plugins (noted b/c Rake is something entirely different in Ruby parlance).
- bad_user 16y agoYes, thanks: it's a common misspelling that I make.
- mickeyben 16y agoAnd Rake plugins (pieces of middleware, done in a standard/reusable way, contrary to Django's middleware) are just awesome. I think you're talking about rack middlewares. Rake is the Ruby make.
- 16y ago
- shadowfiend 16y agoDepends on your definition of pain. I've found the full stack of Lift features quite accessible, if at times somewhat poorly documented (but the group is quite excellent for these situations), from the basics to situations where I needed to short-circuit most of the Lift handling pipeline entirely to serve up something specific. As for big projects, well, Foursquare is written in Lift.