Rails developers, ie web developers having appetite for nice, industrialization ready technologies, may prefer Ember...
Rails developers should learn React
11–20 of 57 posts
Re: Rails developers should learn React
#12I think I must have some sort of strange default wiring in my brain. I've developed code for over 30 years using many different languages, but when I tried to get into Rails about 10 years ago, I just couldn't get my head around it. Nothing seemed to click and go into place for me. I ended up using Ruby, but via a Sinatra based framework called Padrino. It just seemed to make more sense to me. The same thing more rec…
Sounds like your sweet spot is more towards the library end of library/'light weight framework' vs the 'full blown framework' spectrum. I don't believe it has anything to do with age.
I agree. I should have about the same age of cyberferret and I won't do anything serious with sinatra or padrino. Too much work to do. I don't have the time for that and my customers don't have the money. I wrote web apps from scratch in C (not ++) and Perl in the 90s but I don't want to reinvent the wheel every time, and after 10 years and many developers Rails is a much better wheel than anything I can build myself. Replace Rails with any other comparable framework, even if any other framework I've seen requires to do more work.
Re: Rails developers should learn React
#13I think I must have some sort of strange default wiring in my brain. I've developed code for over 30 years using many different languages, but when I tried to get into Rails about 10 years ago, I just couldn't get my head around it. Nothing seemed to click and go into place for me. I ended up using Ruby, but via a Sinatra based framework called Padrino. It just seemed to make more sense to me. The same thing more rec…
I'm not sure if I'm "young" in this instance, but I'm 31 and have been coding since I was ~15 and I had the same feeling. "An ill fitting jacket" is a nice way to describe it - I can't put my finger on exactly what feels wrong but a lot of things that "magically" happen bother me.
Actually for me, React fitted me well as a jacket! Until a friend asked me why there was and advantage to spend an extra minute taking on and off that jacket instead of using a simpler jacket(vanillajs) that fitted just as well but that I could take on and off in seconds.
My conclusion today is that the massive hype around React, Angular and so on, is a similar story as The Emperor's new clothes.
Re: Rails developers should learn React
#14I think this could be right but does one person can really handle both the backend and the frontend projects when the frontend becomes a first class project from day 1 instead of a kind of afterthought? In other words: a single developer can start a Rails+jQuery sugar web site in N days. Where he would be with Rails(API)+React after those N days?
Another question. I checked those rails+react gems. The pro is that they put everything inside the Rails project. The cons is exactly the same. Even in the case the same person is doing both jobs, shouldn't we acknowledge that they are two separate projects and work on them separately?
Re: Rails developers should learn React
#15I think I must have some sort of strange default wiring in my brain. I've developed code for over 30 years using many different languages, but when I tried to get into Rails about 10 years ago, I just couldn't get my head around it. Nothing seemed to click and go into place for me. I ended up using Ruby, but via a Sinatra based framework called Padrino. It just seemed to make more sense to me. The same thing more rec…
I don't think it is easy to dabble in React starting at zero knowledge of all these frameworks. Vue is just accessible and familiar enough to be more approachable at first. When buiding an internal app I took a long hard look at React, but ended up with Vue. I had previously used Angular 1.x.
I know I see this said a lot but the comprehensibility of these frameworks and tooling is borderline impossible to deal with for dabblers. Docs break almost instantly (Angular 2.x). It is hard to manage the number of small ever changing tools, even when you understand the principles.
I think if you took someone with good knowledge of C and good knowledge of Javascript (NOT web), just the base languages it would be easier getting into systems programming!
Re: Rails developers should learn React
#16TL;DR It will make you more money. There are many ways to integrate React with Rails. To get started do the React tutorial and buy my book.
Re: Rails developers should learn React
#17I think I must have some sort of strange default wiring in my brain. I've developed code for over 30 years using many different languages, but when I tried to get into Rails about 10 years ago, I just couldn't get my head around it. Nothing seemed to click and go into place for me. I ended up using Ruby, but via a Sinatra based framework called Padrino. It just seemed to make more sense to me. The same thing more rec…
I don't think it is easy to dabble in React starting at zero knowledge of all these frameworks. Vue is just accessible and familiar enough to be more approachable at first. When buiding an internal app I took a long hard look at React, but ended up with Vue. I had previously used Angular 1.x. I know I see this said a lot but the comprehensibility of these frameworks and tooling is borderline impossible to deal with f…
I should clarify, that my definition of 'dabbling' is usually to build an actual app with it. I will usually try and build an app that I have already done in another language, just to get familiar with the new language oddities etc.
Funny that you mentioned AngularJS - I built quite a few apps using the Ionic Framework a couple of years back, and that is (was) built upon Angular 1. I found Angular quite easy to pick up and run with. React, not so much.
But its all OK. I am sure React is a great framework and all, just not my taste...
Re: Rails developers should learn React
#18I think I must have some sort of strange default wiring in my brain. I've developed code for over 30 years using many different languages, but when I tried to get into Rails about 10 years ago, I just couldn't get my head around it. Nothing seemed to click and go into place for me. I ended up using Ruby, but via a Sinatra based framework called Padrino. It just seemed to make more sense to me. The same thing more rec…
Rails is, by design, a very opinionated tool. The focus on establishing sensible defaults as a convention is great if you can work at least somewhat within those conventions, but it can become increasingly annoying if you regularly bypass the defaults.
The goal is to make development easier, but you probably won't gain those benefits if your definition of "sensible defaults" isn't compatible with the choices made by Rails. Sinatra is a very different approach, which may work better if you want minimal library that doesn't involve a set of design conventions. Both Rails and Sinatra are useful tools; use whichever is a better fit for your needs.
Re: Rails developers should learn React
#19Honest question, is it really here to stay? What's different between React today and Backbone 4 years ago or Angular 2 years ago? Does it solve all the problems of the predecessors? People are already starting to talk about Vue like it's the new messiah.
It is sort of like Go vs Rust in terms of learning cost. Clearly, based on React's popularity the cost is worth it to many. Vue has really nice docs and is more approachable. Not a messiah but for many projects it is a great choice.
Re: Rails developers should learn React
#20 developers should learn
X - What you know
Y - Technology du jour