jeresig

24 ms·

1. 151.▲
   by jeresig 16y ago

   That's correct! We started work on it in early 2006 and moved to Boston/Cambridge in June 2006 to participate in the Y Combinator program (which was a lot of fun, as many have said). We had a monumentally hard time trying to get people to f
2. 152.▲
   by jeresig 16y ago

   Heh, while I assume that this was mostly rhetorical and largely tongue-in-cheek it is a question that I've been pondering lately. (Or, more accurately, thinking about what work excites me.) I've been working on jQuery full-time now for abou
3. 153.▲
   by jeresig 16y ago

   I'm not sure why you would think that? The issue described in this blog post is relating to the performance of a particular CSS selector that jQuery implements - not really anything having to do with memory usage (and the memory usage of jQ
4. 154.▲
   by jeresig 16y ago

   I don't think any of the points that were mentioned in his post are relevant any longer (not that many of the issues that he mentioned were entirely relevant to begin with, mostly just excessive grandstanding over minutia).
5. 155.▲
   by jeresig 16y ago

   At a fundamental level people end up putting jQuery through a huge number of unknown situations (millions of users on even more web sites in even weirder browsers). While we certainly strive to have as few issues pop up as possible they see
6. 156.▲
   by jeresig 16y ago

   Huh - interesting. As far as we know we haven't received any bug reports from the Twitter team (although we have reached out to them - and they do have our contact information) regarding this issue. Additionally I don't think we've received
7. 157.▲
   by jeresig 16y ago

   Straight connection overloading. We're already redirecting the majority of the files - but somehow the hotlking continue to persist.
8. 158.▲
   by jeresig 16y ago

   I've since been able to flip over into developer mode (you have to toggle a physical switch to enable it). It gives you a proper shell (which allows you to install an SSH key) but beyond that there doesn't seem to be much else that you can
9. 159.▲
   by jeresig 16y ago

   jQuery Mobile supports Android (amongst many other platforms): http://jquerymobile.com/gbs/
10. 160.▲
    by jeresig 16y ago

    At best developing exclusively for bleeding-edge platforms is a niche-market. Is there enough interest now to hire a few developers to build HTML 5/CSS 3/etc.-only experiences? Absolutely. Is this a tenable position for anything more than a
11. 161.▲
    by jeresig 16y ago

    > Lot's of it is. (Zepto is broken across multiple files so I might be missing some functionality.) Roughly, Zepto has this many properties/method: On $: 5, On $.fn: 32. jQuery has: On $: 95, On $.fn: 146. Phrases like "jQuery-compatibl
12. 162.▲
    by jeresig 16y ago

    Yep - and it's probably fine if you're only building apps for iOS devices - possibly Android as well. Beyond that you're getting into very shaky territory. What about Opera (the most popular mobile browser)? What about Blackberry (the secon
13. 163.▲
    by jeresig 16y ago

    Sure - and when jQuery was first released it was super-tiny too. The reality is that: 1) Targeting a single platform will yield a smaller file size at the expense of market share. 2) Shooting for small file size will throw important feature
14. 164.▲
    by jeresig 16y ago

    There are a massive number number of features left out - not to mention critical functionality. Just taking a quick peek, for example if we look at .show()/.hide(): http://github.com/madrobby/zepto/blob/master/src/zepto.js#L5... http://g
15. 165.▲
    by jeresig 16y ago

    This was due to the fact that we're targeting a lot of platforms - many of which may not be able to support those elements. For the first alpha we wanted to pick something that would absolutely work - we can absolutely re-examine using thos
16. 166.▲
    by jeresig 16y ago

    Data is not tied to attributed explicitly. It only pulls I the values on first call and then never again. Event namespaces have actually been in jQuery for quite a few years now - we're just exposing that extra property now on the event obj
17. 167.▲
    by jeresig 16y ago

    The fact that it's displaying is a huge step up from where we were just recently. (BlackBerry 5, and especially 4 can be really rough. We'll definitely look in to this, it's one of tr platforms we want to get working for 1.0 final.
18. 168.▲
    by jeresig 16y ago

    Can you file a bug on the form elements? (Specifically which one(s) you are seeing the issue on) It'll help us to pinpoint the general area in which problems are happening - thanks! http://github.com/jquery/jquery-mobile/issues
19. 169.▲
    by jeresig 16y ago

    Thanks for the note about Auto-fit - will look into that. Also that demo page should be fixed now.
20. 170.▲
    by jeresig 16y ago

    Excellent - thank you!
21. 171.▲
    by jeresig 16y ago

    Ah, gotchya - yeah, that's totally a reasonable thing to assume. We'll work on that! And thanks for the testing.
22. 172.▲
    by jeresig 16y ago

    2. Fixed! Thanks for the catch :) 3. Good point - for now you can grab a download from Github: http://github.com/jquery/jquery-mobile/archives/master That'll have everything in it - including the demos.
23. 173.▲
    by jeresig 16y ago

    Hmm - do you have any more details regarding where the hangs happened? We were testing against a G1 w/ 1.6, as well and didn't see issues like that. If you could take a moment to file a quick bug report we would appreciate it: http://githu
24. 174.▲
    by jeresig 16y ago

    So we're not planning on doing a webOS theme (or a iOS theme or a Blackberry theme) as we wish to create something of a unified experience across the platforms - although if you wish to contribute one, we'll absolutely accept it. Unfortunat
25. 175.▲
    by jeresig 16y ago

    Yeah - we've noticed the 'flash' as well - we suspect that it has to do with the CSS transitions but we're still looking in to it (and it only appears to happen on some platforms, but not others, making it all the more frustrating).
26. 176.▲
    by jeresig 16y ago

    I was kind of surprised how rough webOS is to develop for (considering that it is WebKit-based). It's impossible to determine the scroll offset of the screen on webOS, for example (making it impossible to have fixed headers/footers). We'll
27. 177.▲
    by jeresig 16y ago

    Two quick points (I work at Mozilla, but not on the browser - I'm also the creator of the Dromaeo performance benchmark): All browsers implement things to get faster at these benchmarks. They implement caching in bizarre places just to ma
28. 178.▲
    by jeresig 16y ago

    It is absolutely true that after a release there is, at least, some number of bug reports that pop up (regressions, browser issues, etc.). Having a pre-release helps to mitigate a lot of that. In our experience it appears as if the vast maj
29. 179.▲
    by jeresig 16y ago

    Well, in just 5 short days you will be able to see the final release notes - and final release :) Some details about the release were also mentioned in a recent talk by a jQuery community member (I believe it was also posted here, to Hacker
30. 180.▲
    by jeresig 16y ago

    I don't see the point in doing so - the important part is getting some developers to put the copy of jQuery into their page to see if there are any regressions. Additionally we provide focus on the general areas of the library that had majo