3 ms·
Just out of curiosity, did Chrome get faster since https://news.ycombinator.com/item?id=13752024 https://news.ycombinator.com/item?id=13752024 or did Safari get
by bzbarsky 9y ago
Just out of curiosity, did Chrome get faster since https://news.ycombinator.com/item?id=13752024 https://news.ycombinator.com/item?id=13752024 or did Safari get slower?
In any case, I'd like to try to figure out what's going on here. Is the problem reproducible with the publicly available demo of partsbox? If so, what are the steps to reproduce? That is, what operations are you measuring?
- jwr 9y agoI don't think either happened. I made a mistake, I intended to say that Safari comes out on top. Sorry about that. Yes, the public demo is just fine for trying things out. As for measuring, Chrome does seem to have a faster JavaScript engine, as operations like search indexing take shorter than in Safari. However, for interactive use, Safari provides the best experience. I do not know why — perhaps due to the way it updates the displayed DOM? In Chrome long computations in JavaScript run fast, but Safari feels more snappy in real use.
- bzbarsky 9y ago> Yes, the public demo is just fine for trying things out. OK. Could you point me to the specific operations on the public demo that are slow in Firefox? I've been trying a few things side by side with Chrome/Safari and not really seeing a perceptible difference, but I don't really know my way around this UI, so it's possible I'm not finding the right things, or not noticing lag that you're noticing... Note that I was using a Firefox nightly; if you're seeing the slowness in a specific Firefox release, which one is it?
- jwr 9y ago> OK. Could you point me to the specific operations on the public demo that are slow in Firefox? Sure — please try the search box. Enter "mkl" and observe: Safari and Chrome feel snappy and provide instant results as you type. Firefox is noticeably laggy.