Hacker News new | comments | show | ask | jobs | submit login
Rails core killed ActiveResource (github.com)
52 points by rafamvc on Apr 9, 2012 | hide | past | web | favorite | 11 comments



I really wanted ActiveResource to work for me, but I had a few requirements that it couldn't meet, like camelCased attribute and resource names, HTTP caching, and the ability to change authentication at runtime without race conditions (since configuration is done at the class level in ARes).

I wrote a small gem called well_rested to replace ActiveResource in my project. It utilizes ActiveModel for validations and generally plays well with Rails. Maybe it will be useful to someone:

https://github.com/DeepWebTechnologies/well_rested


For anyone that still needs it, it lives on as a separate gem: https://github.com/rails/activeresource


I used AR for a small project a year or so ago.

What are people's favourite alternatives?


I use RestClient. It needs more code, but is more flexible.


That’s funny, today I released a small project of mine I started over the weekend that is meant to be an alternative to ActiveResource:

https://github.com/remiprev/her

It’s still very basic, but I hope to get more features into it in the next weeks.


Keeping a clean code base in large part means having the courage to throw stuff away. Open source is good at this, and I commend the rails team for doing this so easily.

It's a problem I encounter in the "professional" space often, people have a a personal attachment to code. Either because

- they identify with it personally (their self worth)

- they value the hours they put in, and feel deleting it would make all that time worthless/wasted

Writing code is a journey through a specific problem domain. Once you've walked the path a couple of times, subsequent attempts become easier and smarter. I feel a healthy attitude is to see it that way. A lot of early code is just the byproduct of you discovering and exploring said problem.


ActiveResource was very buggy and it's good they're getting rid of it because it doesn't seem like there was any effort for improving that wart. Django ROA, which is just a third-party app, is far more thorough and predictable.


It could've been nice. I don't have links to back this up, but I seem to remember getting patches accepted for it was difficult. I am assuming that is because there wasn't anyone on core that really cared about keeping it up to do with the rest of the Active(.*) universe.


Regardless of everything ActiveResource is or isn't, I am very sad to see Rails lose its out-of-the-box web service client. ActiveResource is an 80% solution which really deserved to have that last 20% filled in.

That said, I'm excited for something better to get traction.


And? This is pretty old news…


I used AResource for several projects, that are still alive, so it impacts when updating to a new version of rails.




Guidelines | FAQ | Support | API | Security | Lists | Bookmarklet | Legal | Apply to YC | Contact

Search: