8 Matching Annotations
- Mar 2021
-
github.com github.comd3/d31
-
No d3 global is exported if AMD or CommonJS is detected.
-
- Feb 2021
-
dry-rb.org dry-rb.org
-
Another solution is using the Safe Navigation Operator &. introduced in Ruby 2.3 which is a bit better because this is a language feature rather than an opinionated runtime environment pollution
-
- Nov 2020
-
css-tricks.com css-tricks.com
-
Internal Sass features have also moved into the module system, so we have complete control over the global namespace.
-
- Oct 2020
-
github.com github.com
-
// Use `noConflict` to restore the pre-fp variant. var fp = _.noConflict();
-
-
humanwhocodes.com humanwhocodes.com
-
github.com github.com
-
Polyfills are naughty as they patch native APIs, while ponyfills are pure and don't affect the environment.
-
How are ponyfills better than polyfills? A polyfill is code that adds missing functionality by monkey patching an API. Unfortunately, it usually globally patches built-ins, which affects all code running in the environment. This is especially problematic when a polyfill is not fully spec compliant (which in some cases is impossible), as it could cause very hard to debug bugs and inconsistencies. Or when the spec for a new feature changes and your code depends on behavior that a module somewhere else in the dependency tree polyfills differently. In general, you should not modify API's you don't own.
-
- Sep 2020
-
en.wikipedia.org en.wikipedia.org
-
protect against polluting the global environment
-