Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

A Modern JavaScript Tutorial

javascript.info

Post reply on HN
Print view View original

61–70 of 299 posts

Re: A Modern JavaScript Tutorial

#61

Post by joshxyz »

emmanueloga_ wrote: post #50

Looks really nice, although ... For as good as the TOC and layout is, there's always something I miss when I read books from a website. I miss the spatial context: how much material I already covered? How much is left? I like the linearity of regular books (that includes PDFs). If the book is a website the next best thing for me is when the whole thing is just a single page. Worst thing are epubs :-p (hate the way th…

I think comparing gaps with exploringjs.com (separated by ecmascript versions) would be worth a shot.

Re: A Modern JavaScript Tutorial

#63

Post by hutzlibu »

wa1987 wrote: post #54
hutzlibu wrote: post #29

Earlier quoted context omitted.

"Just like it's better to understand how prototypal inheritance works in JS BEFORE even using a single class declaration. " About that, does JS class inheritance now work like classes in java for example? Or is it still just syntactic sugar for the prototype inheritance? By your wording, I assume the later?

Well, it's complicated :-) https://stackoverflow.com/questions/36419713/are-es6-classes...

Wow. I was hoping, at some point things would improve a bit.

Re: A Modern JavaScript Tutorial

#64

Post by wolfadex »

simonw wrote: post #40
cosmotic wrote: post #30

Oh no! It's already out of date! (That's a JS changes too fast joke) But seriously, calling it 'modern' is pointless. It's not adding anything valuable and its just going to become out of date (and thus wrong).

Disagree. I've been writing JavaScript for twenty years, and I'm very aware that there's a lot of "new" stuff that I need to brush up on. When I saw it call itself "modern" I instantly assumed that it would be covering the kind of information I need to know.

I, as a JS dev of 10+ years, wouldn't consider this "modern". I didn't see

- for in loop - for of loop

as a couple examples, and those have been around for at least a few years now. There's probably more missing too. To what the above person said. The usage of "modern" or "latest" or similar is going to fall behind and make for bad searching.

Re: A Modern JavaScript Tutorial

#65

Post by ragnese »

hutzlibu wrote: post #29
throw_m239339 wrote: post #19

Earlier quoted context omitted.

> The default way promises are used is now async/await. `.then()` should not be introduced as anything more than 'you may find this in older codebases'. No, because you might have to write explicit promises in the browser with async API that are callback based. You need to understand how promises work to use async/await at first place anyway. Just like it's better to understand how prototypal inheritance works in JS…

"Just like it's better to understand how prototypal inheritance works in JS BEFORE even using a single class declaration. " About that, does JS class inheritance now work like classes in java for example? Or is it still just syntactic sugar for the prototype inheritance? By your wording, I assume the later?

Correct. It's still prototype based. Thus making the class keyword actually MORE confusing for people from other languages, IMO.

Re: A Modern JavaScript Tutorial

#66

Post by wa1987 »

hutzlibu wrote: post #63
wa1987 wrote: post #54

Earlier quoted context omitted.

Well, it's complicated :-) https://stackoverflow.com/questions/36419713/are-es6-classes...

Wow. I was hoping, at some point things would improve a bit.

Agreed. I find myself using a pretty small subset of the language which definitely doesn't include the class keyword. Doubt I'll ever find it useful.

Re: A Modern JavaScript Tutorial

#68

Post by 0df8dkdf »

cosmotic wrote: post #30

Oh no! It's already out of date! (That's a JS changes too fast joke) But seriously, calling it 'modern' is pointless. It's not adding anything valuable and its just going to become out of date (and thus wrong).

to be fair. anything after 'use strict' can be consider 'modern'. However with the rate ES7 - 10 is going. Yeah this wouldn't be modern.

Re: A Modern JavaScript Tutorial

#70

Post by brundolf »

cosmotic wrote: post #30

Oh no! It's already out of date! (That's a JS changes too fast joke) But seriously, calling it 'modern' is pointless. It's not adding anything valuable and its just going to become out of date (and thus wrong).

Nothing will become inaccurate, because JS never introduces breaking changes.

The guide might come to lack some newer things over time, but I doubt those will include any major paradigm shifts, because the past ~10 years have likely been the most dynamic that JS will ever see in terms of idioms and best-practices. JS made a radical shift into a mature language, and now it is mostly on the other side of that transition. So writing a "modern" (post-transition) tutorial makes perfect sense to me, and I don't think it will become irrelevant any time soon.

Post reply on HN