3 ms·

>Overall, as a user of Safari, I appreciate that it lags behind the bleeding edge. Stability, battery life, and privacy are important things to me. Some featur

>Overall, as a user of Safari, I appreciate that it lags behind the bleeding edge. Stability, battery life, and privacy are important things to me. Some features could help with that like https://developer.mozilla.org/en-US/docs/Web/API/HTMLImageElement/loading https://developer.mozilla.org/en-US/docs/Web/API/HTMLImageEl... , if Safari is always behind 1 year or two then you always lose battery and bandwidth, so yeah Safari devs are not chasing efficiency if they would then they would have been the first not the last to implement this. Also try to search for "broken/not working in Safari" and you will see is not all about some nightmarish privacy invading APIs.

falcolas 5y ago
Both are fair points. And yet at the end of the day, it's Chrome that spins my fans up, not Safari. It's Chrome that's pushing FLOC and its replacement, not Safari.
dmitriid 5y ago
> they would then they would have been the first not the last to implement this. Look at it this way, too: It's quite possible that before you get to performance savings by implementing `loading`, you may have a list of things a mile long that are higher on the priority. So, you solve those first. > Also try to search for "broken/not working in Safari" and you will see mostly people who develop and test on nothing but Chrome.
- simion314 5y ago
  >mostly people who develop and test on nothing but Chrome. Most developers can't test on Safari , I use Ff for dev (my colleagues use Chrome) nobody owns a Mac to test on it and there are Safari only issues or cool features that work in Ff and Chrome but not in Safari.