From b3e97a7e45758735fbda111cdff8dab2594253d9 Mon Sep 17 00:00:00 2001
From: Ivo Georgiev <ivo@strem.io>
Date: Mon, 28 Jan 2019 20:55:11 +0100
Subject: [PATCH] browser-support: warn about the performance hit of using the
 polyfill~

---
 guide/src/reference/browser-support.md | 4 ++++
 1 file changed, 4 insertions(+)

diff --git a/guide/src/reference/browser-support.md b/guide/src/reference/browser-support.md
index 7362ea61..c9f4c5b7 100644
--- a/guide/src/reference/browser-support.md
+++ b/guide/src/reference/browser-support.md
@@ -44,6 +44,10 @@ also like to be aware of it!
      };
      ```
 
+     **Warning:** doing this implies the polyfill will always be used,
+     even if native APIs are available. This has a very significant
+     performance impact (the polyfill was measured to be 100x slower in Chromium)!
+
   2. If you're not using a bundler you can also include support manually by
      adding a `<script>` tag which defines the `TextEncoder` and `TextDecoder`
      globals. [This StackOverflow question][soq] has some example usage and MDN