W1GUH
06-21-2011, 12:57 PM
But I GOTTA dump a rant about this.
Who the HELL set the standard, or how the hell did the current de facto "website standeard" happen, already.
(This is not aimed at any particular website and CERTAINLY not the Island -- seems most, if not all websites do this).
It seems that websites are designed assuming:
1) All internet connections are instant
(or...those with slow (where slow = DSL speed) connections don't matter)
2) A website has the right to tie up any machine at anytime.
3) Internet users are idiots.
4) There is only one way to do it....the way it's currently done.
What I'm referring to here is the frequency with which a loading website will completely stymie a computer. Can't close the browser, can't scroll the browser, can't do NOTHING 'til that web page is damned good and ready to release your computer.
It seem obvious that graphics REALLY slow down the load speed of a page, yet page designers don't seem to care -- they'll load up a page with hi-res graphics, etc., and you get to wait while your computer is frozen as the page takes its merry time loading.
Since this happens regardless of the browser -- I've seen it with IE, FF, and Chrome -- does this mean that all 3 use the same load strategy? What earthly reason (except lazy, incompetant web designers) is there for a web page to freeze a computer, or at least the browser? Is this an MS issue and the way it forces designers to load pages? Or is this a function of that cursed Java? Since I see moved windows leave "Java traces" often, it looks like many pages use Java (which, IMHO, should be outlawed, it's got so many issues).
OK rant over....if it's incoherent, that's by design.
Again -- not aimed at any particular site or programmer....just a general rant about web page design I've seen.
Who the HELL set the standard, or how the hell did the current de facto "website standeard" happen, already.
(This is not aimed at any particular website and CERTAINLY not the Island -- seems most, if not all websites do this).
It seems that websites are designed assuming:
1) All internet connections are instant
(or...those with slow (where slow = DSL speed) connections don't matter)
2) A website has the right to tie up any machine at anytime.
3) Internet users are idiots.
4) There is only one way to do it....the way it's currently done.
What I'm referring to here is the frequency with which a loading website will completely stymie a computer. Can't close the browser, can't scroll the browser, can't do NOTHING 'til that web page is damned good and ready to release your computer.
It seem obvious that graphics REALLY slow down the load speed of a page, yet page designers don't seem to care -- they'll load up a page with hi-res graphics, etc., and you get to wait while your computer is frozen as the page takes its merry time loading.
Since this happens regardless of the browser -- I've seen it with IE, FF, and Chrome -- does this mean that all 3 use the same load strategy? What earthly reason (except lazy, incompetant web designers) is there for a web page to freeze a computer, or at least the browser? Is this an MS issue and the way it forces designers to load pages? Or is this a function of that cursed Java? Since I see moved windows leave "Java traces" often, it looks like many pages use Java (which, IMHO, should be outlawed, it's got so many issues).
OK rant over....if it's incoherent, that's by design.
Again -- not aimed at any particular site or programmer....just a general rant about web page design I've seen.