3 ms·

Ah, I clicked expecting developer-orientated techniques. Anyone has any resources he (or she) can recommend about writing faster, more efficient javascript? I'

Ah, I clicked expecting developer-orientated techniques. Anyone has any resources he (or she) can recommend about writing faster, more efficient javascript? I'm not a developer, I learned javascript to hack some things together and obviously I taught myself awful practices, but I can't identify/change them.

rajeevk 12y ago
I am not a full time javascript dev. A general advice: Code review a great tool to learn great practices. Get your code reviewed by some good developer and work on the comments. Sometime code review comments are very personal views of commenter, but in general they can be very helpful. You said that you taught yourself an awful practice. If you can identify a practice as awful, then probably you can fix it without help of anybody else by simply googling. In my opinion the real challenge is to identify a piece of code is awful or not. If you can identify, then probably it is much easier to correct that.
dccoolgai 12y ago
Follow Paul Irish and Addy Osmani for starters. Superherojs.com has a list of stuff to read in their "how browsers work" section... other than that, even the experts admit a lot of it is black magic - there are some fundamental things (dom access, writing is slow) but hard to nail down concrete things.
- rylee 12y ago
  Superherojs seems to be down for me.
  - dccoolgai 12y ago
    Hmm, likewise. Too bad that was one of my favorite reference things (though it was getting a bit dated).
    - graedus 12y ago
      Not quite as convenient, but at least you can still find the links here: https://github.com/superherojs/superherojs/blob/gh-pages/index.html https://github.com/superherojs/superherojs/blob/gh-pages/ind...
91bananas 12y ago
This is not only javascript related, but just good web page speed practices in general. Though it is old, most of it still fair game. http://yslow.org/ http://yslow.org/

rajeevk 12y ago

I am not a full time javascript dev. A general advice: Code review a great tool to learn great practices. Get your code reviewed by some good developer and work on the comments. Sometime code review comments are very personal views of commenter, but in general they can be very helpful. You said that you taught yourself an awful practice. If you can identify a practice as awful, then probably you can fix it without help of anybody else by simply googling. In my opinion the real challenge is to identify a piece of code is awful or not. If you can identify, then probably it is much easier to correct that.

dccoolgai 12y ago

Follow Paul Irish and Addy Osmani for starters. Superherojs.com has a list of stuff to read in their "how browsers work" section... other than that, even the experts admit a lot of it is black magic - there are some fundamental things (dom access, writing is slow) but hard to nail down concrete things.

rylee 12y ago
Superherojs seems to be down for me.
- dccoolgai 12y ago
  Hmm, likewise. Too bad that was one of my favorite reference things (though it was getting a bit dated).
  - graedus 12y ago
    Not quite as convenient, but at least you can still find the links here: https://github.com/superherojs/superherojs/blob/gh-pages/index.html https://github.com/superherojs/superherojs/blob/gh-pages/ind...

91bananas 12y ago

This is not only javascript related, but just good web page speed practices in general. Though it is old, most of it still fair game. http://yslow.org/ http://yslow.org/