Towards a better API framework

From the server side of APIs, here's an interesting article on the past (Rails-style MVC frameworks) and the future (HATEOAS, essentially).

This deserves some thought. Maybe a plain function isn't the best way to organize code, and maybe OOP isn't quite there yet, either. Maybe something like an API is a valid level to understand code at.

I think I need sleep.