Live data from Hacker News

Riot – A React-like, 2.5K user interface library

muut.com

101–110 of 222 posts

Re: Riot – A React-like, 2.5K user interface library

#101

One of the biggest selling points for React/Flux for me was the fact that it had been proven by Facebook and Instagram on some very large projects. What has this been used on?

Welcome to the "Nobody was fired by hiring IBM" of the new century.

Re: Riot – A React-like, 2.5K user interface library

#102
post #66

Oh a new Javascript framework. I'd been getting worried, it'd been 40ms since the last one.

Oh a dismissive comment on HN upvoted to the top. I'd been getting worried, it'd been 1 post since the last one.

Oh a strawman comment on HN...

Re: Riot – A React-like, 2.5K user interface library

#103

This seems way different than the library I remember 6 months ago... https://github.com/muut/riotjs/tree/8c7e841e2c7724df9bab9397... Rebrand?

It seems like their manifesto here hasn't really stood the test of time: https://muut.com/blog/technology/riotjs-the-1kb-mvp-framewor... (The bits about jQuery at least, anyway.)

True. Things have changed since then. Especially about role of jQuery in views. Riot 2.0 unifies HTML/JS together causing less need for it.

I still think jQuery is still fantastic and definitely has a lot of use cases.

Re: Riot – A React-like, 2.5K user interface library

#104
post #60

Seems more like Angular than React with the template expression, why compare it with React then ? Angular is now a dirty word ?

React is closer to Riot than Angular because of HTML/JS components backed with virtual dom. The HTML syntax is perhaps closer to Angular than JSX.

I'm sure there will be a Angular comparison here as well:

https://muut.com/riotjs/compare.html

Ember too, because of HTMLBars (DOM based templating) and FastBoot (later).

Re: Riot – A React-like, 2.5K user interface library

#105

After using ember's router and react-router, I can't do client side routing with a router like this (or backbone's, or anything that is sinatra like). The layout management part of nested routes is crucial and way too hard to do with something as minimal as this. That said, great work on this library! I'm impressed with how much functionality you guys have in such a small package.

By nested routes, you're referring to the kind of thing described by finchjs? How are they critical to your workflow? Would be interested to learn more.

Re: Riot – A React-like, 2.5K user interface library

#107

Earlier quoted context omitted.

Virtual DOM implementation is indeed different. The biggest reason for calling it "React-like" is the basic idea of components, where related HTML and JS are combined together. > "Build components, not templates" http://www.slideshare.net/floydophone/react-preso-v2 I think this is the "what" of React and virtual DOM is the "how".

I don't think of something as React-like just because it puts HTML and JS in the same file or combines HTML tags with blocks of JS code. The difference between React and other databinding methods is that you can use all JS language features (i.e. if, for, while, .filter(), .map(), libraries like Rx.js, etc.) when defining what you want your DOM to look like. Suppose I want to have a list of items based on some array,…

> I don't think of something as React-like just because it puts HTML and JS in the same file or combines HTML tags with blocks of JS code.

Totally agree. While I do (most of the time) appreciate JSX, it is IMO the least interesting and relevant feature of React. It mostly just lets our company's designers continue to edit view templates that would otherwise be far beyond their training/experience. So that's nice, but it's not what makes React tick.

Re: Riot – A React-like, 2.5K user interface library

#108

After using ember's router and react-router, I can't do client side routing with a router like this (or backbone's, or anything that is sinatra like). The layout management part of nested routes is crucial and way too hard to do with something as minimal as this. That said, great work on this library! I'm impressed with how much functionality you guys have in such a small package.

Which (if any) client side router library do you prefer then?

Re: Riot – A React-like, 2.5K user interface library

#109
post #66

Earlier quoted context omitted.

Oh a dismissive comment on HN upvoted to the top. I'd been getting worried, it'd been 1 post since the last one.

Oh a strawman comment on HN...

Oh, a reddit meme on HN. I'd been getting worried. I hadn't seen one of those here yet.

Re: Riot – A React-like, 2.5K user interface library

#110
One thing I like React is it is plain javascript.

Therefore I can use coffeescript to describe the component:

    {div, p, ul, li} = React.DOM
    ...
    render: ->
      div className: 'foo',
        p className: 'bar', 'blabla'
        p className: 'bar', 'blabla'
        ul className: 'somelist',
          @state.items.map (x) -> li key: x.id, x.content
            
If Riot.js uses a custom parser, it may not be able to do this.
Post reply on HN