Bugzilla

Fear not; knowing about how other engines work doesn't mean you have to discard your own ideas for optimization. It just means that by combining both ideas you may become faster than either of them.

(In reply to Nicolas B. Pierron [:nbp] from comment #5) 
> and we would not be faster if we keep copying.

Not strictly true because there are multiple engines to copy from. If the time in a function is made up by its subparts A and B, and if Chrome is fast at A and slow at B, and Safari is slow at A and fast at B, then we can be faster than either of them by copying Chrome's optimization for A and Webkit's optimization for B, and be fast at A and B.

Fear not; knowing about how other engines work doesn't mean you have to discard your own ideas for optimization. It just means that by combining both ideas you may become faster than either of them.

(In reply to Nicolas B. Pierron [:nbp] from comment #5) 
> and we would not be faster if we keep copying.

Not strictly true because there are multiple engines to copy from. If the time in a function is made up by its subparts A and B, and if Chrome is fast at A and slow at B, and Safari is slow at A and fast at B, then we can be faster than either of them by copying Chrome's optimization for A and Safari's optimization for B, and be fast at A and B.

Fear not; knowing about how other engines work doesn't mean you have to discard your own ideas for optimization. It just means that by combining both ideas you may become faster than the other engines.

(In reply to Nicolas B. Pierron [:nbp] from comment #5) 
> and we would not be faster if we keep copying.

Not strictly true because there are multiple engines to copy from. If the time in a function is made up by its subparts A and B, and if Chrome is fast at A and slow at B, and Safari is slow at A and fast at B, then we can be faster than either of them by copying Chrome's optimization for A and Safari's optimization for B, and be fast at A and B.