3 ms·

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