It’s almost bewildering to see how many different (contrasting) opinions there are out there. After reading the post, check out the comments.
There are disagreements on which approach is the most performant, on whether using a custom collection of libraries (more flexible but more work) or a more complete framework (less flexible but less work) makes mores sense. There is disagreement over whether a whole site should be a Single Page Application, or just a section of a site. In fact, there’s disagreement over what constitutes the difference between a “site” and an “application” to begin with. There’s disagreement on whether client-side or server-side DOM-building is faster.
But the thing that struck me the most was this: The article starts with the premise:
“Itâ€™s no longer good enough to build web apps around full page loads and then â€œprogressively enhanceâ€ them to behave more dynamically.”
but as one commenter astutely points out:
“â€¦ unless you happen to be github or 37signals, in which case you can easily build apps and progressively enhance to be fast and responsive â€¦.”
But I’m ready and willing to have my philosophy tweaked on this – all I need is an example of how JS-based DOM creation can be as fast, easy, and performant as it is in Django, while still giving easy access to deep data traversals, model methods, and permissions (without jumping through time-costing hoops).
Today I begin my exploration of Rails in ernest. It’s becoming apparent that Rails has evolved in this direction more quickly than Django by building REST directly into the framework (Django is more about extremely DRY data modeling and it’s awesome auto-generated internal API).
So much to think about, so much cool stuff to explore.
Google+: View post on Google+