The entire post is not a "Hey, fuck BnB, we can do it in 2 hours!". It's about how you can quickly iterate an application using StackMob.
It's a tech demo, showing off StackMob, not putting down BnB.
Christ. :/
The entire post is not a "Hey, fuck BnB, we can do it in 2 hours!". It's about how you can quickly iterate an application using StackMob.
It's a tech demo, showing off StackMob, not putting down BnB.
Christ. :/
Then the title should say that.
If you dupe people into reading your article by using a misleading headline, you should be held accountable for it.
EDIT - I'm glad this is off the front page. This etiquette kick that HN is on is really tiresome. None of you or me (except maybe pg) are the arbiters of what defines polite discourse here. And shame on me for getting dragged into it. The policy I strive towards is that if it's a bad comment (egregiously wrong, trolling, etc) I downvote, if it's a good comment I upvote, and if it's interesting and I have something interesting to add I upvote and reply. It's not the worst policy.
If I write a blog post on how to find and fix leaks in single-page JS apps in various browsers, the top post shouldn't be the one complaining about how Chrome takes more memory than Firefox. Comments like that are certainly on topic because memory leaks end up using more memory by definition. The problem is that those kind of comments are too generic to improve anything for anyone but incite enough vitriol to get voted to the top. The top post should be the one finding faults with my leak handling practices and suggesting better methods of doing the same.