The Rails 3 Way (2nd Edition) und über 1,5 Millionen weitere Bücher verfügbar für Amazon Kindle. Erfahren Sie mehr
  • Statt: EUR 48,66
  • Sie sparen: EUR 13,71 (28%)
  • Alle Preisangaben inkl. MwSt.
Nur noch 1 auf Lager (mehr ist unterwegs).
Verkauf und Versand durch Amazon.
Geschenkverpackung verfügbar.
Menge:1
The Rails 3 Way (Addison-... ist in Ihrem Einkaufwagen hinzugefügt worden
+ EUR 3,00 Versandkosten
Gebraucht: Sehr gut | Details
Verkauft von worldofbooksde
Zustand: Gebraucht: Sehr gut
Kommentar: The book has been read, but is in excellent condition. Pages are intact and not marred by notes or highlighting. The spine remains undamaged.
Ihren Artikel jetzt
eintauschen und
EUR 0,10 Gutschein erhalten.
Möchten Sie verkaufen?
Zur Rückseite klappen Zur Vorderseite klappen
Anhören Wird wiedergegeben... Angehalten   Sie hören eine Probe der Audible-Audioausgabe.
Weitere Informationen
Dieses Bild anzeigen

The Rails 3 Way (Addison-Wesley Professional Ruby) (Englisch) Taschenbuch – Dezember 2010


Alle 2 Formate und Ausgaben anzeigen Andere Formate und Ausgaben ausblenden
Amazon-Preis Neu ab Gebraucht ab
Kindle Edition
"Bitte wiederholen"
Taschenbuch
"Bitte wiederholen"
EUR 34,95
EUR 29,75 EUR 5,03
51 neu ab EUR 29,75 8 gebraucht ab EUR 5,03

Dieses Buch gibt es in einer neuen Auflage:


Hinweise und Aktionen

  • Große Hörbuch-Sommeraktion: Entdecken Sie unsere bunte Auswahl an reduzierten Hörbüchern für den Sommer. Hier klicken.

Jeder kann Kindle Bücher lesen — selbst ohne ein Kindle-Gerät — mit der KOSTENFREIEN Kindle App für Smartphones, Tablets und Computer.



Produktinformation


Mehr über den Autor

Entdecken Sie Bücher, lesen Sie über Autoren und mehr

Produktbeschreibungen

Pressestimmen

Praise for the Previous Edition This encyclopedic book is not only a definitive Rails reference, but an indispensable guide to Software-as-a-Service coding techniques for serious craftspersons. I keep a copy in the lab, a copy at home, and a copy on each of my three e-book readers, and it's on the short list of essential resources for my undergraduate software engineering course. -Armando Fox, adjunct associate professor, University of California, Berkeley Everyone interested in Rails, at some point, has to follow The Rails Way. -Fabio Cevasco, senior technical writer, Siemens AG, and blogger at H3RALD.com I can positively say that it's the single best Rails book ever published to date. By a long shot. -Antonio Cangiano, software engineer and technical evangelist at IBM This book is a great crash course in Ruby on Rails! It doesn't just document the features of Rails, it filters everything through the lens of an experienced Rails developer-so you come our a pro on the other side. -Dirk Elmendorf, co-founder of Rackspace, and Rails developer since 2005 The key to The Rails Way is in the title. It literally covers the "way" to do almost everything with Rails. Writing a truly exhaustive reference to the most popular Web application framework used by thousands of developers is no mean feat. A thankful community of developers that has struggled to rely on scant documentation will embrace The Rails Way with open arms. A tour de force! -Peter Cooper, editor, Ruby Inside In the past year, dozens of Rails books have been rushed to publication. A handful are good. Most regurgitate rudimentary information easily found on the Web. Only this book provides both the broad and deep technicalities of Rails. Nascent and expert developers, I recommend you follow The Rails Way. -Martin Streicher, chief technology officer, McLatchy Interactive; former editor-in-chief of Linux Magazine Hal Fulton's The RubyWay has always been by my side as a reference while programming Ruby. Many times I had wished there was a book that had the same depth and attention to detail, only focused on the Rails framework. That book is now here and hasn't left my desk for the past month. -Nate Klaiber, Ruby programmer As noted in my contribution to the Afterword: "What Is the Rails Way (To You)?," I knew soon after becoming involved with Rails that I had found something great. Now, with Obie's book, I have been able to step into Ruby on Rails development coming from .NET and be productive right away. The applications I have created I believe to be a much better quality due to the techniques I learned using Obie's knowledge. -Robert Bazinet, InfoQ.com, .NET and Ruby community editor, and founding member of the Hartford, CT, Ruby Brigade Extremely well written; it's a resource that every Rails programmer should have. Yes, it's that good. -Reuven Lerner, Linux Journal columnist

Über den Autor und weitere Mitwirkende

Obie Fernandez has been hacking computers since he got his first Commodore VIC-20 in the eighties, and found himself in the right place and time as a programmer on some of the first Java enterprise projects of the mid-nineties. Obie has been evangelizing Ruby on Rails online via blog posts and publications since early 2005. He has traveled around the world relentlessly promoting Rails at large industry conferences. As CEO and Founder of Hashrocket, Obie specializes in orchestrating the creation of large-scale, web-based applications, both for startups and mission-critical enterprise projects. He still gets his hands dirty with code on at least a weekly basis and posts regularly on various topics to his popular technology blog.


In diesem Buch

(Mehr dazu)
Ausgewählte Seiten ansehen
Buchdeckel | Copyright | Inhaltsverzeichnis | Auszug | Stichwortverzeichnis
Hier reinlesen und suchen:

Kundenrezensionen

Es gibt noch keine Kundenrezensionen auf Amazon.de
5 Sterne
4 Sterne
3 Sterne
2 Sterne
1 Sterne

Die hilfreichsten Kundenrezensionen auf Amazon.com (beta)

Amazon.com: 20 Rezensionen
56 von 58 Kunden fanden die folgende Rezension hilfreich
A Rails 3.0 reference for experts, but a flawed champ.. 20. Dezember 2010
Von Peter Cooper - Veröffentlicht auf Amazon.com
Format: Taschenbuch
The Rails 3 Way is an interesting book representing a large amount of effort digging into Rails 3. It shares insights and technical knowledge you'd struggle to patch together from blog posts and documentation. It's a very opinionated book and will not be to everyone's taste. For starters, ERb isn't covered at all, instance variables in views are scowled at, and Test::Unit is treated with contempt.

It's not an introductory book in any sense and Obie acknowledges this in his introduction. Obie bills it as a "day-to-day reference for the full-time Rails developer" - a fair description IMHO, but the book feels disjointed in places and has a scattershot approach to what it cares to cover. You need to be clued up to digest this book properly. For an intermediate to expert Rails developer (especially one yet to move to Rails 3) or an expert Rubyist new to Rails, The Rails 3 Way is a useful book that unearths some of the trickier parts of Rails 3 a professional needs to know about. I recommend it - but not as wholeheartedly as the original edition for a number of reasons:

* Parts of the book feel curiously short or scattershot in their coverage. The AJAX on Rails chapter is a mere 16 pages. The RSpec chapter is 33 pages long and provides only an overview (and says as much) though given the recent release of RSpec 2.0 and the new RSpec book, this may be a plus. Rails Engines aren't discussed or covered at all except for a small sidenote that links you to a gist on GitHub. It's not all bad though - some chapters are great, complete guides to a topic, such as Active Record Associations and Advanced Active Record.

* A lot can be gathered from what's not mentioned in the book at all: Capybara, Selenium, Webrat, Searchlogic, SASS, factory_girl.. It wouldn't be expected for a book like The Rails 3 Way to go into depth with any of these tools but having no mentions of them when related issues are raised feels like a missed opportunity to give people some guidance. The lack of Webrat is bizarre since the only full integration test shown in the book clearly uses it. Webrat is neither mentioned nor explained. Nor is Capybara, Webrat's heir apparent.

* The concept of using a different ORM than ActiveRecord is mentioned only once, in the context of running --skip-migration on a rails generate in order to prevent ActiveRecord migrations being generated. Considering what a big deal ORM agnosticism was when developing Rails 3, this is a disappointment.

* Concepts are sometimes used in code but not mentioned in the text. In the RSpec chapter, for instance, the first example includes a call to factory_girl's Factory method, yet nothing about factory_girl or the benefits of factories is covered. I only know it's factory_girl being called because the gem's name appears in the copy-and-pasted output from running bundle install 500 pages earlier.

* Tests are rarely used or demonstrated except in the RSpec overview, Working With Active Record (4 test snippets in 39 pages), Action Mailer (once), and Active Record Associations (6 test snippets in 50 pages). Oddly, though, 4 stray instances of using Test::Unit instead pop up when writing a test for a belongs_to association - it's never used again anywhere else in the main part of the book..

Nonetheless, I recommend the book. It's a flawed champ. While there are other great Rails books in the pipeline, The Rails 3 Way offers a lot right now, as long as you're either happy to look past its flaws or skilled enough to mentally fill in the blanks..
22 von 23 Kunden fanden die folgende Rezension hilfreich
Not a good reference, not a good intro 6. September 2011
Von David Copeland - Veröffentlicht auf Amazon.com
Format: Taschenbuch Verifizierter Kauf
Had I written this review after about a month with this book, I would've given it very high marks. However, after several months with it, attempting to us it in a real Rails 3 project, I find it wanting.

It's billed as a reference for Rails 3, and seems intended as something to have dog-eared, by your side, while cranking out a Rails app. In my experience over the last several months, it has been a source of frustration, providing me with little more than introductory information on topics that, sadly, are better covered by the rails guides or in various blog posts.

The section on Active Record, specifically on querying, is very light. It's mostly a printout/summary of some of the methods available, with no substantive examples, or anything close to what might be required in the real world. AREL is barely mentioned; all we get is a link to the github page.

There are two bigger disappointments: testing and AJAX.

The AJAX section is not remotely sufficient to become effective with the rails 3 Unobtrusive JavaScript stuff, and most of this section is spent on RJS, which the book says is not recommend (so why is it there?). The way in which Rails deals with AJAX, and the tools it provides, are very poorly documented in general, and this is the sort of gap you'd expect this book to fill in. Not the case.

Testing: Testing is not even listed in the index. Let me repeat that: Testing is not even listed in the index. There is a chapter on RSpec, which is wholly out of place, most of the chapter just dealing with general RSPec stuff. There is some rails-specific stuff, but overall this is IT for testing. Again, the tools and APIs Rails provides for testing are powerful, but very weakly documented, and this book completely drops the ball on filling in this crucial gap. I find it rich, since the Rails community prides itself on testing. Additionally, it seems inconsistent with other non-Rails-default choices (Test::Unit being the default); HAML is used in all view examples, yet there isn't even a mention of it as being nonstandard, nor is there so much as a SIDEBAR to explain how it works. While I personally think using HAML was a bad choice, if the case is to be made that it's superior; at least throw people a bone so they understand what it is, why it should be used, and how it works.

A big chunk of the book is simply formatted API documentation. This information can be easily found online, and is far easier to search.

Given all of this, I've found that The Rails 3 Way has not ONCE provided me with the answer to an issue I was having building what I believe to be a very simple website. Every time, I've closed the book and searched the web, often finding clear and cogent explanations; the exact things that should be in this book!

A book that touts itself as a reference for advanced Rails development should provide more in-depth explanation of not just how things work, but how to go about discovering advanced features and diagnosing problems.

If you are looking for introductory material, I'd advise against this, and if you are looking for more advanced coverage, again, I cannot recommend this book.
38 von 43 Kunden fanden die folgende Rezension hilfreich
Kindle version is unusable 12. Juni 2011
Von Johan Pretorius - Veröffentlicht auf Amazon.com
Format: Kindle Edition Verifizierter Kauf
I have no issue with the contents of the book, only the Kindle implementation thereof.

Listings and tables are converted to images, and some of those are so small that it is all but impossible to read on the Kindle.

Unfortunately, the Kindle for PC version is even worse, the image rendering is pathetic, to say the least.

I've bought 3 other Kindle books from the Addison-Wesley Professional Ruby Series as well, only Eloquent Ruby and Rails AntiPatterns can be read in their entirety on the Kindle, Service-Orientated Design with Ruby and Rails is as badly delivered as The Rails 3 Way.

At least one can get some of the missing details by looking at the source code repositories for each book, but that is no excuse. If you buy a book (paper copy), surely the expectation is that all pages can be read?
15 von 17 Kunden fanden die folgende Rezension hilfreich
Valuable unless you're very beginner or very expert 1. Juni 2011
Von Amazon Customer - Veröffentlicht auf Amazon.com
Format: Taschenbuch
The Rails 3 Way is not quite a reference manual, nor is it a tutorial.

Before picking this up, you're probably going to want to have hit your head against something in the framework, or have tried to solve something that the framework doesn't necessarily lend itself well to, or just plain gotten stuck on something. In short, I think that you need a fair amount of context before this book is useful in any way. Not enough, and your eyes will glaze over, too much and it will seem to be restating the obvious without giving you any finer points to chew on.

This book's best audience is probably the intermediate Rails developer who has written some rails applications, has a basic understanding of the RoR framework, but still thinks that much of what happens is "magic".

If this is you, this book has much to offer. It covers all the major pieces of developing with Rails 3 from configuration to AREL to caching to writing your own plugins (and more).

For such a developer, The Rails 3 Way is likely to take you from being a haphazard poke-a-stick-at-it programmer to a deliberate, skillful, productive, and confident RoR developer.
6 von 8 Kunden fanden die folgende Rezension hilfreich
meh, useful if you already know rails I guess 24. Juli 2012
Von Justin Heck - Veröffentlicht auf Amazon.com
Format: Taschenbuch
This book feels like a hodge-podge mish-mash of Rails knowledge, riddled with errors and inconsistencies (contradicting itself on opposite-facing pages is not uncommon). Too often the book introduces a topic, and paragraphs or pages later will declare said topic defunct. The more attention paid to explanations of features, the more obnoxious they become - nothing is described simply. Instead, one or two highly contrived, barely comprehensible sentences will summarize a feature at the start of a description, followed by long-winded, unguided ramblings of the author's opinions on the feature or useless history. My personal favorites are when the author defers explanations to non-existent blog posts... Really, linking to a blog post in a print publication? Amateur.
The code examples, aside from not having a standard format throughout the book, all work off the same concept of timesheets, which makes not only for unstimulating reading, but the author regularly will miss the point of the feature being described just to contrive some strange use of it to fit into the timesheet paradigm.

This book could be half the length with twice the value if all the fanboy streamofconsciousness bullshit was cut out, and some proper structure/purpose was introduced. As it stands, it's best to read only the first and last sentences of any section, with a quick skim, and look elsewhere for code implementation examples of broad overview functionality descriptions.

There is a lot here, but there's little to be had. A poor excuse for a reference, and a poorer excuse for a guide.
Waren diese Rezensionen hilfreich? Wir wollen von Ihnen hören.