As those threads say, many Unity games run well in other browsers, but since Chrome is dominant in the market (over 50%), poor Chrome performance makes Unity look bad. But this isn't Unity's fault.
If your product runs poorly on the dominant market platform, then that _is_ your fault. Especially as Chrome provides source, a reasonable community centered around that source, and strong developer tools to allow third parties to achieve superior performance on their browser.
It's understandable, but the Unity developers made a guess as to the future state of the market and that guess was wrong.
Unity's WebGL is still officially marked as being experimental, so it can't be expected to be a perfectly smooth experience.
If Chrome uses more memory than other browsers, it is definitely not Unity's fault. Having access to the source code won't change anything. Chrome is behind the competitors right now when it comes to memory usage with WebGL, but that may change even in the near future.
Comments
If your product runs poorly on the dominant market platform, then that _is_ your fault. Especially as Chrome provides source, a reasonable community centered around that source, and strong developer tools to allow third parties to achieve superior performance on their browser.
It's understandable, but the Unity developers made a guess as to the future state of the market and that guess was wrong.
Unity's WebGL is still officially marked as being experimental, so it can't be expected to be a perfectly smooth experience. If Chrome uses more memory than other browsers, it is definitely not Unity's fault. Having access to the source code won't change anything. Chrome is behind the competitors right now when it comes to memory usage with WebGL, but that may change even in the near future.