91–100 of 119 posts
open up chrome console, type `class Foo { }` and it works now out of the box. For what it's worth, when you try define a class that already exists. it throws an error. It seems that re-defining an identifier with the `var` keyword will throw an error too. I don't remember this being the case before.
So, today I'm using babel to transpile my code to es5. Anyone know of any good tooling to use transpiled code for older browsers and es6 for newer?
It'd be nice to see support similar to Autoprefixer[1]'s use of Browserlist queries[2]. Those let the developer to specify the desired target platforms by browser versions, by global usage stats (e.g. '> 5%'), or by custom usage stats ('> 5% in my stats') etc., and derive the correct prefixes needed to deploy to those targets. EDIT (for clarity): It'd be great to see similar query support to derive a "lowest common d…
Also https://twitter.com/samccone/status/722826060161617923.
Earlier quoted context omitted.
If you're using Babel already, WebKit hitting 100% support is irrelevant. IE is going to be the thing that prevents us from running ES6 natively in the browser for several years more.
I was going to reply it wasn't that long, until i realized ie will be around in meaningful numbers for another 4 years. Windows 7 is supported until 2020, and IE is the only game in town there for enterprises. The new distribution policies of w10 will mean plenty of places will run out the clock on w7 support. So, yeah, I guess we're supporting IE 11 for half a decade to come.
IE11 is the new IE6 and will be around a long time in enterprise. Thank you Microsoft. It's epecially annoying as Edge is based just on a refactored and improved trident engine after all, so basically IE12 html engine under hood (and was already called "Edge" in DevTools in IE11).
Maybe now they can fix all their layout bugs they've been adding to the browser and not fixing.
Earlier quoted context omitted.
I think that was fixed in the last TP.
I don't think I'll be able to handle any instability in that right now. My primary development focus doesn't involve web development so having the latest and greatest browser won't benefit me that much. I do want to try the latest features, but I have patience and can wait a few more months.
Earlier quoted context omitted.
It probably could be, but we deliberately don't do it, because: 1) I'm not aware of complaints about the change to error.stack behavior from users or developers. I don't know of an app that broke because of the change to error.stack. I don't know of an app whose telemetry got messed up because of the change to error.stack. So, we don't have a real-world test case that would be improved or fixed by integrating ShadowC…
I will bite the bullet: Do you have a sense of how many devs use Safari compared to Chrome/FF for debugging?
Even if were the worst engine since IE4, it's Not Chrome(tm) and can help when chrome dev tools fail (or - more likely - I fail at working with chrome dev tools and need a fresh perspective.)
It's also good practice to run the profilers at least occasionally, because (a) performance in Safari is relevant and I've been bitten by idiosyncrasies where one browser took >5x than another (in all directions. And (b), as above, just by being different they may add useful information.
Earlier quoted context omitted.
How does tail call optimization cause a regress in performance? Superficially, it seems very counter-intuitive that this should even be possible.
Messes with calling conventions. Citing Rust: https://mail.mozilla.org/pipermail/rust-dev/2013-April/00355...
I'm 99% super confident that this is an almost optimal solution.
tfw when "complete" has degrees. sigh. I'm 99% super confident that this is an almost optimal solution.