Comments on: Dispatch: A Day of Cleanup http://yehudakatz.com/2009/01/10/dispatch-a-day-of-cleanup/ Random Geek-Related Thoughts Tue, 16 Mar 2010 14:46:49 -0700 hourly 1 By: Markus Jais http://yehudakatz.com/2009/01/10/dispatch-a-day-of-cleanup/comment-page-1/#comment-15373 Markus Jais Tue, 13 Jan 2009 07:14:04 +0000 http://yehudakatz.com/?p=188#comment-15373 Great stuff. I am looking especially forward to Rails 3 being JavaScript agnostic. I think this will be one of the great features of the new version. Great stuff. I am looking especially forward to Rails 3 being JavaScript agnostic. I think this will be one of the great features of the new version.

]]> By: Weekly Digest, 1-11-09 - almost effortless http://yehudakatz.com/2009/01/10/dispatch-a-day-of-cleanup/comment-page-1/#comment-15365 Weekly Digest, 1-11-09 - almost effortless Mon, 12 Jan 2009 04:36:53 +0000 http://yehudakatz.com/?p=188#comment-15365 [...] A Day of Cleanup I’m going to start putting together a quick prototype of how Rails3 can be JavaScript agnostic while retaining the existing JS helpers next week some time. I’ve already gotten a lot of good feedback from the jQuery and Mootools communities, and plan to get as much involvement as possible as I move forward. [...] [...] A Day of Cleanup I’m going to start putting together a quick prototype of how Rails3 can be JavaScript agnostic while retaining the existing JS helpers next week some time. I’ve already gotten a lot of good feedback from the jQuery and Mootools communities, and plan to get as much involvement as possible as I move forward. [...]

]]> By: José Valim http://yehudakatz.com/2009/01/10/dispatch-a-day-of-cleanup/comment-page-1/#comment-15345 José Valim Sat, 10 Jan 2009 14:15:58 +0000 http://yehudakatz.com/?p=188#comment-15345 "... but the end result is memoized methods that will retain their names in stack traces ..." Imho, this is the most important. So I'm 1 for this solution, but I still prefer the one from previous post. :) I hope you can share what you have mind for JS agnosticism soon and also plans for the router merging (the "hardest" part maybe?). Keep up the great work! “… but the end result is memoized methods that will retain their names in stack traces …”

Imho, this is the most important. So I’m 1 for this solution, but I still prefer the one from previous post. :)

I hope you can share what you have mind for JS agnosticism soon and also plans for the router merging (the “hardest” part maybe?).

Keep up the great work!

]]>