tn6o

Haters will always hate. Keep up the good work guys! People seem to think they are entitled to something when using open-source software, but they're not. It's still the people working and maintaining it who get to take the decisions, and if you guys think you need analytics to provide a better tool, go for it.

I also completely understand the need for default opt-in. I probably wouldn't check the prompt and leave the default, but for a project like this, I honestly don't mind sending usage data.

If you're not happy with the direction taken by the maintainers, find another tool.

Agreed.

And then the 1% will start complaining. "Why me?"

The team behind Brew is doing a great job and if analytics can help them do a better job, then be it. Nobody is forcing you to use it and opting out is simple enough.

Yes, I know about this model but it wasn't made by Fielding and he made his positions pretty clear about what's RESTful and what's not.

I do agree that this model is a good set of steps to build better APIs but then, how do you call them? RESTful Level 1 API?

My point with this article is just to call API what they are (usually just HTTP APIs). I'm totally against the use of the REST buzzword these days since it doesn't mean much anymore: everyone has a different view on it.

The link you gave is pretty good. Note however, that in this article I wasn't trying to explain in details what is REST.

What I want is more to let people know why their APIs are not RESTful so they can use the kind of resources you gave to actually learn more about REST.

Thanks for sharing!