7 ms·

>"Please keep in mind, if you find areas of improvement in V8 and Chrome, even ones that—like this one—do not directly affect spec compliance, stability, or sec

>"Please keep in mind, if you find areas of improvement in V8 and Chrome, even ones that—like this one—do not directly affect spec compliance, stability, or security, please file an issue on our bug tracker." Worst idea ever, this not-a-real-bug got a correction in just a few days without even being in the bug tracker, while there are real bugs stalled for years in the tracker. Writing a blog post and making a lot of noise on the internet works way better than using the bug tracker.

nolok 11y ago
Wrong, making a bug report then being taken up on it is much better than publishing the issue as:is
- serge2k 11y ago
  Why?
- kevingadd 11y ago
  This RNG problem had a bug report with hundreds of comments where a v8 dev downplayed its importance and insisted it shouldn't be fixed. So, bad example.
  - magicalist 11y ago
    Where is that? There have been other issues where this has happened (like the infamous trig optimization bug), but I'm not aware of one for Math.random(). It's also worth noting that a good number of people (like [1]) outside of the V8 team were also skeptical because of lack of specification for the RNG, speed downsides to switching, and the availability of a CSPRNG in the browser and node. You can argue that they're wrong, but that's not immediately clear, Bug reports sometimes become that site of those arguments, and sometimes even the right arguments end up losing a round and having to come back in when the right people are noticing. Working as intended. Regardless, the blog post or bug report dichotomy is a false one anyways, as obviously you can write a blog post and file a bug (as Mike later said he meant to). It's not like he was assailing the V8 team or something. The post was written a little dramatically, but he was engaged with the team in the followup bug (filed by a V8 dev) and elsewhere. [1] https://mobile.twitter.com/sleevi_/status/667636624256344064 https://mobile.twitter.com/sleevi_/status/667636624256344064
magicalist 11y ago
> this not-a-real-bug got a correction in just a few days without even being in the bug tracker, while there are real bugs stalled for years in the tracker That's survivorship bias talking. How many blog posts and attempted noise never make any mark? Better idea: file a bug and write the blog post. Yes, you won't always get all your issues looked at, but that's true of all major open source projects.

nolok 11y ago

Wrong, making a bug report then being taken up on it is much better than publishing the issue as:is

serge2k 11y ago
Why?
kevingadd 11y ago
This RNG problem had a bug report with hundreds of comments where a v8 dev downplayed its importance and insisted it shouldn't be fixed. So, bad example.
- magicalist 11y ago
  Where is that? There have been other issues where this has happened (like the infamous trig optimization bug), but I'm not aware of one for Math.random(). It's also worth noting that a good number of people (like [1]) outside of the V8 team were also skeptical because of lack of specification for the RNG, speed downsides to switching, and the availability of a CSPRNG in the browser and node. You can argue that they're wrong, but that's not immediately clear, Bug reports sometimes become that site of those arguments, and sometimes even the right arguments end up losing a round and having to come back in when the right people are noticing. Working as intended. Regardless, the blog post or bug report dichotomy is a false one anyways, as obviously you can write a blog post and file a bug (as Mike later said he meant to). It's not like he was assailing the V8 team or something. The post was written a little dramatically, but he was engaged with the team in the followup bug (filed by a V8 dev) and elsewhere. [1] https://mobile.twitter.com/sleevi_/status/667636624256344064 https://mobile.twitter.com/sleevi_/status/667636624256344064

magicalist 11y ago

> this not-a-real-bug got a correction in just a few days without even being in the bug tracker, while there are real bugs stalled for years in the tracker That's survivorship bias talking. How many blog posts and attempted noise never make any mark? Better idea: file a bug and write the blog post. Yes, you won't always get all your issues looked at, but that's true of all major open source projects.