back

by sergiotapia·13y ago·view on hn ↗
Wow, seeing this at the top of this thread really makes me feel HN is jumping the proverbial shark.

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. :/

5 comments
> It's about how you can quickly iterate an application using StackMob

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.

Well, they used a link bait title to get click-throughs, and the article didn't live up to their hype. It's unsurprising that some people are calling them out on 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.

I'm sorry to add fuel to the fire but I've noticed this last few weeks. Almost every single top post to every new Show HN type submission is a brutal teardown or sometimes unfounded criticism. This kind of behavior does not encourage sharing of neat things we build. I've made many things and shared on HN in the past but I'm pretty sure if I were to submit similar things today I'd be called out for not supporting PlatformOfChoice in v0.1a or using improper font-size. I would be nice if people constructively criticized the core product being shared not the tertiary aspects.

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.

Almost every single non-reply post on this article is criticizing how much the app isn't AirBnB. Maybe the new measure of success on HN is finding the excellent discussions under those criticizing posts? Those criticizing top posts always have a huge amount of discussion under them.
why did you use the word "iterate"[1] in this context?

[1]http://www.thefreedictionary.com/iterate

Google it.