3 ms·

"websites were fast-loading" i lived thru that era. how were they fast on 56kbps modem connections? i clearly remember having to leave my pc on all night to d

by kmlx 7y ago

"websites were fast-loading" i lived thru that era. how were they fast on 56kbps modem connections? i clearly remember having to leave my pc on all night to download a single mp3. for websites i would usually grab a book and read a few pages while the site loaded.

raverbashing 7y ago
No thousands of cookies/trackers (for most sites) Few third party js files Optimized images And the fact the site had to actually open on 56k modems
- lazyasciiart 7y ago
  So....they were slow, but smaller amounts of code was involved? That's not the same as being fast.
  - WaxProlix 7y ago
    Connection was slow, pages were (relatively) fast. Not hard to understand.
    - lone_haxx0r 7y ago
      They weren't fast by any stretch of the word. There was no one with a good connection to experience it fast, so it can't be called fast.
      - eitland 7y ago
        I've mostly had good internet connection since 2004, so I know. Pages were better before this modern SPA thing that ironically get sold in to improve user experience. End of discussion I guess..?
        eternalny1 7y ago
        I have begrudgingly been pulled into SPAs as a developer, and at first I was very skeptical. Now that I see what things like Angular can do, with lazy-loaded components, and only downloading JSON data and letting the client render the DOM, my pages are actually much faster and the UX is vastly better. Yes, you need to download the Angular libs, but so many pages use them now they are likely cached, and are negligible in size for a fast connection. After that, it's client-side routing and downloading mostly just downloading JSON from a REST API. You don't need to server to push a 5,000 row table with all the mark-up, you just grab that data and have the browser construct your table. And yes, you can still copy/paste the URL. And save the page as HTML. And everything else you can do with a "non-SPA" page. YMMV.
        skinkestek 7y ago
        I'm also an Angular developer. And no doubt you can do amazing things with it. But just because I and you can make good pages with it doesn't mean that everyone should do it. Also, in my experience I guess it will typically - more than doubles the cost (and I guess this is a conservative number) - can easily introduce unnecessary problems that prevents cross-browser compatibility - can often introduce security issues that many developers are unaware of etc. Then again maybe I should just let the SPA projects keep on coming: I am a consultant.

by kmlx 7y ago

raverbashing 7y ago

No thousands of cookies/trackers (for most sites) Few third party js files Optimized images And the fact the site had to actually open on 56k modems

lazyasciiart 7y ago
So....they were slow, but smaller amounts of code was involved? That's not the same as being fast.
- WaxProlix 7y ago
  Connection was slow, pages were (relatively) fast. Not hard to understand.
  - lone_haxx0r 7y ago
    They weren't fast by any stretch of the word. There was no one with a good connection to experience it fast, so it can't be called fast.
    - eitland 7y ago
      I've mostly had good internet connection since 2004, so I know. Pages were better before this modern SPA thing that ironically get sold in to improve user experience. End of discussion I guess..?
      - eternalny1 7y ago
        I have begrudgingly been pulled into SPAs as a developer, and at first I was very skeptical. Now that I see what things like Angular can do, with lazy-loaded components, and only downloading JSON data and letting the client render the DOM, my pages are actually much faster and the UX is vastly better. Yes, you need to download the Angular libs, but so many pages use them now they are likely cached, and are negligible in size for a fast connection. After that, it's client-side routing and downloading mostly just downloading JSON from a REST API. You don't need to server to push a 5,000 row table with all the mark-up, you just grab that data and have the browser construct your table. And yes, you can still copy/paste the URL. And save the page as HTML. And everything else you can do with a "non-SPA" page. YMMV.
        skinkestek 7y ago
        I'm also an Angular developer. And no doubt you can do amazing things with it. But just because I and you can make good pages with it doesn't mean that everyone should do it. Also, in my experience I guess it will typically - more than doubles the cost (and I guess this is a conservative number) - can easily introduce unnecessary problems that prevents cross-browser compatibility - can often introduce security issues that many developers are unaware of etc. Then again maybe I should just let the SPA projects keep on coming: I am a consultant.