ONLamp.com: Rolling with Ruby on Rails
Popularity Report
![]() |
|||
![]() |
|||
![]() |
|||
![]() |
|||
![]() |
|||
![]() |
URL Tag Cloud
- ruby
- , programming
- , rails
- , rubyonrails
- , tutorial
- , development
- , web
- , webdev
- , tutorials
- , howto
- , ror
- , article
- , design
- , code
- , ruby_on_rails
- , framework
Bookmark History
Saved by 147 people (-44 private), first by anonymouse user on 2006-03-02
- Microzealous on 2009-02-05 - Tags Development
- Cullepm3 on 2008-10-29 - Tags no_tag
- Aalvaradoh on 2008-10-09 - Tags web , tutorial , rubyonrails , ruby , resource , development , article
- Greencactus on 2008-09-03 - Tags Programming , ruby , on , ror , ruby_on_rails , tutorial , rails
- Mgurnett on 2008-05-08 - Tags ruby
Public Sticky notes
Highlighted by denmerc
Highlighted by denmerc
Highlighted by denmerc
Highlighted by denmerc
Highlighted by galonso
Highlighted by djshiow
Highlighted by djshiow
Highlighted by djshiow
Highlighted by djshiow
Highlighted by saltyveruca
What would you think if I told you that you could develop a web application at least ten times faster with Rails than you could with a typical Java framework? You can--without making any sacrifices in the quality of your application! How is this possible?
Part of the answer is in the Ruby programming language. Many things that are very simple to do in Ruby are not even possible in most other languages. Rails takes full advantage of this. The rest of the answer is in two of Rail's guiding principles: less software and convention over configuration.
Less software means you write fewer lines of code to implement your application. Keeping your code small means faster development and fewer bugs, which makes your code easier to understand, maintain, and enhance. Very shortly, you will see how Rails cuts your code burden.
Convention over configuration means an end to verbose XML configuration files--there aren't any in Rails! Instead of configuration files, a Rails application uses a few simple programming conventions that allow it to figure out everything through reflection and discovery. Your application code and your running database already contain everything that Rails needs to know!
Highlighted by saltyveruca
Highlighted by guenter
Rails is an open source Ruby framework for developing database-backed web applications. What's special about that? There are dozens of frameworks out there and most of them have been around much longer than Rails. Why should you care about yet another framework?
What would you think if I told you that you could develop a web application at least ten times faster with Rails than you could with a typical Java framework? You can--without making any sacrifices in the quality of your application! How is this possible?
Part of the answer is in the Ruby programming language. Many things that are very simple to do in Ruby are not even possible in most other languages. Rails takes full advantage of this. The rest of the answer is in two of Rail's guiding principles: less software and convention over configuration.
Less software means you write fewer lines of code to implement your application. Keeping your code small means faster development and fewer bugs, which makes your code easier to understand, maintain, and enhance. Very shortly, you will see how Rails cuts your code burden.
Convention over configuration means an end to verbose XML configuration files--there aren't any in Rails! Instead of configuration files, a Rails application uses a few simple programming conventions that allow it to figure out everything through reflection and discovery. Your application code and your running database already contain everything that Rails needs to know!
Highlighted by arpitjain11
What is Rails?
Rails is an open source Ruby framework for developing database-backed web > applications. What's special about that? There are dozens of frameworks out > there and most of them have been around much longer than Rails. Why should you > care about yet another framework? >
What would you think if I told you that you could develop a web application > at least > ten times faster with Rails than you could with a typical > Java framework? You can-- > without > making any sacrifices in the quality > of your application! How is this possible? >
Part of the answer is in the Ruby programming language. Many things that are > very simple to do in Ruby are not even possible in most other languages. Rails > takes full advantage of this. The rest of the answer is in two of Rail's > guiding principles: > less software > and > convention over > configuration > . >
Less software > means you write fewer lines of code to implement your > application. Keeping your code small means faster development and fewer bugs, > which makes your code easier to understand, maintain, and enhance. Very shortly, you > will see how Rails cuts your code burden. >
Convention over configuration > means an end to verbose XML > configuration files--there aren't any in Rails! Instead of configuration files, > a Rails application uses a few simple programming conventions that allow it to > figure out everything through reflection and discovery. Your application code > and your running database already contain everything that Rails needs to > know! >
Highlighted by arpitjain11
What is Rails? >
Rails is an open source Ruby framework for developing database-backed web > > a pplications. What's special about that? There are dozens of frameworks ou >t > t here and most of them have been around much longer than Rails. Why should yo >u > c are about yet another framework >? >
W hat would you think if I told you that you could develop a web applicatio >n > a t leas >t > t en times faster with Rails than you could with a typica >l > J ava framework? You can- >- > w ithou >t > m aking any sacrifices in the qualit >y > o f your application! How is this possible >? >
P art of the answer is in the Ruby programming language. Many things that ar >e > v ery simple to do in Ruby are not even possible in most other languages. Rail >s > t akes full advantage of this. The rest of the answer is in two of Rail' >s > g uiding principles >: > l ess softwar >e > > and > c onvention over > > c onfiguratio > > > > > >n > . >
Less software > m eans you write fewer lines of code to implement you >r > a pplication. Keeping your code small means faster development and fewer bugs >, > w hich makes your code easier to understand, maintain, and enhance. Very shortly, yo >u > w ill see how Rails cuts your code burden >. >
Convention over configuration > m eans an end to verbose XM >L > c onfiguration files--there aren't any in Rails! Instead of configuration files >, > a Rails application uses a few simple programming conventions that allow it t >o > f igure out everything through reflection and discovery. Your application cod >e > a nd your running database already contain everything that Rails needs t >o > know! >
Highlighted by arpitjain11
Highlighted by khallenb
Highlighted by vivelafrance
Highlighted by akajut
Highlighted by millette
Highlighted by pklausner
Highlighted by parkalewis
Highlighted by tzon02
Highlighted by tzon02
Highlighted by tzon02
Highlighted by yaateehshima


Public Comment
on 2006-07-26 by calebism
on 2006-08-08 by nerdjournal
on 2006-08-18 by omalley
on 2006-10-25 by stumax
on 2006-11-03 by pistos