
3/31/2012
What this post added
This post clarifies the author's previous arguments about RESTful thinking, emphasizing that the primary concern is the intuitive design of applications, particularly for new developers, rather than a strict adherence to REST semantics. It highlights the potential for developers to misuse Rails' RESTful conventions (e.g., abusing the `update` action for state transitions) leading to data loss. The author suggests that Rails should integrate state machine implementations and that educational materials should prioritize teaching state machines for complex operations, with RESTful API design being a subsequent step.