Software Systems Engineer at Ripio·

I was considering focusing on learning RoR and looking for a work that uses those techs.

After some investigation, I decided to stay with C# .NET:

  • It is more requested on job positions (7 to 1 in my personal searches average).

  • It's been around for longer.

  • it has better documentation and community.

  • One of Ruby advantages (its amazing community gems, that allows to quickly build parts of your systems by merely putting together third party components) gets quite complicated to use and maintain in huge applications, where building and reusing your own components may become a better approach.

  • Rail's front end support is starting to waver.

  • C# .NET code is far easier to understand, debug and maintain. Although certainly not easier to learn from scratch.

  • Though Rails has an excellent programming speed, C# tends to get the upper hand in long term projects.

I would avise to stick to rails when building small projects, and switching to C# for more long term ones.

Opinions are welcome!

READ LESS
11 upvotes·2 comments·143.9K views
John Akhilomen
John Akhilomen
·
December 3rd 2020 at 6:18PM

Staying with C# .NET was one of the best decisions I ever made actually. I use to do alot of Java/J2EE programming before moving to C# 5 years ago. But when I did, I never looked back. With C# it's easier to write clean code and implement a clean architecture when building a system. And don't even get me started on .Net core. Personally, I always believed years ago that Ruby and Php were dead. Fortunately for PHP, Wordpress helps keep it alive.

·
Reply
malekmfs
malekmfs
·
April 14th 2021 at 8:34PM

You can't compare Ruby and C# like that. They are on different layers. You can compare C# only to Java and Ruby to Python.

·
Reply
Avatar of Ing. Alvaro Rodríguez Scelza

Ing. Alvaro Rodríguez Scelza

Software Systems Engineer at Ripio