Doubling their high street shop network in 2016 seems to be sheer lunacy.
[1] For those who don't remember the reference, their IPO didn't go to plan: http://news.bbc.co.uk/1/hi/in_depth/business/2000/review/106...
Doubling their high street shop network in 2016 seems to be sheer lunacy.
[1] For those who don't remember the reference, their IPO didn't go to plan: http://news.bbc.co.uk/1/hi/in_depth/business/2000/review/106...
Also images were much, much smaller, both in terms of pixels and amount of compression applied, using large images that weren't content was heavily discouraged, and no-one used auto playing videos. To the extent that sins against bandwidth were committed it was mostly with Flash, which we all complained about and which is now reviled, but which was in fact generally way less abusive, confusing, and performance-destroying, than what gets done now in the name of "modern UX". Pages were much smaller, devs were much more sensitive to markup bloat. The worst we had on that front were WYSYWG-made pages (Frontpage, for example) but they've got nothing on the kind of attribute bloat and huge JS payloads one sees now (and the JS in particular can keep on allocating memory after its text is loaded into memory then parsed into even more memory, with predictable results on resource use and page load times)
I had read how, when the 68000 came out originally, it was considered to be a "minicomputer on a chip", while the 68030 was anticipated to be a "mainframe on a chip".
So, I was unable to viscerally appreciate that perspective, until I ran the original MacPaint, which was extremely optimized for the 8MHz 68000 in the original Mac, and then I was amazed at how fast the 68030 was.
I had the Amiga, 68000 at 7.09 MHz (PAL, NTSC ran a teeny bit faster). Both Mac and Amiga gave fully featured, incredibly low latency GUIs. They might think a bit after the click, but compared to a modern GUI, oh so snappy.
Windows, OSX, X with whatever Windowing never get close to that instant tip of your fingers response. I miss low latency responses.
The Mac mouse pointer was always responsive due to interrupts, but that didn't mean that what you clicked on was.
However, the thing that I hate most about the modern web and similar UIs is that they reflow or otherwise move the content you are looking at after you click and before the click is mapped to an element, so you don't get what you click or tap on. This is absolutely unforgivable in my opinion, and absolutely not a matter of degree or grey areas unlike most of the things people complain about.
Took years after I abandoned the platform for serious use for Windows not to always be more sluggish, and get dramatically worse when under load. Course by then I was on '040 comparing with Pentium something.
I’ve read of paragraph long blogposts with 5MB photos resized down to thumbnails ️
Let's see, 2000. Most would be on dial-up, ADSL was either in very early roll out or pre-roll out hype - so nearly everyone waiting on exchanges to be converted. Techies probably had BT Highway, a dual 64k ISDN link. That always seemed really fast, and way faster than many of today's bloatware sites now feel. Insane page and JS weight with dozens of third party calls every page came later. Early broadband, before pages grew to over-compensate for that bandwidth was delightful!
Downloads and Dial up could feel sluggish, especially when you hit the sites being "clever and disruptive" with Macromedia Flash (not many yet), or a site that didn't know how to do thumbnails or image optimisation (quite a few. Usually pages with little 10x10 icons that were really 1024x768 images etc). :)
Cable internet (@home, Cox, or local provider like I had) was much faster than either of those and was available in a lot of places. I think I had a symmetric 1Mb/s, but would experience slowdowns during peak hours (nowhere near dialup).
But not in the UK, which is what the parent comment was about!