Sinatra Book
sinatra-book.gittr.com
Sinatra Book
1–10 of 13 posts
Re: Sinatra Book
#2I must admit some general annoyance at the recent trend in labeling 20-page web-only how-tos "books".
Though, given that the Sinatra source itself is under 2k lines, were it a real book, it would quickly be much longer than the source itself. :-)
Re: Sinatra Book
#3I must admit some general annoyance at the recent trend in labeling 20-page web-only how-tos "books". Though, given that the Sinatra source itself is under 2k lines, were it a real book, it would quickly be much longer than the source itself. :-)
Measuring programming (books) progress by lines of code (lines of text) is like measuring aircraft building progress by weight
Re: Sinatra Book
#4Nice writeup. Sinatra with builder is just about perfect for implementing web services, dynamically generated RSS feeds, simple web apps, etc. Nicely complements using Rails for rich web apps.
Re: Sinatra Book
#5I must admit some general annoyance at the recent trend in labeling 20-page web-only how-tos "books". Though, given that the Sinatra source itself is under 2k lines, were it a real book, it would quickly be much longer than the source itself. :-)
Measuring programming (books) progress by lines of code (lines of text) is like measuring aircraft building progress by weight
That's trendy to say, and there's a lot of truth to it, but the fact of the matter is that the number of lines of code in a project does convey useful information about its complexity. More accurate would be to say that it's only one dimension in a multi-dimensional metric.
Just like with an airplane, if we add in the weight and what it's made of and used for all of the sudden it becomes a pretty interesting metric.
Re: Sinatra Book
#6Earlier quoted context omitted.
Measuring programming (books) progress by lines of code (lines of text) is like measuring aircraft building progress by weight
That's trendy to say, and there's a lot of truth to it, but the fact of the matter is that the number of lines of code in a project does convey useful information about its complexity. More accurate would be to say that it's only one dimension in a multi-dimensional metric. Just like with an airplane, if we add in the weight and what it's made of and used for all of the sudden it becomes a pretty interesting metric.
(Sorry if a quote sounded empty and cute, I will elaborate my thoughts.)
- Sintara is small (and arguably beautiful), a book on it should be small. Being small doesnot mean it shouldnot be called book.
- Wasn't our biggest gripe with J2ee monster was the enormous complexity, and to handle them the large books required. Wasn't that why rails Django were hailed as game changers? http://i44.tinypic.com/98uhs6.png
Smaller frameworks with smaller learning curve and books take that even further.
Re: Sinatra Book
#7Well written. Includes a section on "deployment" at the end that summarizes various options -- including patches needed to get FastCGI working.
Specific instructions on how to deploy on dreamhost shared accounts (Passanger / fastcgi).
Re: Sinatra Book
#8I must admit some general annoyance at the recent trend in labeling 20-page web-only how-tos "books". Though, given that the Sinatra source itself is under 2k lines, were it a real book, it would quickly be much longer than the source itself. :-)
I'm all for short-but-informative books* , but twenty pages is a booklet. It would be a good size for a chapter in a book on web tools or particularly good Ruby libraries, though.
* Such as seemingly everything Brian Kernighan has co-written.
Re: Sinatra Book
#9How can I contribute? There's a section under the Models for Sequel, but it is blank. I've done plenty of work with Sequel and Sinatra and I'm sure I could fill in the blanks.
Re: Sinatra Book
#10For some reason I enjoy using Sinatra more than Rails, I think it is simpler and more 'Ruby-ish'. Also it works well on the free and scaleable Google App Engine: http://goo.gl/6eW4.