3 ms·

There is a big difference between a dynamically-linked library and a constantly running process. I am on a Mac right now. There are no running webkit, webkitd

• smoldesu 4y ago
  Run this: `lsof | grep webkit` You'll need to run that as the user handling WebKit processes, so sudo might be required.
  • ubercow13 4y ago
    How does this prove that Safari gets an inherent performance advantage over Chrome? I guess on startup there could be a slight difference if the library is already loaded in memory.
  • nwienert 4y ago
    No process there (Ventura, ran with sudo). And like everyone has said that would only affect startup time. Safari does absolutely blow away Chrome at startup time, but it also is more performant in basically every other way: battery, memory, runtime, window resize, tab open/close/re-open, forward/back, paint, layout... The UI also is more minimal making well built sites feel much more native than Chrome (on Mac and iOS), especially combined with all the performance. Chrome feels like a dinosaur.
    • kyleee 4y ago
      Safari feels like how Chrome felt 10 years ago :p