Sinisterly
"Why I wouldn't use Rails for a new company" - Printable Version

+- Sinisterly (https://sinister.li)
+-- Forum: Coding (https://sinister.li/Forum-Coding)
+--- Forum: Coding (https://sinister.li/Forum-Coding--71)
+--- Thread: "Why I wouldn't use Rails for a new company" (/Thread-Why-I-wouldn-t-use-Rails-for-a-new-company)



"Why I wouldn't use Rails for a new company" - Oxyrus - 09-18-2015

While browsing Reddit I found this link which shows an interesting perspective, even with myself being a Rails developer.

http://blog.jaredfriedman.com/2015/09/15/why-i-wouldnt-use-rails-for-a-new-company/


RE: "Why I wouldn't use Rails for a new company" - Man - 09-18-2015

This was very boring to read :noh:


RE: "Why I wouldn't use Rails for a new company" - Oxyrus - 09-18-2015

(09-18-2015, 07:33 PM)Man Wrote: This was very boring to read :noh:

It was pretty much a lot of statistics.


RE: "Why I wouldn't use Rails for a new company" - Ami - 09-18-2015

Was actually quite interesting imo, is it still worth it learning ruby/ruby on rails?
I was planning to do so but I'm not so sure now.


RE: "Why I wouldn't use Rails for a new company" - Oxyrus - 09-18-2015

(09-18-2015, 08:38 PM)Ami Wrote: Was actually quite interesting imo, is it still worth it learning ruby/ruby on rails?
I was planning to do so but I'm not so sure now.

Ruby is still a good language to learn and it's well paid, however, it will be more difficult to get a job as a Ruby developer than a JavaScript developer, because it has increased its popularity incredible since the creation of Node.js.

Personally I will finish learning Ruby on Rails this year, and the next I will start learning more about JavaScript.