@mikekelly85 @stilkov I don't think the comparison is valid, no. Route helpers is not primarily for "moving URLs around". Cleaner code, thou

@steveklabnik @mikekelly85 @stilkov Agree that it's a nice practice but benefits are overblown. We've had public APIs for YEARS w/o breakage

@steveklabnik @mikekelly85 @stilkov "almost always lead to disaster" doesn't match any experience I've had with using IDs.

@steveklabnik @mikekelly85 @stilkov Basecamp's API is close to 8 years old. Hasn't broken any URLs.

@steveklabnik @mikekelly85 @stilkov Same goes for lots of other stable, long-running APIs. See Flickr, for example. Even REST is overrated.

@steveklabnik @mikekelly85 @stilkov (The public benefits of REST, that is. I think it's a wonderful app design technique, though).

@steveklabnik @mikekelly85 @stilkov Have you personally felt the pain of breaking a lot of API urls? Do you have some links to this hurt?

@mikekelly85 @steveklabnik @stilkov Ha. I think it's great. Forces the point to be distilled. Less room for hand-waving.

@steveklabnik @dhh @mikekelly85 @stilkov I believe that works for the use case where you can blindly automate URL extraction in the client

@steveklabnik When Hypermedia discussion is watered down 2 URLs it means someone does not understand Hypermedia. U will just get frustrated.