A Fresh Cup is Mike Gunderloy's software development weblog, covering Ruby on Rails and whatever else I find interesting in the universe of software. I'm a full-time software developer: most of my time in recent years has been spent writing Rails, though I've dabbled in many other things and like most people who have been writing code for decades I can learn new stuff as needed.

As of October 2016, I'm not actively looking for my next job, but I'm still happy to chat about potential opportunities. I'm not able to relocate, so unless you're in the Evansville area, I'd need a completely remote gig. I have lots of experience working remote. Prefer full-time but I wouldn't be averse to an interesting contact gig. Drop me a comment if you've got something or email MikeG1 [at] larkfarm.com.

Navigation
« Double Shot #842 | Main | Double Shot #841 »
Monday
Mar192012

What's New in Edge Rails #13

Week of March 11-March 17, 2012

The big news this week: Active Resource has been removed from Rails, and "API only" Rails applications put in a brief appearance before going back to the drawing board.

  • Text fields and text areas no longer have default size, rows, or cols as of 3384ee24. It's 2012, if you want a default set it in your CSS.
  • eee32af45 adds a dynamic find_or_create_by_{attribute}! method to Active Record.
  • With f1637bf2 Active Resource has been removed from Rails. It will be available as a separate gem if anyone wants to maintain it, though I suspect most people who need that sort of functionality are using one of the alternatives already.
  • c1f397f88 merges a chunk of work to remove sprockets integration from Action Pack and depend on the sprockets-rails gem instead.
  • dde3058c7 removes the Active Record IdentityMap feature, which never worked right anyhow (see 302c912b for some details of the problems).
  • A bunch of commits starting at 4c16791f added "API only" Rails applications. All of them were reverted in 6db930cb because the feature is still half-baked.

Reader Comments

There are no comments for this journal entry. To create a new comment, use the form below.

PostPost a New Comment

Enter your information below to add a new comment.
Author Email (optional):
Author URL (optional):
Post:
 
Some HTML allowed: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <code> <em> <i> <strike> <strong>