Linked by Eugenia Loli-Queru on Sun 17th Jun 2007 23:52 UTC
Thread beginning with comment 248629
To view parent comment, click here.
To read all comments associated with this story, please click here.
To view parent comment, click here.
To read all comments associated with this story, please click here.
My goat with them is the thought of the sheer number of CPU cycles needed, just to drive a simple clock.
First the Javascript has to go through the Javascript interpreter, which then goes through the browser engine, which goes through the OS rendering engine, which goes through the kernel, which goes through the drivers, which then goes through the CPU.
Potentially millions of assembly instructions just to tell you the time. And some people wonder why software is slow - no wonder with developers who think this is a good design model.





Member since:
2005-07-06
Sadly, we'll have to go through this period of uselessness to weed out the pointless implementations. Over a period of time, the purposefullness will eventually come out, but only after the "market" has been saturated with crap.
No one actually knows what purpose it will serve and serve well yet.