Comment by boudin
17 hours ago
Closer to 2 as it was rarelly running at full 56kb/s.
Although, being patient was part of the experience as well
17 hours ago
Closer to 2 as it was rarelly running at full 56kb/s.
Although, being patient was part of the experience as well
I was a lot more careful about clicking things when it took a full minute to load. Now I know that it'll be open in less than a second and I can leave immediately if I need to, so there's WAY less thinking beforehand.
There are quite a few sites that take more than a second to load even now. Should be a war crime, but alas
When I found my first tabbed browser. Netcaptor. It changed everything. Open in new tab. Open in new tab. Open in new tab.
Go back to the first tab which has finally finished loading. Consume.
I would open links in new windows instead. By the time I got done reading one forum thread, the 5 others would be loaded.
It's funny to think back, as I've just recently installed a browser extension to do the opposite (i.e. to prevent "open in new tab" tabs from doing any work until I foreground them.)
Today, my computer's memory is far more constrained than its network bandwidth. I find it very easy to accidentally open tons of tabs very quickly (esp. from the HN front page!) until suddenly the browser is swapping and everything's slowing to a crawl trying to process all those new page DOMs.
And yet, even when it doesn't choke the computer, I find no real benefit to preloading pages in the background any more. At least on my connection, the page load time after I focus a tab is almost imperceptible.
How things have changed!
Also, tabbed browsing was still a couple years off for most people, although some browsers got there earlier than others:
> In 1994, BookLink Technologies featured tabbed windows in its InternetWorks browser.[citation needed] That same year, the text editor UltraEdit also appeared with a modern multi-row tabbed interface. The tabbed interface approach was then followed by the Internet Explorer shell NetCaptor in 1997. These were followed by several others like IBrowse in 1999, and Opera in 2000 (with the release of version 4 - although an MDI interface was supported before then), MultiViews October 2000, which changed its name into MultiZilla on April 1st, 2001 (an extension for the Mozilla Application Suite[11]), Galeon in early 2001, Mozilla 0.9.5 in October 2001, Phoenix 0.1 (now Mozilla Firefox) in October 2002, Konqueror 3.1 in January 2003, and Safari in 2003. With the release of Internet Explorer 7 in 2006, all major web browsers featured a tabbed interface.
https://en.wikipedia.org/wiki/Tab_%28interface%29
Also, Opera had a Multiple-Document Interface from the start, so 1995 or so. That's not "tabs" per se but multiple mini-windows inside the main window; much the same "Hey, I can have multiple things open!" deal
https://en.wikipedia.org/wiki/History_of_the_Opera_web_brows...
My point is, you think more about clicking a link when it'll monopolize your whole UI and you can't just stash it in a background tab or mini-window.
I just opened multiple copies of the browser; I'd have 5 or 10 running most of the time on my 98se box. It's where I got my habit which I still use today, of opening outlinks as I read the page, so they can load in the background, then once I finish the content of this page, I'll go skim those to fill in context.
It meant I cared _less_ about page load time, even on dialup, because they were happening in other windows. I could happily tolerate a 2-minute load time as long as the first page took more than 2 minutes to read.
so true, re: patience
I was just thinking back the other day about BBS days and how frustrating a busy signal could be, or connection time limits, etc.