Link Details

Link 712881 thumbnail
User 478055 avatar

By mitchp
via ruby.dzone.com
Published: Dec 16 2011 / 11:38

One of my favorite subjects is comparing and contrasting tools and frameworks available today. Python and Ruby are probably the big 2 languages right now in web development.
  • 6
  • 3
  • 3451
  • 1150

Comments

Add your comment
User 857907 avatar

Mahmoud Hossam replied ago:

0 votes Vote down Vote up Reply

" As an example, with Django, authentication is built into the framework, there is one Right way to do it. Ruby has no built in authentication, and you can either do it yourself, use Warden, Devise, Sorcery or many other options. Each themselves has good and bad things about it, but they all work well."

Did he just compare a framework to a language?

User 338269 avatar

Miloskov replied ago:

0 votes Vote down Vote up Reply

He means Rails. We know Ruby is all Rails, There are some people that learn Rails and they didnt know they ware using Ruby language rofl. Or people that learn Ruby with Rails.

User 857907 avatar

Mahmoud Hossam replied ago:

0 votes Vote down Vote up Reply

Rails is a framework, Python is a language, comparing a framework to a language is like comparing apples to oranges.

User 338269 avatar

Miloskov replied ago:

0 votes Vote down Vote up Reply

As an example, with Django, authentication is built into the framework, there is one Right way to do it. "RAILS" has no built in authentication, and you can either do it yourself, use Warden, Devise, Sorcery or many other options. Each themselves has good and bad things about it, but they all work well.

Fixed for you maybe he got typo, thats all and calm down bro.

User 959939 avatar

dickeytk replied ago:

0 votes Vote down Vote up Reply

gah I conflate the 2. I did it particularly badly in that section. However, the point I was trying to make is that the philosophy of a language is what you need to keep in mind moreso than the syntax. It's those ideas that end up becoming frameworks and tools that make up what a language is like to work with.

User 296272 avatar

restjohn replied ago:

0 votes Vote down Vote up Reply

This is a well written article. I have a qualm regarding your closing point that delivery of the product is always more important than maintainability. In my experience, the importance of maintainability increases with the age of the software. During the life of a project, code will change, developers will come and go, even the goals of the software may vary. Through all this change, the maintainability of the code becomes a dominant factor in how quickly a team can mutate the code in response to changing requirements. When code is less maintainable but continues to undergo change, the changes become hacks and the release cycle becomes more of a rot cycle. Of course, every project has a varying business context that will dictate the time-to-market of your software, but I generally assign a very high level of importance to maintainable code from the outset.

User 959939 avatar

dickeytk replied ago:

0 votes Vote down Vote up Reply

I think in many contexts you are absolutely right. I work in consumer web, where deliverability is more important than maintainability almost without question.

However, I think in many industries, that wouldn't be the case. 'Launch day' doesn't mean much, it's just having a solid system that's important.

Add your comment


Html tags not supported. Reply is editable for 5 minutes. Use [code lang="java|ruby|sql|css|xml"][/code] to post code snippets.

Voters For This Link (5)



Voters Against This Link (2)



Play Framework
Written by: Ryan Knight
Featured Refcardz: Top Refcardz:
  1. Akka
  2. Design Patterns
  3. OO JS
  4. Cont. Delivery
  5. HTML5 Mobile
  1. Akka
  2. JUnit/EasyMock
  3. Java Performance
  4. REST
  5. Java