Hacker News Reader

Hacker News

Comment by AndrewDucker | Hacker News Reader

Full thread

AndrewDucker

This has the most toxic UI I've seen in my life.

Switching away from my browser and back again causes the page to re-render, losing my place as it did so. Just awful!

View on HN

I'm pretty sure it's explicitly intended solely as punishment for people who have javascript enabled.

Fwiw I think it's pretty hilarious.

Also I warmly recommend to view-source, the makeprogress() function is a true delight.

Abstractly it’s sort of funny as a joke against JavaScript, but it’s really not funny at all when the butt of the joke is people who have JS enabled on their browsers. It’s just elitist and obnoxious.

I like jazz and think rock/pop generally sucks. If I prefaced every blog post with “people who like rock are too dumb to understand the following” I wouldn’t be making a funny joke about music. I’d just be an asshole.

Oh come on, it's a loading bar, it takes one second. It's totally not comparable to calling people dumb if they have JS enabled, like you suggest.

It'd be more like prefacing a podcast about basic music theory with a 5 second pretentious jazz tune.

I'm pretty sure it's an artificial loading screen too. There's no way it actually takes that long to render. It's quite an interesting artistic statement.

Yep.

  window.setTimeout(makeprogress, delay)

With various repeated hard-coded delays of 50, 250, and 500ms.

Looking at the source, the progress bar is completely fake, it really does nothing besides making you wait. It even introduces slight delays to make it look more realistic.

Why? Just why? The worst part is that the site is actually very light, with none of the ads, analytics and resource hog frameworks that are all too common these days. It probably could load almost instantly if it wasn't for that fake progress bar.

Edit: Judging by the other comments, it looks like it is some kind of political statement against Javascript. I disagree with such practices but well, that's his site, his choice.

It's meant as satire on the needlessly script heavy websites that many people create nowadays. The blog post itself isn't entirely serious either.

Well, unfortunately for me it resulted into an early page close. I thought someone who uses that much javascript for a page that could have been 100% static can't have anything interesting to say.

Just disable JavaScript, then the page loads instantly and works perfectly :)

Javascript doesn't kill browsers. People kill browsers with Javascript.

If I try to search something within the page with Ctrl + F that also causes the whole page to re-render and display "loading ..." and "rendering ..." progress bar.

Extra maddening, as it works fine with Javascript disabled. Those loading and rendering progress bars are a terrible idea.

Haha, it's true! Disabling JavaScript leaves a perfectly working article. Is this one big troll?

It's a joke. It's not a terrible idea. It's a great idea! A great joke!

Well, aside from the delay in seeing the content, it borks the back button up, etc. Breaking all the pages on your site for a joke is an odd idea to me.

Edit: As mentioned by another commenter, seems to be deliberate punishment for having javascript enabled. Also, clicking outside the main window (like in the url bar) does the render thing again. And a search for javascript has some odd results too: https://flak.tedunangst.com/search?q=javascript Last, there's some deliberately awful infinite scrolling too.

Yeah, what's wrong about punishing Javascript users? It's funny.

You can't even search within the page. Ctrl-F hides the content and shows the progress bars.

Reply on news.ycombinator.com