101–110 of 131 posts
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.
I recently finished building a small-ish web app for a major federal Government customer in react.js. They are very happy with responsiveness and quality of the product. I'm very happy with how easy and cost-effective it was to build. To get an idea of the size of the app, it has about 20 components. However, some of the components could (and probably should) be broken down. My hunch is that with refactoring the fina…
What did you use to manage state, data flow, communication to servers, etc?
Wow. This dude got really hung-up on the name 'React' (assuming that had to do with reactive programming). His summary of 'React sucks at reactive programming' is ... true? It also kind of misses the point. The React team clearly states their design goals here: https://facebook.github.io/react/ ... and they have nothing to do with reactive programming.
How that data gets into the components is your responsibility; you can easily use something like Baconjs/RxJS to do this.
Earlier quoted context omitted.
Sure, except React easily has the largest community yet (with these types of frameworks) so the argument doesn't really stand for other ones. There has to be really good to reasons to switch to something else completely, and really good reasons not to build on top of React. It's definitely important to look at criticisms, but honestly, these aren't very good ones. It would have been easy to build his library on top o…
Can you explain what you mean by "these types of frameworks" - do you mean the lighter approach that React takes with purely dominating the view and leaving the rest to the developer?
I recently finished building a small-ish web app for a major federal Government customer in react.js. They are very happy with responsiveness and quality of the product. I'm very happy with how easy and cost-effective it was to build. To get an idea of the size of the app, it has about 20 components. However, some of the components could (and probably should) be broken down. My hunch is that with refactoring the fina…
As is covered ad naseum else where, ReactJS is just a way to do Views. What did you use to manage state, data flow, communication to servers, etc?
I recently finished building a small-ish web app for a major federal Government customer in react.js. They are very happy with responsiveness and quality of the product. I'm very happy with how easy and cost-effective it was to build. To get an idea of the size of the app, it has about 20 components. However, some of the components could (and probably should) be broken down. My hunch is that with refactoring the fina…
I recently finished building a small-ish web app for a major federal Government customer in react.js. They are very happy with responsiveness and quality of the product. I'm very happy with how easy and cost-effective it was to build. To get an idea of the size of the app, it has about 20 components. However, some of the components could (and probably should) be broken down. My hunch is that with refactoring the fina…
As is covered ad naseum else where, ReactJS is just a way to do Views. What did you use to manage state, data flow, communication to servers, etc?
Earlier quoted context omitted.
As is covered ad naseum else where, ReactJS is just a way to do Views. What did you use to manage state, data flow, communication to servers, etc?
You can actually do a lot of that stuff with JavaScript, it turns out.
React really doesn't give you any way to handle communication between components besides going downwards, which is fine because that solves a lot of problems. You can very easily implement his 'subscribe' scenario in React. In fact, in 0.14 they are planning on having observe[0] to help you do just this. Now, for my little plug. I've been working on Reapp since launch building a couple real-world apps and I agree tha…
Regarding the page's "poor UI usability" without obvious navigation buttons: I'm guessing the page is intended for the author's use in live presentations (like MS PowerPoint) and is not meant to be a general purpose landing page. The author used it that way here: https://www.youtube.com/watch?v=9QObt0SGriI (I haven't seen the whole presentation so I can't comment if it's worthwhile to watch.)