• Share
  • Email
  • Embed
  • Like
  • Save
  • Private Content
Why not to use Rails? (actually it's when not to use Rails)
 

Why not to use Rails? (actually it's when not to use Rails)

on

  • 705 views

A talk I gave at the

A talk I gave at the

Statistics

Views

Total Views
705
Views on SlideShare
696
Embed Views
9

Actions

Likes
0
Downloads
1
Comments
0

1 Embed 9

http://www.linkedin.com 9

Accessibility

Categories

Upload Details

Uploaded via as Adobe PDF

Usage Rights

© All Rights Reserved

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Processing…
Post Comment
Edit your comment

    Why not to use Rails? (actually it's when not to use Rails) Why not to use Rails? (actually it's when not to use Rails) Presentation Transcript

    • use Rails? hy not to WRails Israel 2012Monday, November 12, 12
    • Arik Fraimovich @arikfr TRuby PodcastMonday, November 12, 12
    • actually... Why use Rails at all?Monday, November 12, 12
    • Monday, November 12, 12
    • • CommunityMonday, November 12, 12
    • • Community • Ruby GemsMonday, November 12, 12
    • • Community • Ruby Gems • SimplicityMonday, November 12, 12
    • • Community • Ruby Gems • Simplicity • Convention over configurationMonday, November 12, 12
    • • Community • Ruby Gems • Simplicity • Convention over configuration • Choices that are made for youMonday, November 12, 12
    • • Community • Ruby Gems • Simplicity • Convention over configuration • Choices that are made for youMonday, November 12, 12
    • Monday, November 12, 12
    • When not to use Rails?Monday, November 12, 12
    • general purpose libraries (gems)Monday, November 12, 12
    • for the simple stuffMonday, November 12, 12
    • for large web application or anything that isn’t a web applicationMonday, November 12, 12
    • “Our tools shape our thinking.” @drnicMonday, November 12, 12
    • Monday, November 12, 12
    • • Everything is sort of global, no need for require • (Usually) no namespacing • Everything in the context of HTTP requestMonday, November 12, 12
    • No need to require?Monday, November 12, 12
    • No need to require? • Sounds nice at the beginningMonday, November 12, 12
    • No need to require? • Sounds nice at the beginning • But then it starts to creep on you and everything becomes sllllowww...Monday, November 12, 12
    • No need to require? • Sounds nice at the beginning • But then it starts to creep on you and everything becomes sllllowww... • Slow boot timeMonday, November 12, 12
    • No need to require? • Sounds nice at the beginning • But then it starts to creep on you and everything becomes sllllowww... • Slow boot time • Slow specsMonday, November 12, 12
    • No need to require? • Sounds nice at the beginning • But then it starts to creep on you and everything becomes sllllowww... • Slow boot time • Slow specs • Slow everythingMonday, November 12, 12
    • Solution? Spork (Zeus?)Monday, November 12, 12
    • Solution? Spork (Zeus?)Monday, November 12, 12
    • The common Rails app.Monday, November 12, 12
    • The Rails app you wantMonday, November 12, 12
    • EnginesMonday, November 12, 12
    • WagonsMonday, November 12, 12
    • What about the everything in “HTTP context”?Monday, November 12, 12
    • Good question.Monday, November 12, 12
    • No good answers* * from me. yet.Monday, November 12, 12
    • Some PointersMonday, November 12, 12
    • Some Pointers • Actor Model - “easy” concurrency. Popular implementation in Ruby: CelluloidMonday, November 12, 12
    • Some Pointers • Actor Model - “easy” concurrency. Popular implementation in Ruby: Celluloid • JRubyMonday, November 12, 12
    • Some Pointers • Actor Model - “easy” concurrency. Popular implementation in Ruby: Celluloid • JRuby • TorqueBoxMonday, November 12, 12
    • Wrap upMonday, November 12, 12
    • Wrap up • Use Rails, but remember there are other things out thereMonday, November 12, 12
    • Wrap up • Use Rails, but remember there are other things out there • Use Rails “carefully”, as your project growsMonday, November 12, 12
    • Wrap up • Use Rails, but remember there are other things out there • Use Rails “carefully”, as your project grows • Don’t forget that not everything is a nailMonday, November 12, 12
    • Wrap up • Use Rails, but remember there are other things out there • Use Rails “carefully”, as your project grows • Don’t forget that not everything is a nail • And most important: keep using Ruby. It’s awesomeMonday, November 12, 12
    • Questions? @arikfrMonday, November 12, 12
    • • Architecture The Lost Years • Wrangling Large Rails Codebases • Hexagonal Rails • Celluloid • JRuby • TorqueBox • About concurrency and the GIL • Images taken shamelessly from Google.Monday, November 12, 12