Linked by Thom Holwerda on Mon 7th Mar 2011 23:21 UTC
Thread beginning with comment 465262
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.
News
Linked by Thom Holwerda on 05/19/13 23:15 UTC
Linked by Thom Holwerda on 05/19/13 23:11 UTC, submitted by Drumhellar
Linked by Thom Holwerda on 05/18/13 21:06 UTC
Linked by Thom Holwerda on 05/18/13 7:37 UTC
Linked by fran on 05/18/13 1:38 UTC
Linked by Thom Holwerda on 05/17/13 23:35 UTC, submitted by kragil
Linked by MOS6510 on 05/17/13 22:22 UTC
Linked by Thom Holwerda on 05/17/13 22:15 UTC, submitted by Tom
Linked by Thom Holwerda on 05/16/13 21:41 UTC
Linked by Thom Holwerda on 05/16/13 17:04 UTC
More News »
Sponsored Links



Member since:
2006-03-26
People keep posing these questions as if they are some mystical unanswerable wisdom questions.
"Who's at fault? The plug-in -- or the browser?"
Whichever one is causing the problem. Thats what developers and debugging is for.
This problem exists already anyway. Your developing an app with .net and something throws an exception. Well good luck convincing microsoft it's them and not your software. Though 99.999% of the time is isnt the .net framework. Even if it is the .net framework, you do your best to make your product look good and work. You find a workaround.
"If the car then crashes because the larger tyres rub on some part of the wheel arch, who's liable?"
Quite obviously the owner of the car. The owner knows the size of the wheel arch and they put the big tires on anyway..
Edited 2011-03-08 13:31 UTC