jeresig

15 ms·

91.
by jeresig 14y ago
I don't think it makes sense to shift the focus of the book - the topic that it serves (understanding the fundamental construction of JavaScript DOM libraries and the trickier aspects of the JavaScript language) is one that is grossly under
92.
by jeresig 14y ago
I wouldn't consider Pro JavaScript Techniques to be "The jQuery Memoirs" really at all. It only mentions libraries in passing. Whereas this book is much more in-depth and really breaks apart the fundamental aspects of a JavaScript DOM libra
93.
by jeresig 14y ago
I definitely agree that there are a ton more JavaScript users now, compared to 4 years ago - I disagree that they're more competent, it's a pretty massive bell curve. The tech bubble can be pretty insular here at Hacker News but I still run
94.
by jeresig 14y ago
Sorry for the delay in announcing it - I was waiting for the book to physically arrive in my hands, which it hasn't done so, yet. (I have a copy pre-ordered with Amazon and since that's the way most people will be receiving the acquiring th
95.
by jeresig 14y ago
Awesome - glad you're enjoying it! One thing to note: If you make changes to the code and then hit play again right now the user's changes are lost (making sure that playback will continue to work). We definitely want to persist those chang
96.
by jeresig 14y ago
In our experience thus far we've found that students are far less intimidated by the numbers/math when they're able to directly manipulate the results. When they can tweak the numbers with minimal ramifications and instantaneous feedback th
97.
by jeresig 14y ago
They are narrated by Jessica Liu (as mentioned in the blog post).
98.
by jeresig 14y ago
I disagree. We're working towards the goal of having a comprehensive Computer Science curriculum and this is just the first step. I talk more about our reasoning and methodology here: http://ejohn.org/blog/introducing-khan-cs/
99.
by jeresig 14y ago
They're narrated by Jessica Liu, more details here: http://ejohn.org/blog/introducing-khan-cs/
100.
by jeresig 14y ago
I wish I could say that I haven't been personally attacked by them, unfortunately it has been rather extensive and ongoing. Thankfully I've been able to avoid most of it by not visiting clj since 2008-ish and blocking choice Twitter users.
101.
by jeresig 14y ago
Interestingly, jQuery was the first major library to switch to a feature detection model. Looking around it appears that a number of other libraries still use browser sniffing (such as MooTools, Prototype, and Dojo). The reason why I switch
102.
by jeresig 14y ago
I think that post has less to do with my opinions of feature testing and more to do with the environment presented by that usergroup. As to why jQuery moved to feature testing, we discussed that in the jQuery 1.3 release notes: http://docs
103.
by jeresig 14y ago
Every where you see the "with statements are harmful"/"eval is harmful" drum being hit, you see Douglas Crockford. He's a great guy, and I really respect his opinion, but I continue to feel that these are legitimately useful aspects of the
104.
by jeresig 15y ago
Sounds sort of like StoryCorps: http://storycorps.org/
105.
by jeresig 15y ago
That may be a bug with that particular problem - you should click the "Report a Problem" link at the bottom of the exercise and copy-and-paste what you just aid here, there. At best the problem isn't being clear that it's looking for a redu
106.
by jeresig 15y ago
Heh yeah, the Mathjax API is rather awful. Tons of separate file requests, configuration is only designed to work in inline script tags, and other ugliness. We've been experimenting with MathQuill - it's way faster and much more lightweight
107.
by jeresig 15y ago
I have yet to see it work - at least my Hip Chat tab doesn't update when a new chat comes in, whereas it does in Firefox.
108.
by jeresig 15y ago
I was looking at it just recently - it looks promising. Haven't had a chance to try it, yet. http://sickbeard.com/
109.
by jeresig 15y ago
Yes. Although I was just reading through the extension docs and realized that you do have permission to add context menu items: http://code.google.com/chrome/extensions/contextMenus.html So yeah, strike the last item from my list - I blam
110.
by jeresig 15y ago
Off the top of my head, three things that've bugged me: I use a ton of tabs in my browser, in Firefox the tabs go off to the side and allow me to scroll through them (while still allowing me to read the title) whereas Chrome squishes the
111.
by jeresig 15y ago
Very interesting, I'll have to check into that! I use a Griffin FM transmitter right now, works OK, but has frequent problems with competing radio stations. http://www.overstock.com/Electronics/Griffin-RoadTrip-iPhone...
112.
by jeresig 15y ago
Naturally, we're talking with our legal representation about that - we'll have to see what we can actually do. I think we're "ok" for now though as users are getting to the right place in the end.
113.
by jeresig 15y ago
Hi Pierre - Thanks for the details on this! We dug into our Wordpress and realized that W3 Total Cache was configured to block anything that had the word 'bot' as part of its user agent string (sigh). That's now fixed and live. As to the re
114.
by jeresig 15y ago
Hilarious - nice job Ben! I was bemusing in the Khan Academy chat the other day that I always thought it'd be hilarious (although, useful) to have a .uncle() or .aunt() method (for getting .parent().siblings()). Quite amused that Ben put th
115.
by jeresig 15y ago
I started to write a reply to some of the comments here but ended up turning it into a blog post: http://ejohn.org/blog/jquery-16-and-attr/ Looks like someone has submitted it to HN as well: http://news.ycombinator.com/item?id=2544698
116.
by jeresig 15y ago
Actually == true and == false will still work, === true and === false will fail (as the return value is now "disabled" or undefined).
117.
by jeresig 15y ago
You probably wouldn't, it's just a convenience method (and patches over some of the cross-browser inconsistencies and naming-convention weirdness).
118.
by jeresig 15y ago
Let's pretend we're working with a checkbox that isn't checked at all: <input type="checkbox" id="c"/> $("#c").attr("checked") => false // 1.5.2 $("#c").attr("checked") => undefined // 1.6 $("#c").attr
119.
by jeresig 15y ago
I thought about this discussion a lot more today, discussed the points with the rest of the jQuery core team, and we decided to land an improvement to bring back the boolean attribute handling (with virtually no performance overhead). The b
120.
by jeresig 15y ago
Roughly right. I told them that I really wanted to build a cross platform, mobile, version of their application (amongst other things, naturally). They mentioned that they were already looking to build an iPad application - that seems like

More ›