_getify

11 ms·

61.
by _getify 12y ago
Yes, that was my intended (subtle) joke.
62.
Iterating ES6 Numbers(blog.getify.com)
1 points by _getify 12y ago|0 comments
63.
by _getify 12y ago
I'm honored to see people are finding it useful! The truth is, we all don't really fully know JS, and we all need to work on knowing it better. The books are my way of learning it, and hoping that others can learn along with me.
64.
by _getify 12y ago
Thanks for the idea. I'll pass that along to my editors at O'Reilly. :)
65.
by _getify 12y ago
There will be once I get the book series finished (five titles expected). :)
66.
by _getify 12y ago
glad you caught the joke. :)
67.
by _getify 12y ago
Of course, if this movement took off, I would absolutely want to come up with a defined list/scope for our efforts.
68.
by _getify 12y ago
As soon as I get a a github repo for this thing, I'll happily accept your PR to change to 01/10/11111100010. :)
69.
by _getify 12y ago
Yes, "how we get into this mess" is incredibly complicated and yet far too much a "pit of failure" for developers. But that doesn't mean we have to just accept it'll never change. I take a sense of pride and ow
70.
by _getify 12y ago
Sure. But the web is well past its infancy, its hype curve, etc. It doesn't need "help" to find adoption. It made it. Now it's time for maturity, in my opinion. I just think this is one way of going about shuffling off s
71.
by _getify 12y ago
> I love the implicit assumption that the standards-of-the-moment are any better. Of course they are objectively "better" (by almost any measure) than the mixed old-and-new-that-conflict crap we have. Is the "new new"
72.
by _getify 12y ago
We've tried "document modes" before, and it was terrible. And it's even worse for JS and CSS. > Is it really worth breaking all legacy websites? In any organization, this question gets asked of their product's te
73.
by _getify 12y ago
In particular, lots of legacy JS bugs that we can't get rid of since people "rely" on them. Also, the biggest one that spurred me to launch this today is all the proprietary -webkit- CSS prefix stuff, especially the non-stand
74.
by _getify 12y ago
What's a date you're free? :)
75.
International “Break The Web Forward” Day(breakthewebforward.com)
19 points by _getify 12y ago|17 comments
76.
Promises: The Extension Problem (part 4)(blog.getify.com)
4 points by _getify 12y ago|0 comments
77.
Promises: The Trust Problem (part 3)(blog.getify.com)
3 points by _getify 12y ago|0 comments
78.
Promises: The Inversion Problem (part 2)(blog.getify.com)
2 points by _getify 12y ago|0 comments
79.
Promises: The Sync Problem (part 1)(blog.getify.com)
3 points by _getify 12y ago|0 comments
80.
by _getify 13y ago
OK, draft figures posted now. https://github.com/getify/You-Dont-Know-JS/tree/master/this%...
81.
by _getify 13y ago
A super quick, simple illustration of the difference, which comes down to the fact that delegation is differential, whereas composition is complete: https://gist.github.com/getify/9895188 For a bit more "real worl
82.
by _getify 13y ago
OLOO is quite different from both inheritance and composition. It embraces delegation rather than covering it up or running away from it. :)
83.
by _getify 13y ago
They're coming. It's an artifact of working with a book publisher and the art department and all that. Sorry for the confusion.
84.
by _getify 13y ago
Huge fan of this article. Makes some really great points! Wish I could share and vote it up a thousand times. :) I have been writing about exactly this topic, of why classes don't make sense (specifically for JS), in my second title of
85.
Optimizing Visual Updates(blog.getify.com)
1 points by _getify 13y ago|0 comments
86.
Adaptive Hybrid JavaScript(blog.getify.com)
3 points by _getify 13y ago|0 comments
87.
by _getify 13y ago
> In Q1 2013, average connection speeds on surveyed mobile network operators ranged from a low of 0.4 Mbps to a high of 8.6 Mbps. Only nine operators demonstrated average connection speeds in the aforementioned broadband category while 6
88.
by _getify 13y ago
> Minified jquery is like 32kb. That means literally nothing in modern web. Unless you are from 1995 using 2G connection, this doesn't matter. Or on like better than 80% of all mobile data connections in the world. But mobile is so
89.
by _getify 13y ago
> it's fairly lightweight Really? 93kb of code is lightweight? Yeah I know it gzips smaller, but that's still not what I'd call "ligthweight". It's not bloated, but it's certainly not a micro-lib. >
90.
Should I Pick jQuery?(shouldipickjquery.com)
13 points by _getify 13y ago|16 comments

More ›