| ▲ | crabmusket 4 days ago | |
> Checking the existence of features and polyfilling is not that complicated. Judging by what we see in the world, most developers don't agree with you. And neither do I. A handful of browsers, multiplied by many versions per browser in the wild (before evergreen browsers like Chrome became widespread, but even today with e.g. Safari, or enterprise users), multiplied by a sprawling API surface (dare I say it, a standard library) is not trivial. And that's not even considering browser bugs and regressions. > very hypocritical of developers that won't blink Not a great argument, as developers don't necessarily get to choose how to add analytics, and plenty of them try to push back against doing so. Also, the cost of parsing and JIT'ing JS code is byte-for-byte different to the cost of decoding an image. | ||
| ▲ | skydhash 3 days ago | parent | next [-] | |
> Judging by what we see in the world, most developers don't agree with you. And neither do I. From my POV, most developers just test on the most popular browser (and the latest version of that) without checking if the API is standard or its changelog. Or they do dev on the most powerful laptop while the rest of the world is still on 8gb, FHD screen with integrated gpu. | ||
| ▲ | typpilol 3 days ago | parent | prev [-] | |
Explain browser defaults to non JavaScript people is kind of eye opening I've found | ||