Learning Node.js and React while building a product

Post by godot » Tue, Jun 13, 2017, 6:44 PM UTC

abritinthebay wrote: post #17

acemarke wrote: post #3

Hmm. So, the complaints about React are "no convention over configuration", "we didn't like JSX", "event handlers require binding for `this`", and "trouble finding a correct source of truth" for articles and such. The first two are pretty common. Some people _love_ that React lets you pick and choose the other pieces that you need for your own application, while others hate that React isn't a kitchen-sink-provided fr…

Agreed. The main complaint is just "I want a framework and I chose a library." JSX isn't even required either. It just desugars into: React.createElement(elementClassorString, props, children); If they want to use their own function for that... they can, but JSX is a trivially easy way to describe nested components (which can get verbose with the above). A nice bonus of JSX is that it also means your components and r…

Post by dcgudeman » Tue, Jun 13, 2017, 7:20 PM UTC

Post by miroslavpopovic » Tue, Jun 13, 2017, 8:00 PM UTC

antihero wrote: post #16

miroslavpopovic wrote: post #5

Earlier quoted context omitted.

Hey @acemarke, thanks for the comment! For myself, I still have not decided whether I like JSX or not :) My colleague finds it great, and I like the declarative nature of it, just need to persuade myself to accept it mixed in JS file. Yes on .bind, but I got used to not having to care about it in Aurelia (and Angular also). Got my fair share of `this` handling in pre-ES6. And of course, thank you for the links. Bookm…

I've found that the best way to make event handlers is instead of doing class Blah { private handleThing(...) {} } to instead do this class Blah { private handlething = (...) => {} } this means that it is created only once, at instantiation of the component, so it is fast, looks decent, and has access to `this` as it's technically a method on the object, not the class. Also, if you're coming from C# land, head straig…

Post by coldtea » Tue, Jun 13, 2017, 8:03 PM UTC

miroslavpopovic wrote: post #9

jmschlmrs wrote: post #7

Earlier quoted context omitted.

Are you using arrow functions? I find that using es2015 arrow functions for class methods takes care of most of the problems around this and react. The only annoyance is dealing with binding event handlers to items/components in a list. Generally you need to abstract the list item into it's own component and do the event handler binding there. I don't use .bind() anywhere in my react code.

Yep, we are using arrow functions and other ES2015+ goodies, but they don't help with event handlers. In fact, I believe class property syntax helps with that, but we only figured it out after we built these few pages and components necessary for the web app part.

  myHandler = (v) => {
    ...
  }

Post by miroslavpopovic » Tue, Jun 13, 2017, 8:06 PM UTC

godot wrote: post #21

abritinthebay wrote: post #17

Earlier quoted context omitted.

Agreed. The main complaint is just "I want a framework and I chose a library." JSX isn't even required either. It just desugars into: React.createElement(elementClassorString, props, children); If they want to use their own function for that... they can, but JSX is a trivially easy way to describe nested components (which can get verbose with the above). A nice bonus of JSX is that it also means your components and r…

I find it a bit odd that both you and the parent commenter (acemarke) seemed to have interpreted the post in a completely different tone than I did. I didn't find anything in the original blog post in the tone of a "complaint". If anything, they were merely pointing out what kind of things they run into and their thoughts, while transitioning from an ASP.NET background. It's actually a really helpful read if you also…