add no transpile

Author: Walle Cyril

html/use_es2015_strategies.md

@@ -1,11 +1,11 @@
-# Strategies for using ES2015+
+# Strategies for using ES2015+ for the browser
 
 There are various ways to deliver a functioning web app while using ES2015+ JavaScript as a development language.
 
 
 ## Build overview
 
-
+ * Transpile nothing
  * Transpile everything
  * Multiple builds
  * Multiple front ends
@@ -24,19 +24,35 @@ There are various ways to deliver a functioning web app while using ES2015+ Java
 
 ## Build
 
+## Transpile nothing
+
+Only build and minify in the build step. Makes sense when target audience uses new browsers, or when the web app relies on features that are only available in new browsers anyway.
+
+
+### Advantages
+
+Easiest to set up and understand.
+
+
+### Disadvantages
+
+The developer has to manually track sets of features that are available in a high enough percentage to be used. Older browser will not be supported unless a fallback is used.
+
+
 ## Transpile everything
 
+
 Generate a single ES5 file (depending on your target).
 
 
 ### Advantages
 
-Easiest to set up and understand.
+Easy to set up and understand.
 
 
 ### Disadvantages
 
-Probably a certain number of users use a modern browser that understands modern ES2015+ syntax and download unnecessary polyfills and more, which slows down page load compared to Multiple builds.
+Probably a certain number of users use a modern browser that understands modern ES2015+ syntax and download unnecessary polyfills and more, which slows down page load compared to Multiple builds. Also some features, may be inefficient after transpilation like `for of loops`.
 
 
 
@@ -178,6 +194,12 @@ A polyfill in JavaScript is a back-port of a standard feature for not yet up to
 Submit an issue or a pull request.
 
 
+
+## Notes
+
+Written in late 2017. Might be obsolete in 2020-2025
+
+
 ## Links
 
  * [script type module for ES2015](https://philipwalton.com/articles/deploying-es2015-code-in-production-today/)