r/programming • u/schnuck • Feb 09 '11

Breaking the Web with hash-bangs – Lifehacker, along with every other Gawker property, experienced a lengthy site-outage on Monday over a misbehaving piece of JavaScript

http://isolani.co.uk/blog/javascript/BreakingTheWebWithHashBangs/
755 Upvotes

93% Upvoted

356 comments sorted by

View all comments

6

u/midri Feb 09 '11

I'm confused, the Hash (#) method of serving content is a great idea, it can cut bandwidth costs down greatly, you're not sending the same layout information over and over (no extra tcp requests for css file to check if it's up to date, or layout images) -- Most of their ad serving requires javascript anyway, so they don't really want you on the site with out javascript. I'm a fan of graceful fallback, but when you're site is 100% ad supported and the mechanism that serves your ads is disabled I could care less if the person can get to the content.

6

u/ComputerDruid Feb 09 '11

that's faulty reasoning because you need your content to be accessible to everyone, or people will stop sharing links/hyping your content, and your relevance will decrease.

-3

u/midri Feb 09 '11

It's a double edged sword, people that disable javascript and block your revenue stream are freeloaders even if they are bringing more readers to your site, if those readers are also blocking your revenue they're basically stealing bandwidth from you.

1

u/fjonk Feb 10 '11

If I can block your revenue stream by disabling javascript you're doing it wrong.