5 ms·
What bothers me about being older is my first browser was Internet Explorer, then I got to play with MOSAIC's slow arse in school, then used Opera/Mozilla, and
by nickpsecurity 11y ago
What bothers me about being older is my first browser was Internet Explorer, then I got to play with MOSAIC's slow arse in school, then used Opera/Mozilla, and so on. Got to see where it came from. And the new stuff, especially Firefox, is coming full circle in how friggin' slow they run to serve the lowest common denominator of web pages.
It's annoying. I miss Web 1.0. Add just a bit of dynamic functionality plus broadband and it would be fine for 80-90% of cases. And FAST!
Instead, we get Web 2.0, 3.0 (4?) which makes pages on 40-50Mbps load like my old 28Kbps modem on AOL. Seriously...?
- pcwalton 11y ago> And the new stuff, especially Firefox, is coming full circle in how friggin' slow they run to serve the lowest common denominator of web pages. It should be easy to find performance numbers showing how Firefox 42 renders old, pre-CSS pages slower than, say, Netscape 4, then. Netscape 4 didn't have a JIT, didn't use hardware accelerated layers, trapped into kernel mode for GDI calls, didn't use accelerated SIMD for painting, and didn't have HTTP 2. It barely had any optimizations for dynamic restyling, so tons of stuff would get reflowed when it didn't have to. This is just the tip of the iceberg. Browsers have gotten more complex, but the complexity is often in the service of making things faster.
- nickpsecurity 11y agoNotice my references to Web 1.0, 2.0, etc? That means my comment was talking about not just the browsers but the sites designed for them. The combination of the two have made web sites really slow that could be designed to load up instantly. Instead, they load up as slowly as some sites did on my old Pentium 2 running Opera, etc. You'd think they'd be significantly faster with all the Moore's law iterations and browser improvements. Modern sites make sure that doesn't happen, though. And I never mentioned Netscape: it was called Netscrape then and hackers despised it. I used Opera and IE mainly.
- pcwalton 11y agoOpera and IE were no different in architecture.
- nickpsecurity 11y agoWasnt aware of that. Interesting. It was just faster, better looking, and skinnable. Plus malware stayed hitting IE so there was that too.
- ZenoArrow 11y agoI don't think the statement you replied to is correct.
- nickpsecurity 11y agoYep. No point in fixing it though.
- ZenoArrow 11y agoWhat are you referring to? Opera and IE certainly used different rendering engines: Trident for IE, Presto for Opera (before it moved to Blink).
- pcwalton 11y agoBack in the Netscape 4 days, the architectures of those engines were broadly the same (in the sense that Linux and FreeBSD have broadly the same architecture). Of course the codebases were different.
- ZenoArrow 11y agoHow do you know this? Trident and Presto were both closed source, did you do some contract work with both Microsoft and Opera at the time?
- CaptSpify 11y agoDisable javascript. Seriously. Disabling js has given me the fastest turn-round on page-load times. It's usually not the browser, but loading 15 different un-optimized JS engines that causes the problem.
- nickpsecurity 11y agoI use NoScript. JS heavy sites are the worst though.