JS lazy loading is a thing of the past.
Just because some sites are slow to adopt, that doesn't make it a valid argument against lazy loading per se.
Native lazy loading is broadly supported, it works well, has no overhead, and you can override the behaviour if you always want eager loading.
There's no point in complaining about it that I am able to grasp.
I don't have data on this but I assume that JS lazy loading is dying rapidly because this is not a critical feature that must polyfilled for legacy browsers.
Of course, plenty of sites will keep their JS lazy loading cruft until the next code refactoring / optimization.
But I am very happy that native lazy loading has been standardized and implemented.
Native lazy loading is broadly supported, it works well, has no overhead, and you can override the behaviour if you always want eager loading.
There's no point in complaining about it that I am able to grasp.
I don't have data on this but I assume that JS lazy loading is dying rapidly because this is not a critical feature that must polyfilled for legacy browsers.
Of course, plenty of sites will keep their JS lazy loading cruft until the next code refactoring / optimization.
But I am very happy that native lazy loading has been standardized and implemented.