moot

Open full view…

From frameworkless JavaScript to Riot 2.0

Thu, 22 Jan 2015 13:31:21 GMT

Florian Coco
Sun, 08 Mar 2015 18:34:34 GMT

I'm a Riot 1.0 user since last year, my app is following the principles of frameworkless mvp with passive-views and I'm now excited to rewrite my app entirely with riot 2.0 ! =D

Anderson Sousa
Thu, 14 May 2015 13:03:34 GMT

Definitively we need real examples of using it. The framework is very exciting but even it is in version 2 is not very adopted yet. A simple question: Why would developer leave some tools like Angular or React full of support from community and developers, with a great integration to other frameworks to use Riot? Any "ionic like" framework is being developed? Do you get what I mean?

Tero Piirainen
Fri, 15 May 2015 09:53:26 GMT

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.

Cristian Llanos
Sun, 24 May 2015 18:56:56 GMT

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!

Irwansyah Irwansyah
Sun, 08 Nov 2015 02:29:58 GMT

Ho ho ho, this is waht I've been looking for!

Josema Enzo
Thu, 07 Jan 2016 10:46:11 GMT

Looking forward for those performance comparison tests :)

Christian Hain
Fri, 15 Jan 2016 21:21:02 GMT

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.

Jem Tan
Sat, 30 Jan 2016 04:44:51 GMT

How about comparing with Preact? Any comments? http://developit.github.io/preact/?utm_source=javascriptweekly&utm_medium=email

Susanth K
Fri, 12 Feb 2016 11:24:47 GMT

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

sylvan
Mon, 21 Mar 2016 09:30:12 GMT

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

adamdonahue
Mon, 11 Apr 2016 20:12:45 GMT

This is such a waste of time. Why not focus your efforts on improving the flaws you see in React instead of rewriting it? We don't need yet another JavaScript framework!

Tero Piirainen
Wed, 13 Apr 2016 06:14:51 GMT

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.

Janne Lehtinen
Wed, 13 Apr 2016 06:24:24 GMT

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.

alvinvogelzang
Wed, 13 Apr 2016 08:27:54 GMT

I think this can be interesting for smaller applications / widgets where we don't want the overhead of frameworks like Angular, Ember or React

Tero Piirainen
Wed, 13 Apr 2016 08:48:05 GMT

I actually think it's the opposite. When architected well, big applications are composed of multiple smaller applications and those smaller applications are yet broken into smaller pieces. Riot (and React) assumes that the ideal building unit is a component that unifies HTML and JavaScript. The simple and powerful Riot syntax gives a strong foundation for a developer. Large applications become a hierarchy of custom tags that you can read in a WYSIWYG manner. Definitely good for keeping things in order. I think organization skills are most important for a programmer to keep sanity in a large software project. And Riot aims to be the most intuitive construction unit for any frontend application.

theprotocol
Sun, 08 May 2016 10:33:04 GMT

I've just started using riot after getting sick of the Architecture Astronaut approaches used in most of the other frameworks, especially Angular. Some UI frameworks these days are seemingly designed by a kind of euphoric, embarrassing attitude that what they're doing is simply the greatest, right down to the jargon they invent, which they promptly hit you over the head with. It's unreal. I agree with the riot approach: acknowledge that React as described in English is great, but that its implementation is slightly overwrought (although nowhere near the level of the madness that is Angular). I've begun using riot on a commercial product and I'm pleased to say it's just what it says on the box. It's straightforward. It doesn't make you pump out HTML from javascript functions like React or Mithril do (who ever even thought this was a good idea). It doesn't force you into a dogmatic conception of what MVC is (the definition of each part of MVC is under debate and l acks consensus, with many frameworks claiming to offer the "one true" implementation of MVC). I've got to say I'm really happy with it.

justinschrader
Thu, 11 Aug 2016 23:01:50 GMT

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

jalenes
Tue, 08 Nov 2016 03:34:41 GMT

Wow seriously just stop already. We have enough frameworks to deal with and its just painful to see more useless ones pop out of nowhere. This JavaScript craze needs to stop. JavaScript isn't everything for gods sake.

Janne Lehtinen
Fri, 18 Nov 2016 10:50:48 GMT

That's what we thought and built the be-all and end-all solution for our own purposes ;)

jonaspm
Tue, 23 May 2017 00:07:02 GMT

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!!!

next
last page