At Notch8 <http://www.notch8.com/>, we've been using React more and more over the last year. It's become our defacto JS framework now.
We're doing so much of it as consultants that LEARN <https://www.learnacademy.org/> (Notch8's sister company) is now offering: A full time React/Node version of our bootcamp: https://www.learnacademy.org/javascript which starts March 13th AND a weekend program for developers of any level who want to learn React: https://www.learnacademy.org/react-accelerated It's 24 hours of coding in one weekend. Friday night 5-9pm, Sat and Sun 9-7pm and we provide all your meals! Designed for developers looking to level up their skills and get a leg up in the industry, you'll LEARN introductory through advanced React topics. Training includes extensive workshop sessions with hands-on help from our experienced developer-trainers,building React components, and shipping real, production ready code. We'll go over common pitfalls and prescribe an end to end stack, while showing you which pieces you might want to swap out. Anyone with any questions don’t hesitate to hit me up off list. Rob [email protected] Schedule a tour of LEARN <https://app.hubspot.com/meetings/learn-academy/learn-tour> On Wed, Feb 15, 2017 at 1:37 PM Alex Escalante <[email protected]> wrote: > BTW, you can read about my experience using React in this Medium post I > wrote: > > > https://medium.com/audelabs/notes-from-my-first-react-redux-project-3f799beeb140 > > Alex Escalante > > Web & Mobile Development For Hire > http://audelabs.com > > On Wed, Feb 15, 2017 at 12:23 PM, Alex Escalante <[email protected] > > wrote: > > I just finished my first React project. Ir was a front-end for several > micro-services, some of them written in Rails. I liked React a lot. > Compared to Angular, is minimal and straightforward. I had some rough days > when understanding how to get Redux into the mix, but the fact that React > is only one library and you can couple it with whatever else you need gives > you a lot of flexibility. > > There are several ways to get it working with Rails. If you're going for a > SPA, I would recommend using Webpack and not the asset pipeline. Build your > assets this way and just serve them. Use Rails as a REST back end only. > > If you want to get the best performance at the expense of some complexity, > do not serve it from Rails itself, but from NGINX. You could go as far as > using one Docker image for this and another for your Rails app. > > Saludos, > > > Alex Escalante > > Web & Mobile Development For Hire > http://audelabs.com > > On Wed, Feb 15, 2017 at 12:02 PM, Ian Young <[email protected]> wrote: > > Given that I'm writing this while taking a break from introducing React > into one of my current projects, I guess the answer is "a fair bit" 🙂 > > I have a sort of counter-question (that hopefully won't hijack Adam's > thread too much): how are those of you who have been maintaining complex > React apps for some time feeling about it? There's a lot of good things > about the framework, but I do worry about how quickly the complexity > ratchets up. *React itself wasn't too bad once we did the tutorials, but > then of course we hit the limits of state management, so let's go with > Redux. Oops, now forms are really hard to do, guess we better add > redux-form. Crap, our URLs are a mess, add react-router. I wonder if the > new developer has figured out what "action creators" are yet. Hmm, and > someone should probably tell them that we're no longer using state for > anything, everything goes in props now. Ignore state, pretend like it > doesn't exist. Yes, I know our old code still uses it, but pretend, ok? > Where did all these props get set? Well, you know how to use a debugger, > right?* > > I guess what I'm saying is if I were starting a new project now, I'd still > try to build most of my interface in normal old Rails, and save React for > the places where it's a true value-add. I worry that going all-in on React > right now is committing to a level of code complexity that might become an > albatross down the road. But this gives me another chance to say something > nice about React, which is that it's very possible to use it just as much > as you need, and I appreciate that design philosophy. > > > On Tue, Feb 14, 2017, at 04:20 PM, Adam + Cuppy wrote: > > We started our company primarily in the Ruby on Rails space, however, > we're finding that a good 50 to 60% of our consulting work is integrating > React.js into Rails applications (as opposed to server side views and/or > Turbolinks). > > So, I'm curious how many of your organizations are utilizing React (or > some form of front end framework) for your front and architecture? > > Adam Cuppy, Zeal > > -- > :: *Adam Cuppy* > :: 866.858.5988 ext. 101 <(866)%20858-5988> > :: 541.660.3681 <(541)%20660-3681> > :: https://linkedin.com/in/adamcuppy > > > -- > -- > SD Ruby mailing list > [email protected] > http://groups.google.com/group/sdruby > --- > You received this message because you are subscribed to the Google Groups > "SD Ruby" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > For more options, visit https://groups.google.com/d/optout. > > > -- > -- > SD Ruby mailing list > [email protected] > http://groups.google.com/group/sdruby > --- > You received this message because you are subscribed to the Google Groups > "SD Ruby" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > For more options, visit https://groups.google.com/d/optout. > > > > -- > -- > SD Ruby mailing list > [email protected] > http://groups.google.com/group/sdruby > --- > You received this message because you are subscribed to the Google Groups > "SD Ruby" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > For more options, visit https://groups.google.com/d/optout. > -- -- SD Ruby mailing list [email protected] http://groups.google.com/group/sdruby --- You received this message because you are subscribed to the Google Groups "SD Ruby" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
