This document discusses the history and essentials of developing web applications. It covers how microframeworks like Sinatra and full-stack frameworks like Rails evolved from earlier technologies. Padrino is positioned as extending Sinatra by adding features like routing helpers and administration capabilities while maintaining a focus on being compact and portable. Rails influenced later frameworks but sometimes takes a detour, while Padrino and Sinatra strive for a minimal approach without unnecessary complexity.
3. WORKS
Padrino::Validation::HTML5
Add supports HTML5 form validations to Padrino
github.com/aereal/padrino-validation-html5
Hated
mocking server which can be utilized for Hatena Diary
github.com/aereal/hated
4. TABLE OF CONTENTS
The essentials of developing a Web Application
The History of Web Application Frameworks
Padrino and Sinatra
Padrino and Rails
Padrino and Others
29. PADRINO IS BUFFET
Routing (Named, Multiple Format)
Helpers
Logger
Admin Apps (like Django)
Reloader (It’s smart!)
see also: www.padrinorb.com/#introduction
30. PADRINO IS FXXKIN’ SHIT?
Extending Sinatra through Public / Safe API
but Padrino::Routing is like a abyss ...
use (Rack Middleware)
register (Sinatra Extension)
37. PADRINO AND RAILS
Rails is full-stack
Padrino can be full-stack
This means you can use Padrino as not full-stack
38. RAILS IS THE INNOVATOR
Discovered many important things
Spirit of DRY, or CoC
ActiveRecord, ActiveSupport, etc.
Sometimes it makes a detour
The innovation involves pains
44. CONCLUSIONS
Padrino is on the Sinatra’s World
Rails’ heritages are behind
Padrino, Sinatra, and Rails should be all in harmony
45. SEE ALSO
Padrino Official Web (www.padrinorb.com)
Padrino Official Web (ja) (jp.padrinorb.com)
Padrino on GitHub (github.com/padrino/padrino-
framework)
Padrino Recipes (github.com/padrino/padrino-recipes)
Sinatra The Book (sinatra-book.gittr.com)