News for hackers. Stuff that matters.
Re:Comparative unsafety by AndrewDucker on Friday April 09, 2021 @10:35AM (#26751084)
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!

Re:Comparative unsafety by ptomato on Friday April 09, 2021 @10:46AM (#26751197)
I'm pretty sure it's explicitly intended solely as punishment for people who have javascript enabled.
Re:Comparative unsafety by skrebbel on Friday April 09, 2021 @10:50AM (#26751259)
Fwiw I think it's pretty hilarious.

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

Re:Comparative unsafety by nicklecompte on Friday April 09, 2021 @10:44PM (#26758503)
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.

Re:Comparative unsafety by skrebbel on Saturday April 10, 2021 @09:34AM (#26761391)
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.

Re:Comparative unsafety by nicoburns on Friday April 09, 2021 @10:39AM (#26751137)
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.
Re:Comparative unsafety by tyingq on Friday April 09, 2021 @10:43AM (#26751170)
Yep.

  window.setTimeout(makeprogress, delay)
With various repeated hard-coded delays of 50, 250, and 500ms.
Re:Comparative unsafety by GuB-42 on Friday April 09, 2021 @10:58AM (#26751352)
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.

Re:Comparative unsafety by ChrisSD on Friday April 09, 2021 @11:11AM (#26751507)
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.
Re:Comparative unsafety by nottorp on Friday April 09, 2021 @11:16AM (#26751581)
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.
Re:Comparative unsafety by boring_twenties on Saturday April 10, 2021 @12:03AM (#26758817)
Just disable JavaScript, then the page loads instantly and works perfectly :)
Re:Comparative unsafety by nottorp on Saturday April 10, 2021 @10:36AM (#26761776)
Javascript doesn't kill browsers. People kill browsers with Javascript.
Re:Comparative unsafety by chriszhang on Friday April 09, 2021 @10:41AM (#26751160)
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.
Re:Comparative unsafety by tyingq on Friday April 09, 2021 @10:40AM (#26751144)
Extra maddening, as it works fine with Javascript disabled. Those loading and rendering progress bars are a terrible idea.
Re:Comparative unsafety by stefan_ on Friday April 09, 2021 @10:42AM (#26751164)
Haha, it's true! Disabling JavaScript leaves a perfectly working article. Is this one big troll?
Re:Comparative unsafety by caslon on Friday April 09, 2021 @10:42AM (#26751165)
It's a joke. It's not a terrible idea. It's a great idea! A great joke!
Re:Comparative unsafety by tyingq on Friday April 09, 2021 @10:48AM (#26751228)
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.

Re:Comparative unsafety by caslon on Friday April 09, 2021 @11:34AM (#26751840)
Yeah, what's wrong about punishing Javascript users? It's funny.
Re:Comparative unsafety by liminal on Friday April 09, 2021 @10:44AM (#26751179)
You can't even search within the page. Ctrl-F hides the content and shows the progress bars.