Front End Development Guidelines • Hacker News Board

Re: Front End Development Guidelines

#41

Post by warfangle » Fri, May 06, 2011, 3:50 PM UTC

timdown wrote: post #34

warfangle wrote: post #28

I'd like to point out that if jQuery fell back to the fundamental Array.prototype.forEach function when available, $.each would be /much/ faster than a for loop. Array.prototype.forEach, when available, is native code.

No. forEach() being native doesn't prevent it from generally being slower than a foor loop, because it still has to do a function call on every iteration.

It depends on what you're doing within the loop. With a for loop, you still have to perform an array lookup. For something simple, like summing up all the numbers in an array, forEach is definitely faster. Try JSLitmus'ing it.

Re: Front End Development Guidelines

#42

Post by lhnn » Fri, May 06, 2011, 3:51 PM UTC

thaumaturgy wrote: post #29

evanwalsh wrote: post #24

"Javascript code requires regular commenting in order to make it easily understandable." Or you could, you know, just make code that's understandable. I'm such an Internet jerk.

I usually aim to make code that solves the problem it was intended to solve, as elegantly as possible. (Where elegance correlates closely to efficiency.) Whether it's understandable or not is completely secondary. Often this means that if I don't leave myself a reasonable comment about what I'm doing in that spot and why, I'll relearn the importance of good comments later.

What you're describing is often considered to be good code. Maintainability is quite often the most important thing when it comes to coding. Cryptic code, though sometimes a tad bit harder to understand, is often preferable when it substantially increases the performance of the application. Short, descriptive comments do the rest of the work for the maintainer.

Re: Front End Development Guidelines

#43

Post by jgv » Fri, May 06, 2011, 4:25 PM UTC

Kind of surprised that there's no love for sass/scss here. Scss has made producing css a delight and v3.1 was just released which is great. Any front end developer who hasn't given it a shot should try it at least once.

Re: Front End Development Guidelines

#44

Post by joshontheweb » Fri, May 06, 2011, 4:49 PM UTC

julian37 wrote: post #38

fuzionmonkey wrote: post #15

Earlier quoted context omitted.

I think the idea is that if you use single quotes for strings, you don't have to escape the double quotes that are often found in html. ' something ' But the same goes for something like "you can't do that" I guess it just depends what you don't want to escape. For Google, the more probable scenario was probably the former.

The former isn't a very good reason: HTML/XML accept both double and single quotes, so " something " would work equally well.

yes, but it is much more common for double quotes to be used in html

Re: Front End Development Guidelines

#45

Post by joshontheweb » Fri, May 06, 2011, 4:52 PM UTC

I remember awhile back another post kinda like this where it was a companies new front end dev training material. Anyone remember that or have a link? I've been trying to find it.

Re: Front End Development Guidelines

#46

Post by pbreit » Fri, May 06, 2011, 6:17 PM UTC

Painbird wrote: post #4

This looks good - however some of the language used is a bit interesting. I laughed when I read "chain like a sick bitch" but I believe most people (especially young kids, who will benefit from this the most) may see it as a bit aggressive / over the top.

I was a little off-put by the inclusion of that phrase.

Re: Front End Development Guidelines

#47

Post by zerok » Fri, May 06, 2011, 6:25 PM UTC

jgv wrote: post #43

Kind of surprised that there's no love for sass/scss here. Scss has made producing css a delight and v3.1 was just released which is great. Any front end developer who hasn't given it a shot should try it at least once.

Indeed. But perhaps the author can't decide or doesn't want to recommend SASS over LESS and vice versa.

Re: Front End Development Guidelines

#48

Post by ricardobeat » Fri, May 06, 2011, 11:00 PM UTC

zmmmmm wrote: post #8

Nice guide & nicely written! This example snippet actually generates a Javascript error (at least, in IE9): var foo = null; // foo is null, but bar is undefined as it has not been declared if (foo == null && bar == null) { // still got in here } It will work if bar is declared but has value undefined , but not if bar is completely undeclared as shown.

common error.

  typeof bar === 'undefined'

Re: Front End Development Guidelines

#49

Post by julien_p » Sat, May 07, 2011, 10:59 AM UTC

joshontheweb wrote: post #45

I remember awhile back another post kinda like this where it was a companies new front end dev training material. Anyone remember that or have a link? I've been trying to find it.

Not sure if this is what you're looking for, but it covers very similar material http://na.isobar.com/standards/

Re: Front End Development Guidelines

#50

Post by joshontheweb » Sun, May 08, 2011, 4:50 AM UTC

julien_p wrote: post #49

joshontheweb wrote: post #45

I remember awhile back another post kinda like this where it was a companies new front end dev training material. Anyone remember that or have a link? I've been trying to find it.

Not sure if this is what you're looking for, but it covers very similar material http://na.isobar.com/standards/

Im not sure if this is the one or not, but definitely a great resource and more or less what I was looking for, thanks.