Hi, really want to buy this book but the idea about chopping down Amazonas when you can do it without, is more valuable. The day it is released digitally i will place an order. /olle
(And sending it with post around the world in more paper and plastics don’t make it better.)
In a world filled with paper towels, toilet paper, and wooden frame houses, I'm surprised that there are some people that don't want to buy this book because of environmental reasons.
This book is not meant to be disposable, certainly not like a paper cup. But when you're done with the book, you can save it, give it to someone else, or recycle it.
I don't know where Lulu sources their paper, but I doubt it's Amazon rainforests. (That sounds expensive.)
Lulu uses FSC certified, lead-free, acid-free, buffered paper made from wood-based pulp.
Electronic devices have an environmental impact too. Which is worse, paper, or electronic waste? A book doesn't need batteries. But more importantly, printed books have tremendous advantages...
Printed books can help you sleep better, are better for learning, and are overwhelmingly preferred over ebooks...
One recent study of college students in the U.S., Slovakia, Japan, and Germany showed that 92 percent of participants preferred actual books that they can hold and touch and leaf through whenever they please.
So yeah, roughly ~8% of people are disappointed with the plan. That's OK, there are digital alternatives... Tumult Hype — Tutorials ...this book was ebook before it was a printed book. While the original had very nice reviews overall, the response now is night-and-day. Look at the joy in this thread. People are happy and excited to get their book. That's amazing. That's what Hype needs.
There's a theme throughout the book — that the modern Internet is boring. Hype can help change that, but you need to really understand the software to push it to the limit. A printed book reduces distraction and helps with learning. The whole purpose of the book is to help people learn Hype. That's been the driving force of the book's design, the way it was written, and the way it's made.
Interesting, I didn't get bubble wrap. It was in a box that tightly wrapped around the book.
Still going to my mailbox every day… not here yet.
The tracking seems to be useless since it says:
«This number can’t be found at this moment. It’s not available in the carrier’s system yet. Please check back»
I keep hope…
Thank you to asked.
Thank you so much for doing it. I have read it now - mostly familiar stuff (hey, been with hype since almost the beginning) but that is also valuable: reminded me of how much I know - and should be happy and proud of. The chapters on JS were extremely valuable: showed me the path forward, the stuff which is still missing in my craft.
Lots of tiny details, small comments which made it time really well spent and also showed how much the author really does care. And personally, I appreciate that a lot.
So one more time, thank you for taking the trouble. I understand this is not business (i.e. the ROI will be minimal, if any…) but - to use grand words - an act of love for the program and community around it. And I find that very touching and valuable.
I have to tell a small anecdote: you said you studied photojournalism and then moved into web design, hype… well, I just finished 30 year career of photojournalism and I am looking for new horizons… Your book is a great asset in that.
Previously I asked if I should put the templates on GitHub. While not exactly a scientific poll, it was unanimous. So, I looked into it. There was one major problem. One doesn't simply drag-and-drop a Hype Template to GitHub.
The .hypetemplate file is actually a package of files. If I try to add it, GitHub automatically compresses it. That defeats the purpose of using Git, as tracking changes is not ideal with encoded text.
...and then there's also my general aversion to social media websites.
I thought about using the "Restore Document from Export" option, but ehhh... that's not exactly friendly to beginners. Anyway, I suppose that's an idea for Hype. Maybe Hype projects should be more friendly for version control.
One of the things I realized while writing this book is that Hype is mainly a soloist app. But lately, the Internet is moving away from the days of an individual "Webmaster" and moving towards teams. Collaboration is definitely and area of improvement for Hype — especially these days, where remote work is far more common.
I think perhaps you're not doing things as you should with your "drag and drop". I just tried pushing a repo with a hype template, then I made changes and committed them and pushed the repo and I could see the changes in data.plist as plain text. I don't know anything about templates but it did seem to work.
You must know how to use Git first, then you can share the repo on GitHub, which by the way is not a social media website.
Or perhaps I'm not understanding what you're trying to do.