Riot.js – A 1kb client-side MVP framework
1–10 of 147 posts
Re: Riot.js – A 1kb client-side MVP framework
#2Uh MVP (Minimum Viable Product) vs. MVP (Model View Presenter). That will be confusing.
(still nice project of course)
Re: Riot.js – A 1kb client-side MVP framework
#3This looks really pretty good. I think I would miss things like ng-each, but I guess not that's not -too- hard to re-implement using $.data('each'). Maybe.
I will consider using this for a site I'm building right now, see what happens.
Re: Riot.js – A 1kb client-side MVP framework
#4Uh MVP (Minimum Viable Product) vs. MVP (Model View Presenter). That will be confusing. (still nice project of course)
On HN (or another startup / business-oriented board), I'd agree it's a bit confusing.
In terms of UI development, the Model-View-Presenter pattern has been around (and fairly mainstream) for a couple of decades now, so the target audience will probably assume correctly.
Re: Riot.js – A 1kb client-side MVP framework
#5Uh MVP (Minimum Viable Product) vs. MVP (Model View Presenter). That will be confusing. (still nice project of course)
Meh, I wasn't confused 'cuz it said "framework," but I guess I'm more of a hacker than a startup junky. ^_^
Re: Riot.js – A 1kb client-side MVP framework
#6I love the refreshingly minimal approach, although jQuery dependency ruins some of the excitement, but still, great work guys!
Re: Riot.js – A 1kb client-side MVP framework
#7How can someone just beat Resig's or Jashkenas' code performance "that easily"?
Re: Riot.js – A 1kb client-side MVP framework
#8How can someone just beat Resig's or Jashkenas' code performance "that easily"?
By doing less.
Re: Riot.js – A 1kb client-side MVP framework
#9key feature of many frameworks is that they break if you don't follow them carefully, limiting damage from 10x developer's hacked together code. does riot provide similar functionality?
Re: Riot.js – A 1kb client-side MVP framework
#10I love the refreshingly minimal approach, although jQuery dependency ruins some of the excitement, but still, great work guys!
Thanks. jQuery dependency is intentional since the library promotes the use of jQuery on the presenter layer.