Totally get what you mean. The size of community and the level of support cannot be compared to Angular or React. You need to make a more technical analysis / comparison on the decision process and trust your "guts" when making the choice. For me the more standards based and clutter free syntax is the winning factor for Riot causing less to study and makes it more tempting for new developers on a project.
Riot.js seems to me a pretty awsome framework, really simple and minimalistic, thanks, Tero. Can't wait to build a web app with it!
Ho ho ho, this is waht I've been looking for!
Looking forward for those performance comparison tests :)
This post seems dated (it's dated January 22, and currently it's Jan15, 2016). It would be nice for a follow up to see which of he future enhancements you were able to complete since it's writing.
Compared with http://vuejs.org Copy Paste from >> http://vuejs.org/guide/comparison.html#Riot ~~~~~~~~~~~~~~ Riot 2.0 provides a similar component-based development model (which is called a “tag” in Riot), with a minimal and beautifully designed API. I think Riot and Vue share a lot in design philosophies. However, despite being a bit heavier than Riot, Vue does offer some significant advantages over Riot: @ True conditional rendering (Riot renders all if branches and simply show/hide them) @ A far-more powerful router (Riot’s routing API is just way too minimal) @ More mature tooling support (see webpack + vue-loader) @ Transition effect system (Riot has none) @ Better performance. (Riot in fact uses dirty checking rather than a virtual-dom, and thus suffers from the same performance issues with Angular.) ~~~~~~~~~~~~~~ Hope Next release of Riot will become much better :) Good Work @Tero and Team. Keep rocking <3 <3 <3
How about Mithrill js. http://mithril.js.org/ => Only 7.8 kB gzipped, no dependencies => Small API, small learning curve => Robust => Safe-by-default templates => Hierarchical MVC via components => Fast => Virtual DOM diffing and compilable templates => Intelligent auto-redrawing system
React source code is 20x bigger and the syntax is much different. It's unlikely that they would accept our radically different pull requests. Mithrill is cool, but the syntax of writing components doesn't feel natural enough for us.
I guess the bottom line is that _we needed yet another js framework for ourselves_, one that does and is exactly what we want. If — as it seems — others find it useful, then that's only a nice bonus.
I think this can be interesting for smaller applications / widgets where we don't want the overhead of frameworks like Angular, Ember or React
I absolutely love Riot, but something I really missed coming from React was being able to define expected PropTypes for my components. If anyone else misses this functionality I've created a Riot mixin here which adds this functionality to a Riot app: https://www.npmjs.com/package/riot-opt-types-mixin
That's what we thought and built the be-all and end-all solution for our own purposes ;)
I am using Riot.js for many of my school / personal projects. I love the way it lets me write my apps. Simple components. Please keep up the good work!!!
Let's try some riot. Can you please tell me what's the color scheme/syntax highlighting that you're using? Thank you.
This is a great example when less popular JS frameworks fit better for the job. Thanks for sharing this with us! After all, it's important to not forget that the technology you use should always be chosen according to the project's requirements. Of course, the big players like Angular or React are used a lot not only because of they are popular, on the contrary, they fit well for many cases and thus are popular. So, my point is not to forget about technologies like Riot, Dojo, and SproutCore, because sometimes(https://mobilunity.com/blog/usage-of-rare-technologies-by-a-js-developer/) one of them can fit you better than the most popular ones.