> you should ask yourself why in a field as performance sensitive as browser and js engines the developers aren't already doing what you've done, and maybe the

> you should ask yourself why in a field as performance sensitive as browser and js engines the developers aren't already doing what you've done, and maybe the result of your changes is actually lower overall performance or otherwise worse user experience. Of course you should, but you should also play around with the settings and publish your findings. If we didn't explore we wouldn't learn anything. It's possible that those other developers simply didn't consider a setting important, or that what they consider normal browser usage isn't the actually common case. We should encourage experimentation of all kinds.