_getify

7 ms·

31.
by _getify 11y ago
> `var` is broken Nonsense. Revisionism at its finest. But that's an argument I made in a different blog post: http://davidwalsh.name/for-and-against-let > It would be nicer to have real, deep immutability, but `
32.
by _getify 11y ago
What you're thinking about in ES6 is called "function name inference" and only refers to certain forms, like this one, where the name -- PURELY FOR DEBUGGING -- can be inferred. Actually, it goes for all assignments, `var`, `
33.
by _getify 11y ago
Except that any variation of these doesn't produce the same thing as a declaration, since function declarations hoist and function expression assignments do not. Most people don't like hoisting -- and I agree that variable hoistin
34.
by _getify 11y ago
Yeah, see, this is exactly the problem. I think most developers assume the latter, when the former is all that's meant according to JS. I don't think the former is all that useful, and the latter is super useful but `const` doesn&
35.
by _getify 11y ago
> Why not use `const` as default? The argument I made toward the end of the post is that refactoring from `const` back to `let` is more risky than the other way around. Moreover, surveying my own code, honestly, the vast majority of my d
36.
by _getify 11y ago
disclosure: self submission
37.
Constantly Confusing ‘const’(blog.getify.com)
33 points by _getify 11y ago|51 comments
38.
by _getify 11y ago
If we're gonna go that route, I still like "middle-end" JS better. :)
39.
by _getify 11y ago
disclosure: self submission
40.
Unimorphic Isoversal JavaScript What?(blog.getify.com)
13 points by _getify 11y ago|7 comments
41.
by _getify 11y ago
> If the threads and their scheduling are implemented wholly by the language There's just one thread, one event loop, for all of JavaScript... so we're not talking about true thread-level race conditions. > strongly implying
42.
by _getify 11y ago
But the article is not about the precision of timers happening at exact moments. It's about the nature of their relative timings. I don't see why the OS would need to be involved in the latter.
43.
by _getify 11y ago
disclosure: self submission
44.
Well, actually; Not all semicolons(blog.getify.com)
1 points by _getify 11y ago|1 comments
45.
ES6: Features by Testing(davidwalsh.name)
1 points by _getify 11y ago|0 comments
46.
JavaScript Coercions Grid(getify.github.io)
2 points by _getify 12y ago|0 comments
47.
by _getify 12y ago
Great point! The order of titles listed here is the intended reading order: https://github.com/getify/You-Dont-Know-JS/blob/master/READM... Also, the "Up & Going" title, Chapter 3, has desc
48.
by _getify 12y ago
That is exactly my intent. I certainly hope the books live up to that vision.
49.
by _getify 12y ago
The books point all the arcane points of the language so that the reader can understand them. They're also full of commentary like "never do this". Rather than most books which gloss over the "bad parts", which prev
50.
by _getify 12y ago
I understand and appreciate your feedback. Unfortunately, given that most of the series is done and half of them are already in print, it's too late to change. I did have lengthy discussions with my book editor about the title and its
51.
by _getify 12y ago
fyi: there were some who felt that it would detract from or dillute the brand "the good parts", which is also an oreilly title.
52.
by _getify 12y ago
> For the love of God please don't put a giant headed person on your cover though These are what the covers of all the books in the series look like: http://shop.oreilly.com/product/0636920026327.do ------ side
53.
by _getify 12y ago
> each $20 I'm trying to work with O'Reilly to bring down the prices on the books a little bit. I always wanted them to be priced so that price wasn't a barrier to entry. As you can imagine, there's lots of intricate
54.
by _getify 12y ago
Also note that these books are available for purchase as actual official ebooks. If you read the content and find it helpful, I of course appreciate any purchases made. :)
55.
by _getify 12y ago
Just wanted to say I appreciate any contributions (even "tiny tiny bit") you've made on GH. :)
56.
by _getify 12y ago
The book series (6 of them) is drafted, and to some extent edited, on GitHub. What you see is what you get. There are some edits and refinements that happen to the content during the publishing/production phase at O'Reilly that ar
57.
by _getify 12y ago
The proposition that I approach JS from, including my writing of these books, the JS workshops I teach, my OSS work, etc, is this: If you're going to make JS your primary language that you write on a daily basis, doesn't it make s
58.
by _getify 12y ago
> I found very little to suggest Just curious what parts you looked at? Did you glance at the table of contents, or did you read full chapters? I certainly tried to reveal in every chapter several different things that, in my professiona
59.
by _getify 12y ago
the game was a play on that phrase, and my book title is a play on both. :)
60.
by _getify 12y ago
I explain the title, and the intended tone and purpose of the book series, in the preface. If you wouldn't mind taking the 3 minutes to read it, I'd be curious if it changes anything about your opinion of the title: https:/&

More ›