Hey! I'm the annoying developer :) I'm sorry if I came out in a bad way. It's not my intention to be harsh and I'm trying to be open to the critics. It's just a

Hey! I'm the annoying developer :) I'm sorry if I came out in a bad way. It's not my intention to be harsh and I'm trying to be open to the critics. It's just a damn hard to point out that the current frameworks are mostly unnecessary and you can make large scale apps with Riot that only has 3 extra methods. It can totally understand that people don't take it easily. And it's especially hard if you are already using a certain framework and feeling good with it. I can see from your comment that you are biased towards MVVP and Angular in particular. You prefer to express the logic in the HTML template and use two-way data binding and avoid using jQuery (Official Angular suggestion). It's a very different approach and you cannot really compare Riot and Angular directly. It's a much broader comparison between MVP and MVVM patterns. A massive topic. I strongly think that MVP scales much better than MVVP and is better for bigger applications/teams. It's easier structure the codebase in modular fashion. Riot documentation focuses solely on this topic. Moot is not a "tiny chat app", it has pretty vast feature set and the code is split into 50 different files. MVP definitely scales.