Apple JavaScript Coding Guidelines [pdf] • Hacker News Board

Re: Apple JavaScript Coding Guidelines [pdf]

#11

Post by Hovertruck » Tue, Jul 05, 2011, 8:03 PM UTC

coyul wrote: post #5

Hovertruck wrote: post #2

I find it strange that the "Global Scope Considerations" section uses Ruby-style inline comments (#) rather than actual JS inline comments (//).

I find it strange that you refer to comments starting with # as Ruby-style comments.

Or any other language that denotes comments with an octothorpe, but I opted for brevity.

Re: Apple JavaScript Coding Guidelines [pdf]

#12

Post by lucaswoj » Tue, Jul 05, 2011, 8:07 PM UTC

I have a strong reason to suspect that this was written by an intern who was relatively new to the language. It seems to be written by someone in the C/C++/Java mindset (ie how they didn't list "function" as a primitive data type)

Re: Apple JavaScript Coding Guidelines [pdf]

#13

Post by adolph » Tue, Jul 05, 2011, 8:21 PM UTC

yalogin wrote: post #10

foobarbazoo wrote: post #9

Man, what a piece of shit. Apple should pull this immediately.

Good that I saw this before reading the pdf. Can you point me to a better resource?

As seen elsewhere in the comments, Crockford's is very good:

http://javascript.crockford.com/code.html

Re: Apple JavaScript Coding Guidelines [pdf]

#14

Post by lucaswoj » Tue, Jul 05, 2011, 8:27 PM UTC

The example in this document of using the delete operator on a function is wrong.

http://perfectionkills.com/understanding-delete/

Re: Apple JavaScript Coding Guidelines [pdf]

#15

Post by jmreid » Tue, Jul 05, 2011, 8:28 PM UTC

Two years old?

Re: Apple JavaScript Coding Guidelines [pdf]

#16

Post by chc » Tue, Jul 05, 2011, 8:38 PM UTC

coyul wrote: post #5

Hovertruck wrote: post #2

I find it strange that the "Global Scope Considerations" section uses Ruby-style inline comments (#) rather than actual JS inline comments (//).

I find it strange that you refer to comments starting with # as Ruby-style comments.

I'm pretty sure Ruby is bigger than Perl and sh put together now, at least in mindshare.

Re: Apple JavaScript Coding Guidelines [pdf]

#17

Post by Tomek_ » Tue, Jul 05, 2011, 9:28 PM UTC

Already discussed in http://news.ycombinator.com/item?id=1854783 with the same consensus, it's a terrible guide. Read Crockford, Stoyanov, Bolin instead.

Re: Apple JavaScript Coding Guidelines [pdf]

#18

Post by blahpro » Tue, Jul 05, 2011, 9:38 PM UTC

It’s shocking that this document refers to "classes". JavaScript doesn’t even have classes.

Re: Apple JavaScript Coding Guidelines [pdf]

#19

Post by encoderer » Tue, Jul 05, 2011, 10:01 PM UTC

blahpro wrote: post #18

It’s shocking that this document refers to "classes". JavaScript doesn’t even have classes.

Why is this comment deprecated? He's absolutely right, if a little late to the party. Shockingly bad document from Apple.

Re: Apple JavaScript Coding Guidelines [pdf]

#20

Post by neimado » Tue, Jul 05, 2011, 10:02 PM UTC

foobarbazoo wrote: post #9

Man, what a piece of shit. Apple should pull this immediately.

I agree. Also they aren't using 1TBS for the code examples, and that will naturally lead to noob javascript programmers running into trouble when they inevitably type

  return  
  {
    hello:"world"
  }

using 1TBS will naturally lead the programmer to type the correct javascript syntax

  return {  
    hello:"world"
  }

1TBS is naturally a better fit for javascript programming.