What I take from the article is that we try to push things into where they don't really fit. I like the modern URLs we are building now, that they are easy to u

What I take from the article is that we try to push things into where they don't really fit. I like the modern URLs we are building now, that they are easy to understand to humans. The problem is not wether we should use GET or POST, the problem is when we try to use PUT and other verbs for things they are not ment to do. If you want a system to perform an action, it's not GET or POST, but it's not PUT either. You can't use the old HTTP error codes for application errors such as "flight is overbooked."