Why we ditched Rails

Presentation about Deveo's development challenges in Frozen Rails 2012.

Transcript

1. Why we ditched Rails 6 lessons we learned the hard way
2. Jerry Jäppinen GUI Designer @jerryjappinen jerry.jappinen@eficode.com
3. Apps & APIs Collaboration Repo hosting
4. Views shouldn’t be tied to domain objects Rails is logical, UIs are not 1.
5. View’s lifetime is just beginning on page load Preprocessed views won’t cut it 2.
6. HTML, CSS, JS & JSON Technology stack gets out of hand 3.
7. Seriously WTF, look at your smartphone Page refreshes *_* 4.
8. JavaScript can’t be escaped or superceded No options for writing modern UIs 5.
9. Ruby != JavaScript Rails is Ruby 6.
10. No Rails :( For now. =
11. www.deveo.com @deveoteam