5 ms·

Cool presentation, but holy shit, taking ~2 minutes to load on FF and freezing the browser is not.

chimeracoder 11y ago
> Cool presentation, but holy shit, taking ~2 minutes to load on FF and freezing the browser is not. Do you have any extensions installed? It took less than 2 seconds to load for me in a blank Firefox profile, which isn't particularly long for any website with a decent number of images on my connection. My only complaint is that the animations make me seasick - I wish there were an obvious way to turn them off.
- M8 11y ago
  I had same problem on Chrome. Have a lot of extensions, but other websites are fine.
simfoo 11y ago
Welcome to the modern web, where bad technologies (JS, HTTP, CSS and others) are developed to the max and declared modern despite always remaining bad technologies
- jessaustin 11y ago
  Yeah I liked the web better before HTTP... wat? Are you a gopher fan?
  - simfoo 11y ago
    I was alluding to the recent developments leading to HTTP 2
    - jessaustin 11y ago
      Hmmm, my confusion might be because I'm so old that I used gopher before I used the web: it is indeed possible to browse without using HTTP.
carsongross 11y ago
In fairness, taking 2 minutes to load and freezing the browser is a pretty darned good summary of Javascript at 20.
- talmand 11y ago
  In fairness, taking 2 minutes to load and freezing the browser is a pretty good indicator of bad Javascript code.
  - BrendanEich 11y ago
    Rather blame FF or some add-on, if you have to guess. Mark Dalgleish's bespoke framework is tiny. The images are not, so maybe blame your ISP? Dunno, not guessing, but JS is last on the blame-guess list.
    - talmand 11y ago
      Don't get me wrong. I agree wholeheartedly. I'm just responding to the accusation as if Javascript is the known culprit. In those cases, chances are the code itself is the problem and not the language. I can code a page that will likely hang the browser but that doesn't mean I don't take the responsibility of the code that I wrote.
wwweston 11y ago
Anecdote, but I've got 30 tabs open in Chrome and I'm using a Macbook Pro that's over 7 years old and it loads in less than 3 seconds. Also, I can open it in Lynx. The un-alt'd images mean there's a bit of inaccessible content, but it's actually more or less coherent, which might be useful to those whose machines are struggling with the content or even (potentially) to those rendering opinions on whether the web just sucks.
- frik 11y ago
  Anecdote, IE11 "Edge"-mode still doesn't support 3D CSS transformations. It's also end of life in Win8. The presentation worked fine in Chrome and Firefox. It only consumes a few MB RAM. But the favicon of his website is missing - that's why it looks like it loads several seconds.
lol768 11y ago
My issue with it is that I click on the Hacker News link, step through the slides and then want to return back to the hacker news discussion to read the comments. Unfortunately, each slide is treated as a new history item and Firefox only remembers a finite amount of them so I then get stuck on the presentation with no way to get back to the site I was on before. Tempted to just inject this into each page I visit since the feature annoys me so much: history.pushState = function (){};
- tracker1 11y ago
  So, if you're on a search results page, and click next 20 times and then click back, do you expect to go back to the search form, or the previous results page?
  - lol768 11y ago
    Whilst I agree it'd make sense in that particular context for the back button to take me back a page in the results list, I'd rather the search results page made use of actual links which I can use via my browser to make a new HTTP request for another page of results. I dislike sites which insist on loading primary content with JavaScript, breaking the browser's loading feedback (animated icon, hidden favicon) in the process. These sites usually don't handle failed requests properly, either. If I were to post a form in Firefox to a site which happened to be temporarily down, Firefox would display a message explaining what went wrong and giving me the option to resubmit the entire form as many times as I want. I also worry about the pushState function being misused to hide URLs in XSS attacks which involve query string parameters. It's clear you can also stop a user from going back from your page too, something I imagine could also be misused.
conradfr 11y ago
This page loaded fine for me but anecdotally my FF freeze-on-a-page-load has been as it worse for the last one or two versions (no new extensions).
TazeTSchnitzel 11y ago
It loaded instantly for me. Do you have troublesome browser extensions?

> Cool presentation, but holy shit, taking ~2 minutes to load on FF and freezing the browser is not. Do you have any extensions installed? It took less than 2 seconds to load for me in a blank Firefox profile, which isn't particularly long for any website with a decent number of images on my connection. My only complaint is that the animations make me seasick - I wish there were an obvious way to turn them off.

M8 11y ago
I had same problem on Chrome. Have a lot of extensions, but other websites are fine.

simfoo 11y ago

Welcome to the modern web, where bad technologies (JS, HTTP, CSS and others) are developed to the max and declared modern despite always remaining bad technologies

jessaustin 11y ago
Yeah I liked the web better before HTTP... wat? Are you a gopher fan?
- simfoo 11y ago
  I was alluding to the recent developments leading to HTTP 2
  - jessaustin 11y ago
    Hmmm, my confusion might be because I'm so old that I used gopher before I used the web: it is indeed possible to browse without using HTTP.

carsongross 11y ago

In fairness, taking 2 minutes to load and freezing the browser is a pretty darned good summary of Javascript at 20.

talmand 11y ago
In fairness, taking 2 minutes to load and freezing the browser is a pretty good indicator of bad Javascript code.
- BrendanEich 11y ago
  Rather blame FF or some add-on, if you have to guess. Mark Dalgleish's bespoke framework is tiny. The images are not, so maybe blame your ISP? Dunno, not guessing, but JS is last on the blame-guess list.
  - talmand 11y ago
    Don't get me wrong. I agree wholeheartedly. I'm just responding to the accusation as if Javascript is the known culprit. In those cases, chances are the code itself is the problem and not the language. I can code a page that will likely hang the browser but that doesn't mean I don't take the responsibility of the code that I wrote.

wwweston 11y ago

Anecdote, but I've got 30 tabs open in Chrome and I'm using a Macbook Pro that's over 7 years old and it loads in less than 3 seconds. Also, I can open it in Lynx. The un-alt'd images mean there's a bit of inaccessible content, but it's actually more or less coherent, which might be useful to those whose machines are struggling with the content or even (potentially) to those rendering opinions on whether the web just sucks.

frik 11y ago
Anecdote, IE11 "Edge"-mode still doesn't support 3D CSS transformations. It's also end of life in Win8. The presentation worked fine in Chrome and Firefox. It only consumes a few MB RAM. But the favicon of his website is missing - that's why it looks like it loads several seconds.

lol768 11y ago

My issue with it is that I click on the Hacker News link, step through the slides and then want to return back to the hacker news discussion to read the comments. Unfortunately, each slide is treated as a new history item and Firefox only remembers a finite amount of them so I then get stuck on the presentation with no way to get back to the site I was on before. Tempted to just inject this into each page I visit since the feature annoys me so much: history.pushState = function (){};

tracker1 11y ago
So, if you're on a search results page, and click next 20 times and then click back, do you expect to go back to the search form, or the previous results page?
- lol768 11y ago
  Whilst I agree it'd make sense in that particular context for the back button to take me back a page in the results list, I'd rather the search results page made use of actual links which I can use via my browser to make a new HTTP request for another page of results. I dislike sites which insist on loading primary content with JavaScript, breaking the browser's loading feedback (animated icon, hidden favicon) in the process. These sites usually don't handle failed requests properly, either. If I were to post a form in Firefox to a site which happened to be temporarily down, Firefox would display a message explaining what went wrong and giving me the option to resubmit the entire form as many times as I want. I also worry about the pushState function being misused to hide URLs in XSS attacks which involve query string parameters. It's clear you can also stop a user from going back from your page too, something I imagine could also be misused.

conradfr 11y ago

This page loaded fine for me but anecdotally my FF freeze-on-a-page-load has been as it worse for the last one or two versions (no new extensions).

TazeTSchnitzel 11y ago

It loaded instantly for me. Do you have troublesome browser extensions?