Developing with Riot is completely different from other frameworks. It's just 3 functions and after 1.0 the API will be hardened. It's more of a design pattern than a framework. The application developer is the biggest culprit for breaking things.

Calling this a framework is a bit of a stretch isn't it? I don't see how a few helper functions that rely on a very large library constitute a framework for doing anything at all.

Yeah. I guess it's more of an library, but it promotes the use of MVP design pattern / way of coding – and can thus be interpreted as a framework. I might change it to library if it makes more sense.

That's the same thing with Rails.

You don't follow a rule, it doesn't allow you to do it. You need to go by the book there, so why not here?

Rails is much more than just 4 methods.