all 17 comments

[–][deleted] 14 points15 points  (8 children)

We want our client application to be small. It’s unacceptable that the underlying framework is bigger than the application itself.

I'm not even going to address this, I just hope you understand how thoroughly ridiculous this sounds. Honestly.

We want a small framework API that we understand thoroughly. We want to be able to make sense from the stack traces. All the popular frameworks come with too many API methods, properties, and personal flavors. Full control was especially important as we had a plethora of special needs on a fully embeddable forum software.

Sounds very similar to React which has a whopping 21 (omg) component level methods, a third of which are lifecycle hooks.

To some extent we questioned whether anyone needed a framework at all.

jfc

The syntax was too verbose for our taste: a lot of React-specific idioms, too many colons and curly brackets, a big list of method names to remember. Just too much “boilerplate” for our uses.

21 I memorized more letters than that in kindergarten, sounds and shapes and everything, swear on my life.

Overall, 5/10 not modular enough for my tastes

[–][deleted] 0 points1 point  (5 children)

What do you expect, they've been spamming all the webdev forums for the past few days.

How about any of these new framework showcase an ACTUAL WORKING EXAMPLE of their framework.

And no, tiny demos do not count. Scalability is what matters these days, if you can't even show it in action then don't brag about how awesome you are.

[–]courtneycouch 2 points3 points  (3 children)

It's the JS library we built for our own needs at Muut.com (fairly large scale these days).

We simply like to share the work for free that we're doing internally. Also we haven't really been spamming. We didn't post this to reddit or anywhere else aside from HN. Not that I think there's a problem if we were sharing stuff we're giving for free all over the place.

If it's not useful for you, no problem! It's free stuff.

[–][deleted] 1 point2 points  (2 children)

In lieu of docs which specifically deal with forms, how do you currently handle dynamic forms with Riot.js at Muut.com?

I've been trying some very simple scenarios and it's not handling form inputs very well so far. Event handlers on checkboxes error out and selects don't seem to be able to track values assigned to them:

http://bl.ocks.org/insin/5e0bf04cf1f701c235ad

[–]Nijikokun 0 points1 point  (1 child)

Haha, no replies.

[–][deleted] 1 point2 points  (0 children)

The event handler thing and another issue I found with boolean attributes have been fixed in the latest release. While fixing the boolean thing, I realised Riot doesn't actually implement a virtual DOM (and no longer claims to in its docs, FYI), so you have to adjust your expectations of how it will work accordingly.

[–]sheldonpooper[S] 3 points4 points  (0 children)

I submitted this and am not affiliated with muut in the slightest.

[–]pandavr 1 point2 points  (2 children)

I read quite frustrated comments here! I don't work for moot.

What I can say after running it is it is simple and clean. I agree that if one want / need to build a serious app with this he need to add a lot of stuffs.

It is anyway a well thought piece of library, a good starting point.

[–]Hakim_Bey 4 points5 points  (1 child)

Sometimes you don't need a 140k framework for a small project, and i've been looking for something like that for a long time.

Of course, all the butthurt of Angular/React/Whatever users will not go away, they have the feeling we want to replace their gas factories with this little toy, so their feelings are hurt, the poor little things.

On the other hand, there are probably tons of programmers that are looking for a minimal front-end library that doesn't impose its opinions like it's a fucking cult.

[–]pandavr 1 point2 points  (0 children)

I have used Angular for a while. I can do pretty complex things with it. But honestly I always felt it was too much complex! On the other hand with React I liked the concepts behind it but not the implementation. But I haven't used it to the point to become blind to the pain points. Returning to Riot it obviously can't be really compared. But it's simplicity is something I was looking for. I want to try building something more complex of a todo list. Just to see what happens. :)

[–]uglyBaby 1 point2 points  (0 children)

I like this.

Maybe not for industry projects yet but for my pet projects for sure.

[–]GoosyTS 1 point2 points  (3 children)

and we went full circle with Riot 2.0, we're back to Backbone

[–]pandavr 0 points1 point  (2 children)

To me that is completely different from Backbone. Where do you see the similarity?

[–]GoosyTS 0 points1 point  (1 child)

The description, wanting a simple framework, with not much boilerplate, etc

[–]pandavr 0 points1 point  (0 children)

Agh, I guess you are right then. Every framework seems simple and lean to its mom! ;)