3 Reasons Not to Use Ruby

Preview:

DESCRIPTION

I love Ruby, but last year I found myself at the Smithsonian Institution coding in, of all things, PHP & Drupal. And I realized that despite my ambivalence towards those technologies, I had no compelling-enough reason to propose Ruby as an alternative. How did we get to this point? I’ll tell 3 reasons we didn't use Ruby, and reflect on whether these are things we want, or problems we should solve.

Citation preview

3 Reasons Not to Use Ruby

@ultrasaurus

I love Ruby

Bridge Foundry

User Centric Design Agile Development US Government

http://bit.ly/exec-order-open-data

19 museums

9 research centers

23 libraries

15 archives

137Millionspecimens, art works and other treasures...

with over...

136,000 cubic feetof archival material

5M plant specimens

3.7 M without digital records

This is the record (structured data)

Why Ruby?

Flexibility Test Framework

Software Evolution

Why Not Ruby?

#1

CMS

#1

Ruby CMS?

0

300,000

600,000

900,000

1,200,000

Refinery

Comfortable!Mexican Sofa

Browser CMSRadiantAlchemyLocamotive

Drupal 7

Drupal 6

Downloads

Active Installs

0

300,000

600,000

900,000

1,200,000

Refinery

Comfortable!Mexican Sofa

Browser CMSRadiantAlchemyLocamotive

Drupal 7

Drupal 6Ruby CMS?

Active Installs

#2

High Level Components

I can build a blog in 5 minutes!

CODE

#3

#3

Biggest Challenge is not code

So what?

Framework Choice leads to

Language Choice

CMS

CODE

time

100%

0%

CMS CODE

time

100%

0%

BIG

REW

RIT

E

Frameworks are

Patterns for How we Work

Ever notice that the top Ruby CMS options are all Rails apps…?

http://18fblog.tumblr.com/post/85232393363/a-few-notes-on-notalone-gov

A Few Notes on NotAlone.gov

Ecosystem of Components as Important as

the Language Itself

Component Ecosystem?

separate pieces assembled by a developer

OmniAuth

OmniAuth

Bootstrap

OmniAuth

Bootstrap

What we do not automate

we are doomed to repeat.

What will you

make happen?