Board Thread:Support Requests - Getting Technical/@comment-1852193-20200313053705/@comment-9605025-20200313072001

I already do use Chrome because of this.

Regarding includes, both arrays and strings have indexOf which can easily be used in-place of includes and is IE compatible. So perhaps comparing includes to matches was a poor choice on my part.

Fair point about performance. However, the exact implementation of the specs is up to browser devs. Using matches v. includes as an example, what is stopping them from just redirecting string arguments from matches to includes? If they did that, then you could just call matches and, if the input happens to be a string, it benefits from the performance of includes.

Lastly, there are things called transpilers. Let's say you disagree with all of my previous points and still think the devs should always use the latest and greatest even at the cost of comparability. How about this? Write your code using the latest and greatest but then use a transpiler to create an ES5-compliant version. When a user comes to your site, just to a quick check of what their browser supports and import the corresponding set of scripts. Perhaps something like this (substitute importArticles for the import method of choice):