• Post Reply Bookmark Topic Watch Topic
  • New Topic
programming forums Java Mobile Certification Databases Caching Books Engineering Micro Controllers OS Languages Paradigms IDEs Build Tools Frameworks Application Servers Open Source This Site Careers Other Pie Elite all forums
this forum made possible by our volunteer staff, including ...
Marshals:
  • Devaka Cooray
  • Campbell Ritchie
  • Tim Cooke
  • Ron McLeod
  • Paul Clapham
Sheriffs:
  • Liutauras Vilda
  • Jeanne Boyarsky
  • paul wheaton
Saloon Keepers:
  • Tim Holloway
Bartenders:

Why Rails?

 
Ranch Hand
Posts: 194
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
(I enjoy both Ruby/Rails and Java, so I'm not trying to start a flame war here.)

Reporting has always seemed like a non-web focused technology, so I'm wondering why Rails was stuck into the title? Looking through the description on it seems like while reporting ON web applications is a key part of the book, the book is about reporting not building websites that generate reports.

Is the book more about using Ruby to generate reports, with Rails tacked on as a buzzword, or is the use of rails more prevalent, and if so how?
 
Well behaved women rarely make history - Eleanor Roosevelt. tiny ad:
The new gardening playing cards kickstarter is now live!
https://www.kickstarter.com/projects/paulwheaton/garden-cards
reply
    Bookmark Topic Watch Topic
  • New Topic