undefined | Better HN

0 pointsarendtio4y ago0 comments

The difference is that in the backend you have control over the runtime environment. In the frontend you don't.

However, because frontend devs know that, they have build tools to support them. It started with jquery as an cross browser abstraction and has grown to a whole eco system ranging from websites like caniuse.com to editor plugins that check for features based on the current browser shares and your specific selection (e.g. browserlist) up to test-farm services like browserling.

I think what makes frontend development harder, is that standards carry a lot of legacy (you can't just redesign CORS and 3rd party cookies) and that you have a very diverse set of runtime environments with very different capabilities.

0 comments

3 comments · 1 top-level

exikyut4y ago· 2 in thread

> check for features based on the current browser shares

TIL! That sounds awesome. What are these called? :D

arendtioOP4y ago

Browserlist [1] makes use of the browser market shares and you can use it with plugins such as eslint-plugin-compat [2].

[1] https://github.com/browserslist/browserslist [2] https://github.com/amilajack/eslint-plugin-compat

joshxyz4y ago

More here at https://kangax.github.io/compat-table/es6/

j / k navigate · click thread line to collapse