Dmitri Zaitsev

> Yes, indeed. That example should work. In fact, one can always rewrite Turbine code to eliminate the use of generator functions. They are not essential. But they make things...

Just to show how verbose is React in comparison :) ```js class HelloTurbine extends React.Component { constructor(props) { super(props); this.handleChange = this.handleChange.bind(this); } handleChange(e) { this.setState({name, e.target.value}) } render() {...

Also the desugared chain version can be mentioned along and looks even simpler for this example: ```js const main = () => div('Welcome from Turbine!') .chain(() => input({ attrs: {...

@trusktr You raise some good points. How to put the output before the component is exactly the questions I asked in https://github.com/funkia/turbine/pull/31#issuecomment-301054029 and it appeared the Turbine provides a very...

@limemloh >Almost 😃 model have to return a Now Thanks for correction, I was thinking about it for a second and then left it out in the hope I would...

>>but I am not aware of any benefits of not merging them together like React does. > attrs is the same as setting attributes on the element which I think...

@paldepind @trusktr > The advantage of having attrs on it own sub-object is that attributes are then clearly separated from the other things. Is that an advantage because otherwise there...

@trusktr ```js input({ autofocus: true, placeholder: "Your name?", _output: { name: 'inputValue' } }) ``` It is an interesting idea, the props like `output` have some special functionality, so it...

@trusktr >We can't make that assumption, we don't know what requirements the DOM has, and there's also custom elements that can have any attribute names imaginable. There could be some...

Now removed the `js` and `yarn` stuff