I don’t think the constructor/factory logic is necessary at all, as long as you change how you think about Object-Oriented Programming. In my recent exploration of the topic, I’ve discovered that Prototypical inheritance lends itself more to defining a set of functions that use particular data. This isn’t a foreign concept to those trained in … Read more
In IE<9, .toStringing (function (x) {return x*x;}) gives “(function (x) {return x*x;})” While in chrome it gives: “function (x) {return x*x;}” If you compare: “function (x) {return x*x;}” > “1,2,3” // true “(function (x) {return x*x;})” > “1,2,3” // false Which is effectively the same as comparing: “f” > “1” “(” > “1” Which is … Read more
No, not for now 🙁 From the CoffeeScript FAQ: Q: Will you add feature X where feature X depends on a platform? A: No, implementation-specific features are not allowed as a policy. Everything that you write in CoffeeScript should be supported and runnable on any current JavaScript implementation (in practice, this means the lowest common … Read more
Your cryptic part isn’t all that cryptic if you rewrite it a little: [][”] [] will be coerced into a string because it isn’t an integer, so you’re looking for a property of [] with the name ” (an empty string). You’ll just get undefined, as there is no property with that name. As for … Read more
That is not actually a babel issue, you are just trying to run CommonJS code (transpiled from ES6 export) in the browser without preparation. CommonJS doesn’t run on the browser, you need to use a tool to package it for the browser, such as Webpack or Browserify. Just by coincidence this week I created a … Read more
var ES6Promise = require(“es6-promise”); ES6Promise.polyfill(); var axios = require(“axios”); writing this above axios worked for me maybe other options also worked it was mainly a cache issue in IE that i was facing installing es6-promise-promise webpack plugin also worked npm install es6-promise-promise and include new webpack.ProvidePlugin({ Promise: ‘es6-promise-promise’, // works as expected }); in webpack … Read more
The difference between let and const is that once you bind a value/object to a variable using const, you can’t reassign to that variable. In other words Example: const something = {}; something = 10; // Error. let somethingElse = {}; somethingElse = 1000; // This is fine. The question details claim that this is … Read more
According to this Github page the shims include all monkey-patches that faithfully represent the ES5 features. In other words: you can use the features provided by these files as if you were using ES5 proper. The shams, however contain those features that can not be emulated with other code. They basically provide the API, so … Read more
tl;dr The second (0, eval)(‘var a = 1;’); case is in fact not a direct call. You can see this more prevalently in: (function(){ “use strict” var x = eval; x(“var y = 10”); // look at me all indirect window.y;// 10 eval(“var y = 11”); window.y;// still 10, direct call in strict mode gets … Read more
It appears to be O(n) in V8 (chrome, node.js) at least: > var hash = {} > , c = 0; > > var s = +new Date();Object.keys(hash);console.log(+new Date() – s); 0 > for(var i=0; i<100000; i++, c++){ hash[c] = 1; } > var s = +new Date();Object.keys(hash);console.log(+new Date() – s); 26 > for(var i=0; … Read more