- Taschenbuch: 236 Seiten
- Verlag: Manning (28. Juli 2013)
- Sprache: Englisch
- ISBN-10: 1617290149
- ISBN-13: 978-1617290145
- Größe und/oder Gewicht: 18,7 x 1,4 x 23,5 cm
- Durchschnittliche Kundenbewertung: 1 Kundenrezension
- Amazon Bestseller-Rang: Nr. 181.136 in Fremdsprachige Bücher (Siehe Top 100 in Fremdsprachige Bücher)
Andere Verkäufer auf Amazon
+ kostenlose Lieferung
Sass & Compass in Action (Englisch) Taschenbuch – 28. Juli 2013
Kunden, die diesen Artikel gekauft haben, kauften auch
Welche anderen Artikel kaufen Kunden, nachdem sie diesen Artikel angesehen haben?
Es wird kein Kindle Gerät benötigt. Laden Sie eine der kostenlosen Kindle Apps herunter und beginnen Sie, Kindle-Bücher auf Ihrem Smartphone, Tablet und Computer zu lesen.
Geben Sie Ihre Mobiltelefonnummer ein, um die kostenfreie App zu beziehen.
Wenn Sie dieses Produkt verkaufen, möchten Sie über Seller Support Updates vorschlagen?
Über den Autor und weitere Mitwirkende
Wynn Netherland is a full stack web creative. When he's not shipping awesome at GitHub, he co-hosts The Changelog Podcast and speaks at industry conferences.
Nathan Weizenbaum is the creator and the lead developer of Sass. He's currently a software engineer working on Gmail at Google.
Chris Eppstein has more than ten years of experience building web sites. An active member of the Ruby community, he's the creator of Compass, a member of the Sass core team, and maintains or contributes to dozens of open source projects.
Derzeit tritt ein Problem beim Filtern der Rezensionen auf. Bitte versuchen Sie es später noch einmal.
Die hilfreichsten Kundenrezensionen auf Amazon.com
At work, I had dabbled with Sass here and there, but never really knew what I was truly doing. As always, with a stable codebase, one can actually get away with hacking around, or “sort of knowing” what is going on. With code reviews, you can usually produce some quality code just by developing by making inferences.
Of course, it didn’t take too long before my engineering self decided to really dive deep into how something really worked under the hood. Before reading this book, I had read the official Sass documentation and had a good grasp of writing “sassy” stylesheets. In hindsight, the Sass documentation is actually enough for one with enough CSS background to actually be knowledgeable about creating maintainable stylesheets. Now, I have just given away my opinion of what I think of Sass and Compass In Action.
So first, my expectations for this book.
I had expected it to be a deep-dive tutorial to further discuss the inner-workings of Sass. I wanted to learn more than what the Sass documentation provided. To be truthful, I did not. But here’s my objective opinion:
Who this book is for:
- If you really aren’t convinced that compiled stylesheets are the future, this book will convince you.
- It’s a great introduction to modern front-end web development for those who come off from a traditional “build your pages server-side dynamically and send the generated markup back to the client”-club.
- If you haven’t really played with CSS grids in the past, this book will give you just that.
- Learning basic browser-rendering performance. The book has a section dedicated to optimizing the delivery of your front-end assets. I think this is probably worth buying the book to get a taste and basic delivery of front-end assets on the web. There’s even a section on how to go about debugging HTTP requests to assets.
Who this book isn’t for:
- If you have prior experience to CSS frameworks like Twitter Bootstrap, a lot of the stuff discussed that tries to pump you up about Compass isn’t a big deal: Grids, Dynamic sprite sheet generation, URL generation, etc.
- If you know Sass, then you should probably skip this book… honestly, it felt like the book was more of “Compass in Action” rather than the former.
- If you are already a professional web engineer and are already creating production-grade user interfaces, then this book falls too much into beginner-grade for you.
Overall for the 195 pages or so of content, it took me about 3 days worth of reading for 1–2 hours at a time to complete (totaling about 8 hours or so). I had read word-for-word in the beginning, but slowly teetered off to scanning for only the material which interested me.