News for hackers. Stuff that matters.
Re:Google – you can change the game, damn it by endtime on Thursday April 08, 2010 @04:45PM (#1250846)
Even if such a thing could cope with rendering differences, there's not a damn thing it could do about performance differences (unless it artificially slowed down everything to run as fast as the worst browser).
Re:Google – you can change the game, damn it by endtime on Friday April 09, 2010 @12:59AM (#1251922)
I didn't intend to say anything stupid here...why the downvotes? I don't care about the karma, just want to understand why I was wrong.
Re:Google – you can change the game, damn it by plinkplonk on Friday April 09, 2010 @01:12AM (#1251942)
".why the downvotes? I don't care about the karma, just want to understand why I was wrong."

Voting on HN has gone to the dogs a bit recently with thoughtless (and often mass) downvoting. There is often no real "reason" except some dumb fellow got up oon the wrong side of the bed today.

My suggestion, don't worry about it, just say what you want to. By and large, good comments are upvoted sooner or later. (upvoted you btw)

Re:Google – you can change the game, damn it by endtime on Friday April 09, 2010 @03:47AM (#1252160)
Thanks (and I agree with you), but like I said, really not concerned about the karma. Just wanted to know if I'd said something foolish or incorrect.
Re:Google – you can change the game, damn it by mhansen on Friday April 09, 2010 @02:56AM (#1252094)
Computers have different speeds, and the same software still runs on them. (Unless the computer's too slow or the program is sloppily coded, but then that's the fault of the manufacturer or programmer.) Why do you think a framework should iron out performance differences?
Re:Google – you can change the game, damn it by endtime on Friday April 09, 2010 @03:51AM (#1252164)
I specifically don't think that. My comment's grandparent mentioned performance differences between browsers, and my comment's parent suggested that a JS framework could smooth out differences between browsers. I was pointing out precisely that a JS framework wouldn't be able to compensate for that.