[deleted]
Is Rails still relevant in 2018?
281–290 of 346 posts
Re: Is Rails still relevant in 2018?
#282Earlier quoted context omitted.
> These days if your chosen language doesn't have things like strong typing, interfaces, good debugging tools, a good compiler, etc, then you should definitely be asking yourself if it's the right tool for the job. All of these things existed long before Ruby on Rails gained in popularity. Unless the popularity of Rails, Python, PHP, and Javascript was all just collective insanity, dynamic languages do offer benefits…
Unless the popularity of Rails, Python, PHP, and Javascript was all just collective insanity, dynamic languages do offer benefits in some circumstances over languages with stronger type guarantees. The benefit they offer is fewer checks so you can deploy things faster. It's the same benefit you can get if you take your car to a mechanic who doesn't bother to check the wheels are attached properly after they've change…
But one can add checks after the design/features settle; it's not all or nothing. Using the mechanic analogy, if you are requesting a custom car, the mechanic can shape the look and feel first, and then verify everything once you made up your mind.
Most CRUD (such as tracking applications) is just marshaling attributes around and about, not really doing much math on them. Forced type checks can be repetitive busy work and hogs screen real-estate.
Re: Is Rails still relevant in 2018?
#283One thing you'll run into with rails in 2018 for web development is it's going to be hard to find developers and only getting harder by the day. Rails developers are aging. They are no longer your 20 year old hipsters, that stereotype has long since gone, they have families now and boy are they EXPENSIVE. React is what people new to web development are LEARNING and that's all you need to care about. You can get react…
Why would you compare a backend with a frontend framework? Are you implying Node on the backend? React developers are dependent on a backend, be it Node, a managed solution like Firebase, or Rails. I don't think it's a matter of React instead of Rails, but rather, Rails developers are learning they must add frontend skills, and React seems the safe bet. Many are probably shifting to Node, given the idea (true or not)…
I’m talking about your traditional rails app with classic templates views and controllers (no SPA) vs. react + node (express) stack.
Re: Is Rails still relevant in 2018?
#284Earlier quoted context omitted.
Wow. We really need to fix our install page if people are reaching this conclusion. Hey, Nim dev here. I can assure you that Windows is incredibly well supported by Nim. > a) No mention of MSVC support as a compiler option https://nim-lang.org/faq.html#how-do-i-use-a-different-c-com... > b) Installer does not install the complete required language runtime, and the end user must hunt the missing DLL:s by themselves. T…
Hey! Cool to read you response. My initial comment may have been a bit uncharitable, and I'm sorry - I chose clear communication instead of overt politeness. I might not resemble the core audience of the language in any way :) I based my response to the first page mentioning windows install: https://nim-lang.org/install_windows.html This is the first page I end up from both https://nim-lang.org and Google. My instinc…
Thank you! I'll take your feedback on board :)
Re: Is Rails still relevant in 2018?
#285Earlier quoted context omitted.
To be fair the technology stack is almost irrelevant when you are starting a company. write it in perl, python, rails, hell write it in old school cgi and use c++. It all comes down to how many sales did you make today. The clients will rarely care what language was used behind the scenes.
I refuse to write Perl. If enough people feel the same way, Perl is not a good choice.
Or you are not the right choice to hire...
Re: Is Rails still relevant in 2018?
#286The article is good but it completely ignores the rise of Python, which is the main thing challenging Ruby in 2018. Elixir doesn't really compete with Ruby. It may be technically superior, but will never supplant Ruby because it's just not very accessible, and the timing was bad. So it attracts different sorts of people. Same with Clojure, although they really, really tried. Javascript is the opposite; it gained and…
Python is definitely becoming the language of ML stuff, largely thanks to Python being popular as a replacement for Java in academia. If you look at the general trend, python is on the rise: https://trends.google.com/trends/explore?date=all&geo=US&q=%.... If you look at web frameworks though, you can see that Python web development has been stagnant since 2012: https://trends.google.com/trends/explore?date=all&geo=US&q=%....
Re: Is Rails still relevant in 2018?
#287Rails really nailed the problems of web development as it was 10 years ago by (rightly) pointing out that 97.2% of web projects were all about making an application server talk nicely to a relational database and then generating a front end that reflected the data model and that had javascript that Just Worked (everywhere). Web dev is in a different place now. Developers don't generally install and maintain applicati…
> Just the idea that a Danish web consultant could hack together something that became popular and which then allowed him to literally retire and become a racing driver before he hit 30 should inspire us all. While being successful in all those aspects, DHH is still very active in the development of the framework. He is currently also the CTO at Basecamp. Not really what I would consider being retired.
Also he didn't get rich at least to begin with off Rails as such, which is free open source but off Basecamp which as he is fond of pointing out charges customers money in the old fashioned way. (As opposed to raising VC.)
Re: Is Rails still relevant in 2018?
#288The article is good but it completely ignores the rise of Python, which is the main thing challenging Ruby in 2018. Elixir doesn't really compete with Ruby. It may be technically superior, but will never supplant Ruby because it's just not very accessible, and the timing was bad. So it attracts different sorts of people. Same with Clojure, although they really, really tried. Javascript is the opposite; it gained and…
Python is definitely becoming the language of ML stuff, largely thanks to Python being popular as a replacement for Java in academia. If you look at the general trend, python is on the rise: https://trends.google.com/trends/explore?date=all&geo=US&q=%... . If you look at web frameworks though, you can see that Python web development has been stagnant since 2012: https://trends.google.com/trends/explore?date=all&geo=U…
That said, it looks like Rails interest is as stagnant as Python web framework interest, tracking almost exactly with interest in them, just more popular: https://trends.google.com/trends/explore?geo=US&q=%2Fm%2F06y...
Re: Is Rails still relevant in 2018?
#289I work in a small full-stack JS/TS shop, and we've inherited a RoR application lately.
I see a lot of criticism against the Javascript ecosystem. Let me tell you why I prefer working in Javascript rather than with RoR.
It all boils down to the magic Rails advocates rave about, which is precisely what made my life a nightmare while working on that Rails project. Conventions over configuration is fine when you know those conventions. When all you have to do is work on the frontend part and rebuild an app, then you don't really care all that much about what an asset pipeline might be, or how you're supposed to use it. All those abstractions slow me down. At the end of the day, your run-of-the-mill CRUD apps are all structured kind of the same, and calling a cat a cat instead of inventing non-obvious abstractions is detrimental to speed of dev.
I prefer having `package.json` explicitly listing all the commands I might possibly need than having to memorize what does what with Rails. We've had absolute noobs work on both JS and Rails project and they seem to move much faster and be stuck less on the JS project than with the magic Rails provides. The fact that JS is more imperative helps linking parts of the source code intuitively, compared to Rails having standard classes and hooks and whatnot.
I'm very grateful for what Rails brought to Webdev in general, but I do think that monolithic framework are on their way out. I kind of appreciate being able to follow non-smart code when things go south, and being able to understand what is wrong by just reading the code. I've spent waaay too much time skimming through outdated documentation pages about things that were so clever that they were changed in ulterior versions.
I had the same problems when dealing with Symfony (which still angers me to this day), or Angular.js, or just anything that pretends to know better than me how I should write code. It's kind of a recurring pattern with frameworks that makes me increasingly wary of all of them.
Working with much smaller libraries that you can hope to grasp fully has proven to be much less frustrating personally.
Another advantage is that I can write code once for both the frontend and the backend, which helps me move a lot faster than writing the code + tests in 2 languages.
I know this is not a proof by any means, but I felt that having the point of view of a non-believer would be interesting to you guys.
Re: Is Rails still relevant in 2018?
#290Earlier quoted context omitted.
Why would you compare a backend with a frontend framework? Are you implying Node on the backend? React developers are dependent on a backend, be it Node, a managed solution like Firebase, or Rails. I don't think it's a matter of React instead of Rails, but rather, Rails developers are learning they must add frontend skills, and React seems the safe bet. Many are probably shifting to Node, given the idea (true or not)…
I’m talking about your traditional rails app with classic templates views and controllers (no SPA) vs. react + node (express) stack.
Guess I was correct about the unspoken assumption :-)
Keep in mind there's no real React default. You can pair React with a Rails backend pretty easily (or Elixir or .NET or ColdFusion or PHP or ....) It's really just a matter of what you have in place or what your developers are already competent in.