A good way to force this along is to have a champion for the work, and an automated burndown metric that random devs can watch and influence.
Mozilla is pretty good at the latter, cf. https://arewefastyet.com
Mozilla is pretty good at the latter, cf. https://arewefastyet.com
>Safari defaults to 64-bit machines and doesn't need to worry about 32-bit anymore. Big pieces of their engine is 64-bit only. As a result showing Safari on 32-bit machines would give incorrect results.
Maybe this has something to do with it?