3 ms·

Wow. The site loads the text with javascript simply to achieve a fade-in effect. With noscript enabled it's simply a blank page. Fuck this trend in web desig

by na85 11y ago

Wow. The site loads the text with javascript simply to achieve a fade-in effect. With noscript enabled it's simply a blank page. Fuck this trend in web design, and fuck this site. I hate how javascript-heavy the web has become. Why do I need scripts enabled to read a page of text?

pen2l 11y ago
Ohhhhhhh, so that's why so many pages were recently blank for me. I was racking my brain trying to figure out why pages were blank on my default browser with extensions, but not on other browsers.
dTal 11y ago
Firefox's reader mode works well on it, though not on all sites.
ilurk 11y ago
I also experienced the same thing. Could someone explains the tech aspect of this? If noscript is enabled then how is code being executed? HTML and CSS tricks?
frou_dh 11y ago
https://news.ycombinator.com/item?id=9238739 https://news.ycombinator.com/item?id=9238739
- pdkl95 11y ago
  Bikeshedding, which your link complains about, is offering opinions on minutia instead of addressing the actual problems that actually need discussion. Expressing concern about the trend the web is going - executable code instead of open documents - is a primary concern if we want to preserve what's left of the open web. It's important to call out social problems like this so people get accurate feedback[1] about what is and isn't acceptable behavior. [1] see B. F. Skinner and his box (operant conditioning)
  - frou_dh 11y ago
    > the actual problems that actually need discussion That's some mouthful you've come up with to avoid involving "the article", which is the blindingly obvious context for top-level comments on a link aggregator. > It's important to call out [...] problems like this The HN admin seems to disagree.
    - pdkl95 11y ago
      > top-level comment What? This doesn't make sense. > That's some mouthful you've come up with to avoid saying "the article" I'm not referring to the article. That "actual problem" was in reference to the parent comment about requiring readers to execute javascript to read text.
- na85 11y ago
  Not a clue what you're trying to imply by posting this.

by na85 11y ago

pen2l 11y ago

Ohhhhhhh, so that's why so many pages were recently blank for me. I was racking my brain trying to figure out why pages were blank on my default browser with extensions, but not on other browsers.

dTal 11y ago

Firefox's reader mode works well on it, though not on all sites.

ilurk 11y ago

I also experienced the same thing. Could someone explains the tech aspect of this? If noscript is enabled then how is code being executed? HTML and CSS tricks?

frou_dh 11y ago

https://news.ycombinator.com/item?id=9238739 https://news.ycombinator.com/item?id=9238739

pdkl95 11y ago
Bikeshedding, which your link complains about, is offering opinions on minutia instead of addressing the actual problems that actually need discussion. Expressing concern about the trend the web is going - executable code instead of open documents - is a primary concern if we want to preserve what's left of the open web. It's important to call out social problems like this so people get accurate feedback[1] about what is and isn't acceptable behavior. [1] see B. F. Skinner and his box (operant conditioning)
- frou_dh 11y ago
  > the actual problems that actually need discussion That's some mouthful you've come up with to avoid involving "the article", which is the blindingly obvious context for top-level comments on a link aggregator. > It's important to call out [...] problems like this The HN admin seems to disagree.
  - pdkl95 11y ago
    > top-level comment What? This doesn't make sense. > That's some mouthful you've come up with to avoid saying "the article" I'm not referring to the article. That "actual problem" was in reference to the parent comment about requiring readers to execute javascript to read text.
na85 11y ago
Not a clue what you're trying to imply by posting this.