4 ms·
> The sunsetting of IE11 and the rise of evergreen browsers that implement the latest JavaScript standard means that developers can once again run standard Jav
by codedokode 4y ago
> The sunsetting of IE11 and the rise of evergreen browsers that implement the latest JavaScript standard means that developers can once again run standard JavaScript code without transpilation.
This is a wrong assumption. There are lot of smartphones that do not get updates and have browsers that can be several years old.
Therefore transpiling and polyfills are not going away anywhere soon.
Of course, supporting different browsers can insignificantly increase development costs. It might be impractical to try to support Internet Explorer 7. A safe and reasonable choice would be to make sure that site looks and works perfectly in any browser released 5 years ago and is usable in a 10-year old browsers.
Obviously there are cases when this rule can be amended, for example, if you are making a game requiring a fast GPU and a mouse, then you can ignore smartphones and old browsers. But for a general website, like a corporate website, an online store, a social network, this seems like a sane default choice. You can extend support to 12-15 years old browsers if you feel confident in your skills.
- asddubs 4y agoI think it doesn't really matter one way or the other, anyway. Even if it takes 10 years to proliferate, at some point in the future, it'll be 10 years from now, and we'll be able to use it. depending on your usecase, maybe sooner.
- laurencerowe 4y agoI still expect most people would bundle and minify the code shipped in production but removing the requirement to setup a transpiler for development would be a huge win for developer ergonomics. For many smaller projects that bundling step may then simply be `deno bundle index.js` or similar.