Home/ Questions/Q 1040237
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-16T15:11:56+00:00

I’m an experienced C/C++/C#/Objective-C desktop,web, and mobile programmer and I’ve become accustomed to building

  • 0

I’m an experienced C/C++/C#/Objective-C desktop,web, and mobile programmer and I’ve become accustomed to building most of my software from scratch. I’ve built all my websites from the ground up using ASP.NET. I have quite a few ideas for websites that I’d like to test and I’d like to increase the rate at which I can actually build a website. I’m sure I’m unaware of many of the technologies that are commonly used for building out ideas quickly. About a year back, I looked into using the popular CMS called Drupal to see if it would help me speed up development. After two weeks of trying to decipher the structure of the Drupal CMS, along with trying to learn PHP, I found the learning curve to be steep enough to convince me that it would just be faster if I built my website yet again from scratch using ASP.NET MVC. I’m wondering if anyone could suggest any other technologies that are designed for programmers to build websites quicker than my current method of building them from scratch using ASP.NET MVC.

Secondly, I’ve been hearing many entrepreneurs mention Ruby on Rails is what they use to speed up the development of their ideas, so I’m planning to investigate it. Why do I hear more about Ruby on Rails than any other technology? Would you suggest using it to speed up development?

Thanks in advance for all your wisdom!

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    I’ve tried out Ruby on Rails, Django (the Python equivalent of Ruby on Rails) and Drupal. Drupal is nice if you’re just acting as a sysadmin: install the modules you want and use it as-is. But PHP as a programming language is so annoying that I’d hate to use it for something serious.

    Django has some odd quirks but seems to work well. From an MVC perspective, Django calls views “templates” and calls controllers “views”, which is ugly. Also, instead of generating default URL -> controller/action mappings for you the way that Rails does, Django set up routing files by hand before things work. You also have to set up some DJANGO environment variables if you want to run other helper Python code with access to your model objects. Rails also creates and configures a sqlite database by default so that you can start right away, but with Django you have to set it up yourself.

    Rails seems to “just work” in so many ways that I highly recommend it. Ruby is also a pleasant language to work in. Try the simple startup to see what I mean:

    rails foo # Create the foo webapp
cd foo
script/server

    Then browse to http://localhost:3000 to try things out. That page will give you some info about your webapp and point you to the next steps.

    • 0