6. web development now
• open-source technologies and tools
• server-side frameworks
• javascript libraries
• shorter development cycles
7. with Rails you focus on
• creating functionality, not creating code
8. Rails is...
• Rails is opinionated
• “If you try to design for the 20 percent of your
target audience who are power users, your design
may be not usable by the other 80 percent of
users”.
• if one feature satisfy 20% of your customers - it’s
not worth implementing
• convention over configurations
10. Code
• the less code you write, the more
maintainable and flexible your app is
• you don’t have to ship your product to
your customers - show it, get feedback,
make it better, deploy a new version, get
feedback...
11. most of the things are
done for you.
• routing
• database
• MVC
• data, time zones
• CSRF attacks
• ...and many more.
12. developer’s tools for...
• deployment
• testing
• maintaining code
• monitoring your production application
18. community support
• blogs, wiki, railscasts, podcasts, e-books,
traditional books, irc channels, discussion
boards...
• it’s a great thing. really.
19. The Rails Myths: Rails
• ...is hard to deploy
• ...is hard because of ruby
• ...only speaks english
20. Rails is hard to deploy
• Phusion Passenger
• hosting Rails in Poland? no longer a pain in
the ...arm
21. Rails is hard because of
Ruby
• just try it yourself.
• http://tryruby.hobix.com
• it takes as much time as it would to learn a
framework in language that you already
know.
• and then things go faster. and they are
easier. and prettier. and better. believe me.
