Note on the "Don't use reserved words as keys" about javascript HOT 4 CLOSED

Even though you might not need to support IE8, I still see this as good practice. "default" is a case that might look nice, but if you disagree with this entirely then you could end up with:

var superman = {
  var: { clark: 'kent' },
  function: true,
  for: 'yup',
  if: 'then',
  else: false
};

The syntax works, but seeing that in code can be confusing.

from javascript.

Well I don't agree, it doesn't look confusing to me. But anyway this is not
my point actually. My real point is it is important not to sacrifice
code quality because of broken software, but to fix the software. Of course
we can have different opinion on what "code quality" is, but this is not my
point, my point is only about renaming something that you would normally
name otherwise because of IE8.

On Fri, Nov 8, 2013 at 3:57 AM, Ross Allen [email protected] wrote:

Even though you might not need to support IE8, I still see this as good
practice. "default" is a case that might look nice, but if you disagree
with this entirely then you could end up with:

var superman = {
var: { clark: 'kent' },
function: true,
for: 'yup',
if: 'then',
else: false};

The syntax works, but seeing that in code can be confusing.

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/98#issuecomment-28025798
.

from javascript.

We still have to support IE8 at Airbnb so it's our best practice. When we drop support for IE8 we will be sure to update the guide.

from javascript.

This is important for the guide, and I believe it makes sense. Of course if you address a different context (like top smartphones, browsers) might not matter.

Regargind IE8: the browser still matters if you provide a critical worldwide product to your customers. Can't tell half China to upgrade and lose money.

from javascript.