Originally posted by starshipeleven
View Post
Announcement
Collapse
No announcement yet.
Google Uncovers CPU Bug For Geminilake, Affecting At Least Firefox & Chrome
Collapse
X
-
-
Originally posted by starshipeleven View PostThat's a juvenile dream.
You know full well that you can't just disable the program for something you can work around in software. This is the real world for like 1000% of actual software development.
But sometimes I have "hizzyfits/juvenile dreams" of telling a hardware vendor to "shove it".
There isn't much liability in software or hardware for most use cases.
I think that CPUs can be considered static in their presentation.
And as such, if their bugs affect your usage and cannot be fixed without deteriorating other parameters, vendors should be liable.
Ie, taking it back/compensating/replacing it.
- Likes 4
Comment
-
Originally posted by starshipeleven View PostI think that it's not so much only browser triggering the bug, but only browsers have so large widespread use and (for Chrome) so extensive telemetry info that allows them to actually be notified of crashes and their probable cause.
Most other software won't do that, and people will blame Windows, or the software, or the Gods that didn't smile back at them or something.
This is a prime reason why I strongly believe that telemetry about technical and performance information is a very important thing to have.
- Likes 1
Comment
-
Originally posted by discordian View PostSounds more like it's a hard to reproduce bug that depends (amidst other things) on where the linker places stuff.
Hard to blame Google if a cpu can be singled out. Especially if at the same time Mozilla did the "don't care/works for me" instead of investigating.
Mozilla sucks these days.
Intel is having a he'l of CPU bugs these days. I'm getting nostalgia of the old Pentium days.
- Likes 3
Comment
-
Originally posted by timofonic View Post
- Likes 2
Comment
-
Originally posted by milkylainen View PostWhat's so special about the browsers that they keep (apparently?) triggering the bug?
- Likes 3
Comment
-
Originally posted by milkylainen View PostWhat's so special about the browsers that they keep (apparently?) triggering the bug?
Software developers should not fix this issue themselves, neither should compilers or linkers work around it. People should just pressure Intel to roll out a microcode patch ASAP.
- Likes 4
Comment
-
Originally posted by timofonic View Post
Typical Mozilla attitude.
Mozilla sucks these days.
Originally posted by timofonic View Post
Comment
-
Originally posted by milkylainen View PostWhat's so special about the browsers that they keep (apparently?) triggering the bug?
- Likes 2
Comment
-
Originally posted by milkylainen View PostQuite likely. But doesn't Windows come with pretty nice bug reports/automatic telemetry that can be amassed into nice data points?
Which means everything else must use its own telemetry
Comment
Comment