|
|
|
|
|
|
by mikeash
5289 days ago
|
|
|
In addition to what others have said, Safari 5.1 moved to a subprocess model somewhat like Chrome but the change went severely wrong. Memory usage skyrocketed, and speed and stability both took a big dive. After using Safari pretty much exclusively since it was originally released, the awful 5.1 release prompted me to switch to Chrome and I haven't looked back since. Apple's attention really is turned to the mobile space today, and the non-mobile Safari suffers for it. |
|
|