Watched some of the videos (bought the second package)/read a chapter or two and wow. So much stuff in here that's been a pain to figure out via scattered posts and confusing docs. Go pick this up if you want to learn Meteor.
Discover Meteor
21–30 of 80 posts
Re: Discover Meteor
#22This book is exactly what I wanted. But the thing I don't like about Meteor; the barriers to contemporary web development drop like a rock. The problems that could keep me employed with other frameworks are largely solved.
Maybe this will raise the bar into a whole new level of product. But I'm not sure I want to spread the news; its more like something I'd rather keep for myself as a competitive advantage.
Re: Discover Meteor
#23Will this be updated to reflect changes to Meteor? So, when it hits 1.0, will the book be updated?
Re: Discover Meteor
#24This looks fantastic. I am considering a purchase. Just curious, why didn't you use meteor to make discovermeteor.com?
Re: Discover Meteor
#25This book is exactly what I wanted. But the thing I don't like about Meteor; the barriers to contemporary web development drop like a rock. The problems that could keep me employed with other frameworks are largely solved. Maybe this will raise the bar into a whole new level of product. But I'm not sure I want to spread the news; its more like something I'd rather keep for myself as a competitive advantage.
A wee bit over the top there.
Re: Discover Meteor
#26Earlier quoted context omitted.
If the information in the book (regardless of page count) gives you insight into a new technology that you can use to expand your career, is $30 really too much? If you're a contractor billing at market rates in SF, $30 is one-third to one-fifth of a single hour's income. Time to start valuing books based on knowledge contained rather than paper weight.
IF the information contained is proven to be valuable and well-expressed than yes, I agree, $39 (or even $99 or whatever) is totally worth it when the expertise derived pays off. BUT, for an unknown quantity it's still steep. There are plenty of poorly written tech books not really worth the "paper" they're printed on. So asking people to pony-up that kind of money is a little shocking. It might be better to provide…
Asking $30 for a book is shocking? I expect to pay at least that for a good technical book. This is a book I paid $60 for: http://www.amazon.com/Linux-Programming-Interface-System-Han... I did so because the information in it is relevant to my job, it's unlikely to change in a significant way over the next decade, and I was tired of not having a single place to look up Linux systems stuff.
If I was a web developer using Meteor, I imagine I would come to a similar conclusion about this book - with the exception that because it's online, the authors can update it over time.
Re: Discover Meteor
#27This book is exactly what I wanted. But the thing I don't like about Meteor; the barriers to contemporary web development drop like a rock. The problems that could keep me employed with other frameworks are largely solved. Maybe this will raise the bar into a whole new level of product. But I'm not sure I want to spread the news; its more like something I'd rather keep for myself as a competitive advantage.
I am sure that someone said that same quote about [printing press/calculator/CSS/etc.] one time. Not comparing Meteor to these other inventions but tend to dismiss the argument that "X new technology will make my job easier and this is a bad thing."
Re: Discover Meteor
#28Just browsing through it, definitely worth $30 to me. Well written and explains Meteor perfectly for retards like myself.
So tmeasday, now that you're not busy any chance of fixing accounts-anonymous?
Re: Discover Meteor
#29How many pages does the book have? Even with the discount: $30 is way too much for a tech book IMO. Maybe $20 would be doable.
If the information in the book (regardless of page count) gives you insight into a new technology that you can use to expand your career, is $30 really too much? If you're a contractor billing at market rates in SF, $30 is one-third to one-fifth of a single hour's income. Time to start valuing books based on knowledge contained rather than paper weight.
"If you're a contractor billing at market rates in SF, $30 is one-third to one-fifth of a single hour's income."
The issue is that the overwhelming majority of technical people don't live in SF, nor will they ever earn SF rates.
It's absurd that people insist on projecting the economic situation of an incomprehensibly small subset of programmers that are lucky enough to reside in a hot market onto the entire cohort of developers. Most people don't make $100 per hour, and even if they do, other aspects of life are quite expensive (car, house, school). I don't understand why people can't comprehend that some people make modest salaries or don't have limitless disposable income.
$30 isn't necessarily the world (and many people will certainly receive positive value), but it's still a hefty expense that requires one to gauge value. Asserting that someone is wrong to be hesitant about buying the book is presumptuous.
People buy things based on cost, and strive to preserve their money and maximize value. What is so upsetting about that?
Re: Discover Meteor
#30Earlier quoted context omitted.
IF the information contained is proven to be valuable and well-expressed than yes, I agree, $39 (or even $99 or whatever) is totally worth it when the expertise derived pays off. BUT, for an unknown quantity it's still steep. There are plenty of poorly written tech books not really worth the "paper" they're printed on. So asking people to pony-up that kind of money is a little shocking. It might be better to provide…
Asking $30 for a book is shocking? I expect to pay at least that for a good technical book. This is a book I paid $60 for: http://www.amazon.com/Linux-Programming-Interface-System-Han... I did so because the information in it is relevant to my job, it's unlikely to change in a significant way over the next decade, and I was tired of not having a single place to look up Linux systems stuff. If I was a web developer us…
"Asking $30 for a book is shocking?"
Where did you get that? He explicitly said that "if the information contained is proven to be valuable and well-expressed than yes, I agree, $39 (or even $99 or whatever) is totally worth it." He literally said the exact opposite of what you are alleging that he said. Literally.
His shock was in regards to the fact that the offer no sample chapter (which they probably should).