My favorite part of the release notes: "Despite jQuery.isNaN() being undocumented, several projects on Github were using it. We have contacted them and asked that they use jQuery.isNumeric() or some other solution." This is an excellent reminder of how much things have changed in the last 10 years in our space; a popular tools vendor can go query a massive source code repository and reach out proactively for transiti…
This is one of the reasons why Google killing Code Search is so sad.
JQuery 1.7 Released
31–40 of 47 posts
Re: JQuery 1.7 Released
#32One thing I don't like about jQuery's evolution is the size. This version weights at 92K minified / 33K gzipped, which for mobile phones is a PITA.
I'm not really a developer so ignore if that's not possible / makes no sense.
Re: JQuery 1.7 Released
#33One thing I don't like about jQuery's evolution is the size. This version weights at 92K minified / 33K gzipped, which for mobile phones is a PITA.
Why isn't there a tool that analyzes which functions / features of jQuery your project is using and generates a smaller library with only the stuff you need? I'm not really a developer so ignore if that's not possible / makes no sense.
Re: JQuery 1.7 Released
#34Re: JQuery 1.7 Released
#35My favorite part of the release notes: "Despite jQuery.isNaN() being undocumented, several projects on Github were using it. We have contacted them and asked that they use jQuery.isNumeric() or some other solution." This is an excellent reminder of how much things have changed in the last 10 years in our space; a popular tools vendor can go query a massive source code repository and reach out proactively for transiti…
This is one of the reasons why Google killing Code Search is so sad.
I assume they found those github projects using code search. Code search may not be used a lot, but the people and projects using it have a large impact. Is there any way we can convince Google it's worth keeping it available?
Re: JQuery 1.7 Released
#36One thing I don't like about jQuery's evolution is the size. This version weights at 92K minified / 33K gzipped, which for mobile phones is a PITA.
Re: JQuery 1.7 Released
#37One thing I don't like about jQuery's evolution is the size. This version weights at 92K minified / 33K gzipped, which for mobile phones is a PITA.
Why isn't there a tool that analyzes which functions / features of jQuery your project is using and generates a smaller library with only the stuff you need? I'm not really a developer so ignore if that's not possible / makes no sense.
Re: JQuery 1.7 Released
#38It's always nice with new features and enhancements but some bugs should first be fixed, like e.g. this one (i cannot update my code to a version higher than 1.5.x due to customers still using IE7): http://bugs.jquery.com/ticket/9646
I had to work around this insidious creation http://bugs.jquery.com/ticket/8205
It creates a memory leak (it hit my getJSON calls) that slowly strangled one of my apps until it crashed the browser.
I list a lot of hours on that one...
Re: JQuery 1.7 Released
#39One thing I don't like about jQuery's evolution is the size. This version weights at 92K minified / 33K gzipped, which for mobile phones is a PITA.
I've been leaning more and more toward Zepto for mobile. It's still lacking a fair bit of jQuery's functionality, but the basics are there and the syntax is compatible. You lose a lot of IE/older browser support, but if you do some device sniffing and serve jQuery to desktops and Zepto to mobile devices, that's not really an issue.
Re: JQuery 1.7 Released
#40One thing I don't like about jQuery's evolution is the size. This version weights at 92K minified / 33K gzipped, which for mobile phones is a PITA.
That's somewhat mitigated with the CDN version (most users won't have to download it).