After reading your post and interacting on this page, I'm am willing to bite. Besides, I hate following the crowd. ...be it software, religion, politics, etc. it's not that the crowd is always absolutely incorrect. But I like to form my own opinions. So, where to begin?
You can read more here: [Follow up blog post - Riot.js](https://moot.it/blog/technology/riotjs-the-1kb-mvp-framework.html) [Riot release info](https://moot.it/riotjs/) [Github repo](https://github.com/moot/riotjs)
why thank you! :)
I just got to this line on Riot: , and is the *best pattern for unit tests.* I got into TDD in 2008 and have been hooked ever since. Back to Riot reading...
I couldn't agree more with you! It all seems like big conspiracy, people using frameworks like crazy. it feels so wrong.
Should have used ExtJS (combined with sencha touch) in google trends comparisons also... and with the massive decline in jquery mobile...
I'm currently scouring the web for a decent framework, but I noticed you said something and wanted to pass some advice. If you want the two-way binding from Angular without all the extra stuff, knockout is a great framework. It's only 13K and crazy fast in my opinion: http://knockoutjs.com/
Oh, but I thought jQuery was large too! Is it worth it to you? I'd love to hear how you ended up using it. I do agree that Vanilla JS is the best toolkit :) And the recent fast.js revelation that the side effects of many JS Array methods makes VJS MUCH faster than native (and also works with Typed Arrays, important for my project. It would be nice if Object.observe was in most browsers, would make "binding" that much easier.
changed my mind...
Changed your mind? About what?
"If you look at the history of frameworks in any programming language, it’s a history of failures." How do you define "failure"? There are popular, long-lasting frameworks actively used to this day in several languages, eg, Struts 2, Spring, Wicket (Java); Django, web2py (Python); CakePHP, Symfony (PHP), just to name 3 languages. These frameworks don't seem to be going away any time soon.
I'm sure you know what I mean with that. There are far more failures than success stories. And your list also looks a bit suscpicious; slightly outdated tools that will eventually fade away since there are already "modern" alternatives available.
[Riot 2.0 is out!](/riotjs/) This is large rewrite brings custom tags for all browsers starting from IE8. Think React + Polymer, but squeezed into 2.5K. It's a full stack with virtual DOM, "reactive views", router and observable.
'3.5 years to build Moot' - r u serious?
> @resolution1441 > 3.5 years to build Moot' – r u serious? Absolutely. There are multiple reasons for why it took that long, speed, scalability and (apparent) simplicity of the UX being some of them. There's a blog entry about this called [You spent 3.5 years on this??](https://muut.com/blog/technology/you-spent-3.5-years-on-this.html)
Are you recommending then using YOUR framework then? That's not exactly framework less, is it? =)