Your name has two ns in it, like some common street urchin or rogue. I say, sir, you must take them out or there will be a reckoning upon the morrow! Eviera it shall be, or my name be not atipagada!
Btw I remember browsing the web with early versions of Netscape on X console of an i386sx server which at the same time had dozens of irc-and-whatever-doing users. The browsing experience was smoother than now.
Of course there were no flash, js and other pile of technologies. But face the facts, most of these novelties are used today to deliver the content of questionable value in a way which will make it better memes, nothing more.
If you look at it from a distance it's quite stupid use for such advancved technologies. I still believe in an idea that computers are here to free us from a boring repetitive work - to compute things for us. The outcome of it would be that average user spent less time by the computers, enjoying what he likes in a life instead. But today's situation is that the software industry is making users sitting more by the computers, because this industry is all about trading the information, memes and advertisements, luring the users into false comfort zones like social networks, ad target groups via portals and stuff like that.
It's just stupid. Flash loaders are just part of this counter-productive culture. Usually the more CPU they eat the less interesting the content showed afterwards is. It's like that because CPU-eating intro shows something about the state of mind of people who created it (or hired the creators) and most likely such people will not have anything interesting to show as a real content.
Some of the loaders I've seen (Coke's sites in particular, in my experience) have ridiculous system requirements to appear smooth. Add in that they're using Flash, which pretty much allows you to do anything... and they're examples of what the removal of limitations has spurred. Google's pacman is a good example of creativity within limitations, given that it's a bunch of divs and even works on IE6, instead of something more capable like <canvas>.
Not that I'm denying limitations spur creativity. There are some awesome things in the Demoscene, and older hardware, and more power can often result in less focus.
The Pacman loading bar [1] is actually very interesting. I think it’s just a static image – doomed to be stuck at 60% forever. Since load times are low that doesn’t really matter. It’s instantly recognized for what it is and that might be all that’s needed (and it fits the theme better than those newfangled spinning indicators).
[1] Empty your cache (if you visited before), load and quickly click “Insert Coin”, you might see it for a fraction of a second: http://google.com/pacman
Here's the alternate content, which I saw before allowing scripts:
Once upon a time, in a land of sputtering dial-up connections, websites took ages to load. Folks yearned for the 100% mark. But as soon as that figure arrived, the beloved (or bemoaned) preloader disappeared, never to be seen or heard from again. Until now.
Pretty Loaded is an archive of preloaders that preload other preloaders…which in turn reveal yet more preloaders. Copy that? It’s a tribute to a vanishing art form amid a constantly changing digital landscape.
This infinite loader is being put together with help from friends across the interactive community. We’ll continue to add to it over time, so keep on coming back.
Pretty Loaded is created and curated by Big Spaceship. Kindly direct your observations and inquiries right this way: info |at symbol| prettyloaded |dot| com.
You expect website-creators to stop using ridiculously data-expensive techniques because a new tech comes out? Usually new tech implies the opposite.
The end of loaders (which HTML5 does not represent in the least. Just pre-load through JS with a % done) would be a bad thing, because you wouldn't know that the site would load within a reasonable amount of time. Coke's site could take 5 seconds or 5 minutes, and without a loader, what do you do? Stare at a blank page, wondering if it's working?
When your application uses a lot of assets, it's pretty much unavoidable, independently of underlying technology.
In fact, it's probably going to be worse, at least at the beginning, as JS currently lacks a good way to handle packs of binary resources.
Just check Google IO presentation from team that ported Quake 2 to JS [1]. Resource loading was a big pain point, they had to resort to pack data in UTF strings.
Silverlight also uses the browser cache. I'm surprised that Flash doesn't make use of it (if I had to guess I'd say it does, or rather at least it can).
Flash has used the browser cache since the inception of the plugin. In fact it routes all http requests through the browser itself, it has no built-in stack of it's own. (unless you're on the desktop)
This is an old site and is pretty popular in the creative industry.
Not because of the technical accomplishments but because of the ideas. It should judged as that.