Engineering code quality in Firefox

Re:Engineering code quality in Firefox by mschuetz on Wednesday April 22, 2020 @03:32AM (#22943131)

I wish I could recommend Firefox but I can't because it cripples performance of the things I'm working on, namely streaming and rendering large 3D data.

I'm using Firefox privately at home but for work, including work@home, I'm using almost exclusively Chrome. Chrome is just so much faster and the developer tools so much more polished than Firefox. DataView is 40 times slower in Firefox, and I'm using it quite extensively to read binary files. There is a Uint8Array hack/workaround that lets you write your own DataView that is 4 times faster in Firefox, but 10x slower in Chrome, so it's not an alternative I'm going to use.

[ Parent | on HN ]

Re:Engineering code quality in Firefox by hafta on Thursday April 23, 2020 @12:49AM (#22952898)

Would you be able to file a Firefox bug on the DataView problem? Or if you have an example link we could look at that would be greatly appreciated.

[ Parent | on HN ]

Re:Engineering code quality in Firefox by mschuetz on Thursday April 23, 2020 @01:39AM (#22953128)

There is this 6 year old and open report here: https://bugzilla.mozilla.org/show_bug.cgi?id=1065894

Chrome has improved DataView 2 years ago: https://v8.dev/blog/dataview

A rather basic jsperf is here: https://jsperf.com/dataview-float-int The results are that the u8 hack is equally slow in firefox and chrome (~90ops/sec), the DataView version is 10x faster in chrome(945ops/sec) but almost 4x slower in firefox(25ops/sec).

[ Parent | on HN ]

Re:Engineering code quality in Firefox by hafta on Thursday April 23, 2020 @03:57PM (#22960447)

Thanks.

[ Parent | on HN ]

Re:Engineering code quality in Firefox by mschuetz on Friday April 24, 2020 @12:34AM (#22964677)

Thanks for bringing it up in the firefox issue tracker.

[ Parent | on HN ]