41–50 of 131 posts
For anyone else who, like me, didn't realize it - there's a little triangle on the bottom right to let you go through the presentation.
Space seems to work as well. I love it when a page telling you not to use something fails at UX.
For anyone else who, like me, didn't realize it - there's a little triangle on the bottom right to let you go through the presentation.
I think that author is completely right about the part, that React has the only one reactive part — its render function. But I don't see why it makes React bad. I think it is great, fast and easy to use. By the way, virtual-dom is a little bit early to use for production application. For example, if you have some elements in your vdom, that are changing after you render it (i.e. like buttons, embeded posts, etc.), vi…
>For example, if you have some elements in your vdom, that are changing after you render it (i.e. like buttons, embeded posts, etc.), virtual-dom will be totally confused and unpredictable. I can't think of a reason that someone would use react and still bypass it do their own dom modifications.
Also, lets not forget React Native. NO other framework can prove that compatibility with mobile. A React programmer can now cover both web and mobile development with relative ease. I'm not saying that React Native or React is perfect, but I would argue it is the best option for any company with limited developer resources.
Appcelerator Titanium says "Hi. Must be nice to just coast on hype without any product support investment or proven track record."
For anyone else who, like me, didn't realize it - there's a little triangle on the bottom right to let you go through the presentation.
You can also easily navigate it with your cursor keys though.
I think that author is completely right about the part, that React has the only one reactive part — its render function. But I don't see why it makes React bad. I think it is great, fast and easy to use. By the way, virtual-dom is a little bit early to use for production application. For example, if you have some elements in your vdom, that are changing after you render it (i.e. like buttons, embeded posts, etc.), vi…
>For example, if you have some elements in your vdom, that are changing after you render it (i.e. like buttons, embeded posts, etc.), virtual-dom will be totally confused and unpredictable. I can't think of a reason that someone would use react and still bypass it do their own dom modifications.
For anyone else who, like me, didn't realize it - there's a little triangle on the bottom right to let you go through the presentation.
What an awful UI decision. I wouldn't have even noticed it. EDIT: This apparently wasn't intended to be navigated by the general public, as explained by a comment below.
I think that author is completely right about the part, that React has the only one reactive part — its render function. But I don't see why it makes React bad. I think it is great, fast and easy to use. By the way, virtual-dom is a little bit early to use for production application. For example, if you have some elements in your vdom, that are changing after you render it (i.e. like buttons, embeded posts, etc.), vi…
On the one hand, yes, and on the other hand, I have never in practice had this happen when it was not my fault. I've also never had it be my fault unless I fell back on some old jQuery plugin or Google Maps or something that directly manipulates the DOM because I'm trying not to reinvent the wheel.
However, you can deal with these things gracefully by diligently recognizing these instances in which you, for one reason or another, need to directly manipulate the DOM. React's lifecycle methods like `componentDidMount`, `componentWillUpdate`, and `componentWillUnmount` are the place to deal with those kinds of issues.
It definitely takes you out of the React philosophy and forces you to manage your own state carefully. But that's generally confined to a single component, so if you get the component innards right, everything that calls it can be ignorant of the ugly stuff inside.
Unless you're talking about something else entirely that I've just been lucky to never encounter.
Earlier quoted context omitted.
Space seems to work as well. I love it when a page telling you not to use something fails at UX.
It doesn't fail at UX - it's intended to be a presentation manually controlled by the presenter. Just because someone posted a link to Hacker News doesn't mean the author intended for it to be here.