Hacker News Reader

Comment by unwind | Hacker News Reader

Uh, I get a mostly blank page with a randomly-placed YouTube icon on the right, and no actual text? Wut?

Edit: Firefox on Linux/x64.

Impressive that they managed to make a plain blog post break. What kind of insane Javascript must be running, that a vertical scroll view with text and pictures has been overcomplicated to the point of breakage

Last time I looked up a function in the Android API reference, it involved a 10MB of file transfer (mostly crude custom fonts, IIRC), and the browser gave up trying to resolve the anchor url meant to jump me to the function itself, so I had to Ctrl-f or manually scroll to actually get to my information.

In recent years, FAANG web teams are way more invested in automating things than engineering them to be efficient, durable, or gracefully adaptive products.

It was harder to try and remove the default js from my small webpage than it was to spin it up and deploy it.

(At Google).

I tried though. My button just did a post and I handled that as opposed to using js to do it.

I also got a blank page on Firefox so I opened the inspector and found manmade horrors sadly within my comprehension: a bunch of elements that initially load as hidden then get unhidden later by JS (which never runs) and the body of the blog post is nothing but a script tag. What the fuck, Google.

Thank goodness no natural intelligence will be able to scrape and copy the content

Loading this page actually makes my CPU fan spin faster for a few seconds :D

maybe they can replace javascript with rust :')

Their Javascript must have got wet - it rusted too much...

That makes it sound like JS is analogous to iron, instead of the damp cardboard it actually is hahahaha

It's choking on this regex with a "too much recursion" error:

   var match = data.match(/([\s\S]+?)<div data-is-preview.+?>([\s\S]+)<\/div>/m);

There's a Firefox bugzilla entry for it: https://bugzilla.mozilla.org/show_bug.cgi?id=1845775

And a (closed in favor of the bugzilla entry) webcompat issue: https://github.com/webcompat/web-bugs/issues/125193

Uh... wow. https://bugzilla.mozilla.org/show_bug.cgi?id=1845775#c14 "Long story short: the watchdog thread interrupted us four times, so we gave up and threw an error. This also explains why Chrome is significantly faster here: when interrupted, we stop the regexp, handle the interrupt, then restart regexp execution from the beginning, whereas V8 does scary code crimes to keep the regexp running despite the possibility of triggering a GC with unrooted values on the stack. (The words "manually relocate unhandlified references" are involved.)"

That doesn't sound good...

Same here.

If you use the uBlock Origin "disable Javascript for this site," it loads totally fine (all of the content is hidden behind either <noscript> tags or some broken javascript).

Works fine for me with no JavaScript, but if I open it in a private browsing window without LibreJS I get what you describe. Funny, usually it's the opposite!

Try refreshing a few times. It seems that they've managed to partially break the page on firefox. I'm currently also on x64/firefox/linux and it works roughly half the time for me.

On the same platform and browser, it displays the header line separator and my CPU fan ramps up but it does load after a few seconds.

It doesn't seem to display properly on all browsers - I got that on Linux Firefox at work earlier, but Android Firefox seems to manage to display it OK.

Not always. I just tried it in FF on my Android phone. No luck. Assuming I'm not missing anything, if they can't be bothered to make a simple blog page loadable.

FFS.

I gave up on Firefox about a month ago. The stupid not being able to copy bug was enough for me. Have had plenty of webpage issues that Chrome and Edge seem to handle just fine. I don't know what's changed lately, but seems as if it's gotten quite buggy.

I gave up on having feet about a month ago. The stupid I hit my toe on the corner of the wall bug was enough for me. Have had plenty of times now where I've ignored that walls might have corners and I haven't banged my toes anymore. I don't know what's changed lately, but seems as if having feet have gotten quite buggy.

Personally when I bang my toes against a corner, I don't think about removing my feet just to prevent toe banging.

---------------

Reductio ad absurdum aside, if I'm experiencing an issue in a browser, my first thought is to diagnose and fix the issue or find an expectable workaround rather than change to a browser with obvious privacy issues.

If you're using Firefox because you think it offers you "privacy", please be sure to read the Firefox Privacy Notice:

https://www.mozilla.org/en-US/privacy/firefox/

Currently, you'll see words, phrases, and names like "Firefox sends", "telemetry", "Google", "Microsoft", "share this with our partners", "share that data with its partners", "sends us data", "share aggregated data", "our third-party ad platform Kevel", "AdMarketplace (a third-party referral platform)", "Cloudflare", "Comcast", "Adjust", "Google advertising ID", "our partner Fastly", and so forth.

In my opinion, I wouldn't expect to see any of those in the privacy policy of any software product that truly respects my privacy.

These are telemetry you CAN turn off.

The browser, for me, is a tool to view web pages. If it does not do that for some web page, I'm going to switch to another browser to view the web page. Lots of browsers to try to view that web page I want to see!

> Lots of browsers to try to view that web page I want to see!

They're literally all Chromium unless you think that Lynx renders websites better than Firefox

Lol privacy issues. Best not use the Internet at all my dude. There is no fix for the copy bug. There is no fix for not loading many webpages properly. Firefox can't do it's primary job well enough for me. The other browsers can.

I've never had any problems with Firefox, odd.

Reply on news.ycombinator.com