Yeah, if I learned one thing from the movies, its that these fish will one day learn to spit acid on me, make me drive my jeep off a cliff and/or eat me.
Let's just hope the scientists had the foresight to make them lycine deficient or else we are all going to die.
I agree that most web sites do not need extensive client-side scripting to be effective (slashdot is an excellent example). However, believe it or not, many businesses want to buy *Applications* that run in web browsers. They don't want the hassle and expense of deploying traditional client-server apps, but still want the functionality and usability of them.
Standard HTML doesn't do that.
Taking your example, even something as providing feedback in the form of an hourglass cursor while a lengthy operation is taking place has a measurable effect on the usability of these applications, especially for our target users (which is clearly not you). The browser is much more of an application platform than a simple layout engine.
My first one is all dog-eared and out of date, but it still sits on my shelf and I occasionally refer back to it. Great book for learning and as a reference.
Sadly, the only book I ever use these days is the Dynamic HTML Reference and SDK from Micro$oft (basically the same info you can get for free from msdn). If you're only supporting IE and just need a quick reference, that book is the bomb. Oh, am I not supposed to use the word bomb anymore? It is the bawm.
Slashdot Mirror
Yeah, if I learned one thing from the movies, its that these fish will one day learn to spit acid on me, make me drive my jeep off a cliff and/or eat me. Let's just hope the scientists had the foresight to make them lycine deficient or else we are all going to die.
I agree that most web sites do not need extensive client-side scripting to be effective (slashdot is an excellent example). However, believe it or not, many businesses want to buy *Applications* that run in web browsers. They don't want the hassle and expense of deploying traditional client-server apps, but still want the functionality and usability of them.
Standard HTML doesn't do that.
Taking your example, even something as providing feedback in the form of an hourglass cursor while a lengthy operation is taking place has a measurable effect on the usability of these applications, especially for our target users (which is clearly not you). The browser is much more of an application platform than a simple layout engine.
My first one is all dog-eared and out of date, but it still sits on my shelf and I occasionally refer back to it. Great book for learning and as a reference.
Sadly, the only book I ever use these days is the Dynamic HTML Reference and SDK from Micro$oft (basically the same info you can get for free from msdn). If you're only supporting IE and just need a quick reference, that book is the bomb. Oh, am I not supposed to use the word bomb anymore? It is the bawm.
I don't have a signature.