Y'all are a bunch of wankers!

Why are companies still use Ruby/Rail???

I saw many job ads asking for this skill. I shudder.
Permalink DrNo 
May 11th, 2018 10:11am
Fanboys/dickheads probably took their companies down that path 10 years ago because they thought it would look good on their CVs. The companies are now stuck with it.
Permalink Grumpy Old Git 
May 11th, 2018 11:56am
It was once very popular.  They probably need peoole to support their legacy trash.

The hipsters seem to be using node.js now.
Permalink FSK 
May 11th, 2018 11:57am
Git - I was at a startuo that failed because they decided to rewrite their product in Rails.
Permalink FSK 
May 11th, 2018 11:58am
*still using - want to correct my grammar before the grammar police arrests me.
Permalink DrNo 
May 11th, 2018 12:04pm
Yes. Using Ruby/Rails was the big mistake. It was pushed heavily by David Heinemeier Hansson at Basecamp.
Permalink DrNo 
May 11th, 2018 12:05pm
Copied from Quora:

First of all, the Ruby community is strong and not going anywhere anytime soon. What many may perceive as "where did they go?" is primarily because many of the original evangelists are not here anymore. Let's list some of the top ones:
Chad Fowler, once one of the co-founders of the USA Ruby community and co-founder of the original Rubyconf since faded away since he moved to Living Social and then moved away to Wunderlist. He is probably very busy with this successful german startup.
Ryan Bates, once the primary source of screencasts for Ruby and Rails, he took time off and never returned. His duties was later picked up by others such as GoRails - Ruby on Rails screencasts for Web Developers - GoRails
Gregg Pollack, once the "Ruby vs X" videos (parodying the old Mac vs PC commercials from Apple), founder of EnvyLabs, Envycasts, Ruby5, Ruby Heroes, and Code School, is probably busy with his business since Code School was acquired by Pluralsight.
Geoffrey Grosenbach, also once synonymous with quality screencasts also sold to Pluralsight and as far as I know is taking time off.
Yehuda Katz and Carl Lerche, once strong evangelists for Rails-alternative Merb and then strong developers of the Rails 3.0 merge, left to focus on their own startup Skylight under the Tilde services company. They are heavily invested in their own javascript framework Ember.js
José Valim, also once Rails 3.0 full time developers went away to implement his own language in the form of Elixir.
Matt Aimonetti, also once Merb evangelist, left after the Rails 3.0 to Sony and he is more interested in Go Lang these days.
Ilya Grigorik, once known as Igvita and one of the best technical writers I've seen sold his startup PostRank to Google and became Web performance engineer and W3C co-chair of web performance and he's been doing research on the Web in general.
Evan Phoenix, once Rubinius creator and evangelist, also created Puma and he is still maintaining it, he is also a RubyCentral member and RubyConf organizer if I am not mistaken, but he is less vocal about his work nowadays.
Mitchell Hashimoto, from Vagrant fame, moved to Go to do heavy work on Docker and tools around it to improve the life of devops.
Steve Klabnik, philosopher coder of the new crop, he keeps back and forth between Ruby and Rust although I think he is more involved in writing the Rust book nowadays.
There are several other recognizable names that "vanished" in the last 10 years. But many are still there doing heavy work and many new faces emerged. It's only natural.
You should follow people such as:
Aaron Patterson, aka Tenderlove, who was recently hired by GitHub. He is Ruby and Rails committer and he is still doing terrific work.
Richard Schneeman, at Heroku he is doing interesting work as well, in particular he helped solve a Sprockets performance problem recently.
Rafael França, former Plataformatec engineer and currently at Shopify, he is still doing a lot of maintenance of the Rails codebase.
Pat Shaughnessy, Michael Hartl and others are still doing a lot of writing (books)
Peter Cooper expanded his Ruby Inside domain into RubyFlow and many other newsletters for other languages. A most follow.
The Japanese committers never stood up as being very vocal, they silently do the heavy lifting so we can do our work. Follow people such as Koichi Sasada, now at Heroku.
Charles Nutter is still doing JRuby development and he is nowhere near done.
Brian Shirai took the Rubinius mantle and is doing some niche work down there too.
Dr. Nic is still doing a lot of under the covers work in Cloud Foundry if I am not mistaken.
Laurent Sansonetti is still doing great with RubyMotion since he left Apple, his technology allows you to write Ruby for both Android and iOS apps, a must try!
Tobias Lütke is also still going on with his successful Shopify, hosted e-commerce platform. It's possibly the oldest Rails app besides DHH's and the fact that it's still going on strong after almost 10 years is a great achievement.
Satish Talim, decade old comrade from Ruby Tutorial - Learn Ruby is training beginners to this day. Hundreds of Ruby developers got started because of this relentless passion to teach. Nowadays he is also teaching Go, so you should definitely follow him.
And, of course, there are more important people to list, so this is but a very short list out of the top of my head right now, not a comprehensive list.
What happened is that many startups worked out nicely, many kudos to Peepcode, Code School, PostRank, Github, Heroku, etc And many developers either moved to more managerial roles and have less time to invest in public speaking or open source, but they are there. We now have very interesting and complex platforms from Gitlab, to Spree, to Discourse and a plethora of tools available in a very mature ecosystem. Rails is approaching version 5.0-stable and DHH himself is not near giving up.
So, "where did everybody go?" this is part of the answer. We are not shying away and we are not ignoring the current trends in technology. Rubyists are not religious people and we go back and forth, we will use Elixir, we will use Go, we will use Javascript, and we will take the Ruby way with use wherever we go.
Activity over Github will naturally be less accelerated because most of what needed to be built is already built. The advantage is that any Ruby developer will be able to find good, stable, battle tested and reliable Rubygems that solve many of our daily problems. The half-assed stuff is mostly gone, the packages that survived are well maintained and ready to use. You should go to Ruby Toolbox, for example, pick your option and you're ready to go. We ironed out techniques, stacks, libraries, patterns and guidelines. Everybody knows what to do in the best way possible.
Other flourishing ecosystems are taking our lead in one way or the other. The Ruby ecosystem is strong right now, go ahead and use it. Of course, there are rough edges here and there, specially in niche use cases, but for the most part we solved 90% of everybody's use cases already, no need to reinvent the wheel.
Permalink DrNo 
May 11th, 2018 12:08pm
Rails is plural.
Permalink Grammer Nazi 
May 11th, 2018 12:08pm
Rails is just so non-standard. Ruby is this weird language invented in Japan. RoR is a stack that doesn't have anything in common with anything normal like PHP or Python or Perl.

Rails seems like the Borland Delphi of web apps. Quick results but no general acceptance by industry.
Permalink Trumpier than Trump 
May 11th, 2018 12:34pm
I understand why Rails is considered an outlier framework.

But I don't get it why people think Ruby is any weirder than Python.
Permalink John 
May 11th, 2018 12:50pm
One of our software suppliers recently switched to delivering with Ruby.  So recently I've been learning ruby.

This is after they switched from Java to Perl, Perl to Python, and now Python to Ruby.

It's been an interesting path.  I find Ruby, with its 'begin...end', white-space is flexible (unlike python), a LOT of perl-isms, to be Python done better.

Like Perl, it's SO freaking flexible there's dozens of ways to do anything, some of them so terse they can be hard to maintain, hard to error-check, hard to validate.  But with a little discipline in how you write your code, you can get around that.  So it's not bad.

But I agree it seems Javascript is the current technology for the web.
Permalink SaveTheHubble 
May 11th, 2018 12:59pm
LOL. I feel for you Hubble. Diamonds are girl's best friends. Ruby is Hubble's best friend! That gonna sucks so bad.
Permalink DrNo 
May 11th, 2018 1:18pm
Python has mainstream uses.  pandas is very good for dealing with large csv files.

Coming from PHP, Python wasn't that hard to pick up.
Permalink Send private email FSK 
May 11th, 2018 6:27pm

This topic is archived. No further replies will be accepted.

Other topics: May, 2018 Other topics: May, 2018 Recent topics Recent topics