Panasonic Youth rob sanheim writes about software, business, ruby, music, stuff and things



Posted
1 September 2006 @ 2am

Tagged
Ajax, Rails, Ruby

Discuss

Deprecation in Rails, and What You Can Do About It

Now that the sound and fury over Kevin’s post on the old and busted in Rails is calming down, we do have some nice constructive resources. One is Geoffrey’s Deprecated Plugin which greps your code for things like @params or render_partial. Very nice, and he’s going to rewrite it so its not dependant on grep, so those poor win32 people can use it. Those guys probably don’t care about deprecated stuff anyways, as they are too busy lusting after macbooks. Thats a little “geek humor” for you there…

A Deprecated Patterns page on the wiki got some love, and Jimmy took some steps to flesh it out and I added a few things here and there. So go and add anything you think is missing, and keep that url handy to pass along on rails-talk. My call for http://deprecated.rubyonrails.org went unheeded, but the wiki will be good enough. Until it gets crushed with spam again, that is. Maybe Ruse should take the place of i2 for the rails wiki?

I’ve also heard talk of the ajax helpers being removed from core, but haven’t seen it from the trac feed yet. Is that happening in time for 1.2?


1 Comment

Posted by
BigJimmy
1 September 2006 @ 6am

Thanks a mil for picking up the ball and adding those links on the wiki. I agree that the entire wiki needs to be “weeded” but it was the path of least resistance.

I’m still not sold on the idea of plugins for one-shot deals like finding deprecated stuff. I guess you just uninstall it when you’re done, but it seems like that’s the rare case where a gem would be preferable (ala capistrano).

Thanks again for playing along.


Leave a Comment

Symbol#to_proc and inconsistent code vs DRY Accessing Rails Configuration and database.yml Programatically