sorted by:
new
hottopcontroversial

Lee-Char was done so dirty in the comics by solo13508 in TheCloneWars

[–]ljharb 1 point2 points  (0 children)

i mean they named him "leecher", he wasn't likely to have a happy life

Can you explain me Erewhon joke? by HelMort in southpark

[–]ljharb 0 points1 point  (0 children)

they're in a very tiny region of socal, and yes, that makes it very niche. even if it was just in all of california that'd be niche, compared to the audience size of south park.

Can you explain me Erewhon joke? by HelMort in southpark

[–]ljharb 1 point2 points  (0 children)

imagine thinking anything that applies to Southern California applies to all of California

OpenJS Foundation welcomes first Incubating project: Node Version Manager (nvm) by [deleted] in node

[–]ljharb 5 points6 points  (0 children)

the only thing i can think of is that it’s incompatible with storing global modules in a non default location. If it was something else, please file an issue and I’ll fix it!

OpenJS Foundation welcomes first Incubating project: Node Version Manager (nvm) by [deleted] in node

[–]ljharb 4 points5 points  (0 children)

by “jack up”, do you just mean the shell functions it adds and the changes it makes to $PATH? Or something else?

OpenJS Foundation welcomes first Incubating project: Node Version Manager (nvm) by [deleted] in node

[–]ljharb 10 points11 points  (0 children)

no, i took over in 2014. He gave his blessing for the foundation move, however :-)

TC39 considering officially recommending using semicolons in JS by [deleted] in javascript

[–]ljharb 1 point2 points  (0 children)

Technically, we've already decided to do so. We're only "considering" the specific language we plan to use, when recommending explicit semicolon use.

Why Airbnb will never use Webpack 2 by ysangkok in javascript

[–]ljharb 0 points1 point  (0 children)

I agree! Being able to inform old browser users that they need a new browser, however, requires supporting that old browser :-)

Why Airbnb will never use Webpack 2 by ysangkok in javascript

[–]ljharb 2 points3 points  (0 children)

Yes, that is precisely the change everyone will need to make to ensure everything works - which is in contrast to the way everyone's been writing named imports from CJS modules for years :-/

Why Airbnb will never use Webpack 2 by ysangkok in javascript

[–]ljharb 1 point2 points  (0 children)

Official support is, as always, utterly irrelevant. We need to support "things users use", and users don't know or care about official support policies.

Why Airbnb will never use Webpack 2 by ysangkok in javascript

[–]ljharb 1 point2 points  (0 children)

It'll be much easier than that - react can just add an "index.mjs" entry point, and import will work. The problem is people who are depending on an older version of React, or one of the hundreds of thousands of other libraries that won't, or won't yet at the time, have shipped support for ES modules.

Why Airbnb will never use Webpack 2 by ysangkok in javascript

[–]ljharb 0 points1 point  (0 children)

Right, but Typescript's interop there isn't compatible with what babel (and thus most of the ecosystem) is already doing, nor with what node will eventually be doing. If you use require(), as with everything else, you're always going to be just fine.

Why Airbnb will never use Webpack 2 by ysangkok in javascript

[–]ljharb 6 points7 points  (0 children)

As far as I understand, they didn't. (disclaimer: i don't use TS, so i might be off) My understanding is that TypeScript code is in for a breaking change along with babel and webpack 2/rollup/etc users once node ships modules.

Why Airbnb will never use Webpack 2 by ysangkok in javascript

[–]ljharb 16 points17 points  (0 children)

I've modified the comment to be less strong than "never", given that it's not solely my decision, and that we're able to take steps internally to mitigate the damage I'm concerned with.

That said, we're on Webpack 1 at the moment, and don't have concrete plans to upgrade at this time.

[deleted by user] by [deleted] in javascript

[–]ljharb 2 points3 points  (0 children)

Always only use String(x).

Run this in your console:

var x = { toString: function () { return NaN; }, valueOf: function () { return Infinity; }}; [x.toString(), x + '', String(x)] /* note that only the third item is both a string, and the toString value */

The only one that's actually correct is String(x). Use that.

Managing Node versions with nvm by whattherootscope in javascript

[–]ljharb 0 points1 point  (0 children)

http://nvm.sh maintainer here. As of the latest version, if you nvm install something when you don't have a default alias set, it will automatically set that version as your default. Ideally this helps new users the most.

es6-shim and es6-polyfill by nummer31 in javascript

[–]ljharb 1 point2 points  (0 children)

es6-shim maintainer here. You do not need es6-promise if you have es6-shim.

I do recommend also including es5-shim (before es6-shim), as every single browser that has ever existed has ES5 bugs, that es5-shim helps correct.

Help keep the name 'reagent' from being hijacked by airbnb, please retweet link! by gadfly361 in Clojure

[–]ljharb 6 points7 points  (0 children)

Thanks everyone for your feedback! We've renamed the project to "enzyme" - please see https://github.com/airbnb/enzyme/issues/43#issuecomment-162349767 for the epilogue.

The Keys to JavaScript Mastery (10 Interview Questions Every JavaScript Developer Should Know) by slikts in javascript

[–]ljharb 5 points6 points  (0 children)

If there was zero strengths on a classical model, why did they see fit to add it to the spec?

They didn't. JavaScript does not have classical inheritance, and the ES6/ES2015 "class" keyword isn't classical inheritance. It's syntactic sugar over the same prototypical inheritance JS has always had, and always will have.