jQuery’s Content Delivery Network: You Got Served!

Posted on by

MaxCDNIn 2013, MaxCDN joined the jQuery Foundation and stepped up to provide Content Delivery Network (CDN) services for the jQuery CDN at code.jquery.com. Files can now be requested through both HTTP and HTTPS (SSL) protocols, either to download to your own servers or to use directly on production web sites. MaxCDN’s infrastructure can reliably deliver jQuery files through a worldwide high-speed collection of servers to minimize round-trip time.

Why a CDN is Useful to Developers

The obvious benefit is that the MaxCDN network is much faster than the average server, and geographically distributed so that round-trip times are kept low. Yet there is another subtle benefit. Many web sites simply serve up all their content (HTML, CSS, scripts, images, and other assets) from the same domain. This can create a bottleneck on both the browser and the server. Downloading content from multiple domains, known as domain sharding, can improve performance. Just remember that as with any good thing, going overboard is a bad idea. Some research shows that just two domains may be the sweet spot. Use a tool like WebPageTest to test your site to get the best results.

Why a CDN is Useful to jQuery Projects

jQuery projects serve out a huge number of bytes, especially on days when a project makes a new release. When developers rush to download the latest version, we want to be able to handle the load. GitHub does a great job of supporting our development cycle and working project files, but it is not designed to serve up billions of copies of our production files. Google and Microsoft also provide CDNs, but it can take several days between the time a project makes a release and the time the files appear on those CDNs. Third-party CDNs also have their own rules about which files can be placed on the CDN, for example they don’t post pre-release versions. The jQuery CDN allows us full control over timing and content.

Serving Billions of Files, Trillions of Bytes

We thought we were serving a lot of files, but some statistics from MaxCDN really drive home the point. In the last five months of 2013, the CDN served more than 82 billion files, exceeding 3.6 petabytes. We sent out enough bytes to completely fill 3,269 1-terabyte disk drives! An average day on the CDN has us serving up about 20 terabytes of data.

Here are the ten most popular files requested from the CDN:

# File name Hits
(billion)
Size
(terabytes)
1 jquery-latest.js 6.36 404.65
2 jquery-1.9.1.min.js 5.93 193.96
3 jquery-1.7.2.min.js 4.95 154.50
4 jquery-latest.min.js 4.45 116.08
5 /ui/1.10.3/jquery-ui.js 4.18 484.58
6 jquery-1.9.1.js 2.45 178.54
7 jquery-1.10.1.min.js 2.27 71.62
8 jquery-1.7.1.min.js 2.26 78.05
9 jquery-1.4.2.min.js 2.07 39.80
10 /ui/1.10.3/themes/smoothness/jquery-ui.css 1.55 9.83

There are some encouraging signs here. Some of the most popular files are the minified files, as they should be for a production web site. It’s also encouraging that recent versions of jQuery Core (1.9.1 and 1.10.1) are high up on the list. That means a lot of jQuery developers are keeping up with the features and bug fixes we’ve been adding.

The most commonly requested file is jquery-latest.js, which automatically updates whenever the jQuery Core team releases a new version. Developers should never use jquery-latest.js or jquery-latest.min.js on a production site, it is primarily meant for testing. Similarly, the full jQuery UI build at position 5 is the latest version, but that file may not be a good fit for production sites needing only a few jQuery UI widgets. A minified copy with just the needed widgets can be built on the download builder page.

Counting on the CDN

Thanks to MaxCDN’s contribution, the jQuery Foundation has a content delivery network that offers reliable high-speed access to all of our project files. The files at code.jquery.com serve as the official repository for all jQuery project releases. You can either download the file for local use, or reference our domain directly from your own web pages to take advantage of the CDN and domain sharding.

The State of jQuery 2014

Posted on by

The year 2013 was an incredibly exciting one for jQuery. As jQuery celebrates eight years of supporting web developers, it’s time for our annual review. I’m pleased to say that we achieved a lot in 2013 and have some great plans for 2014!

New Leadership

In November, Kris Borchers became Executive Director of the jQuery Foundation as successor to Richard Worth. Kris has been a jQuery Foundation board member and a long-time jQuery contributor, so he understands the mission of the Foundation well. We welcome Kris, and thank Richard for his work in shepherding the Foundation through its first full year of existence.

jQuery used by 68% of the top 100k sites

Continuing Growth

It seems impossible to believe there are still web sites that don’t use jQuery, but the statistics at builtwith.com show there are fewer and fewer of them. jQuery’s core library is used by more than 61 percent of the top 100,000 sites, up 10 percent from last year. Growth is also strong in other jQuery Foundation projects such as jQuery UI, which is now used by nearly one-fifth of top-10,000 web sites.

New Environments

jQuery is also used in a lot of places that can’t be identified through a web crawl. You’ll find jQuery anywhere web technologies are used, not just the public Internet. That includes Google Chrome add-ons, Mozilla XUL apps and Firefox extensions, Firefox OS apps, Chrome OS apps, Windows 8 Store apps, BlackBerry 10 WebWorks apps, PhoneGap/Cordova apps, Node.js, and even the Sony PlayStation 4. By supporting these technologies, we’ve made it possible to take advantage of jQuery knowledge in many places other than just browsers and web pages.

Future-Oriented

In January 2013, we released jQuery 1.9; then jQuery 2.0 was released in April. These two versions dumped old APIs that were making jQuery bigger, slower, and harder to use. jQuery 2.0 went a step further and dropped support for environments that don’t support newer standards, such as Internet Explorer before version 9. From an API standpoint, the two behave identically, though; web developers can update to the 2.x branch whenever those older versions of IE are no longer important to their web pages or apps.

Backwards-Compatible

We knew that removing some old functionality from jQuery core could make migration slow and difficult; after all, a lot of code on web sites was written years ago and the people who wrote it are long gone. That’s why we created the jQuery Migrate plugin to identify code that was using the features we removed. Better than that, it allowed most of that old code to continue to work by shimming in the old behavior. It’s a great tool for keeping a site running while things are being updated, although we don’t advise using it for a long-term fix.

jQuery Served Your Way

With jQuery being used in so many environments, we want to make sure it fits with their workflows and conventions. So, we’re adapting by making jQuery available on both the npm and Bower package managers. This makes it easy for just about any JavaScript-based project to keep jQuery dependencies up to date. Last year’s refactor of jQuery core into small modules also lets developers create a custom build that removes features a project doesn’t need, to reduce the download size.

Keeping it Simple

We haven’t forgotten, however, that most developers keep things simple and just include a copy of the standard jQuery build using a <script> tag. So in 2013 we upgraded our content delivery network (CDN) thanks to a generous donation from MaxCDN. The jQuery CDN is now better than ever and supports the https protocol for delivering all files.

Advocating for Developer Needs

jQuery’s use of a convenient and browser-independent layer around the cumbersome DOM interfaces is one reason for its popularity. As Simon St. Laurent put it, “jQuery is how the web routes around broken API design.” But we don’t want the DOM API repair business to be our full-time line of work. People should be continuing to use jQuery because it’s a powerful way to implement designs and provides a vibrant ecosystem of useful plugins, not because the native DOM APIs are broken, verbose, or inconsistent. That’s why we participate in the standards process through bodies such as the W3C and ECMA.

Let’s Keep Innovating!

Over the next few days, posts on this blog will be counting the ways that the jQuery Foundation is improving the web developer community, in keeping with our mission. If you see something that interests you, we invite you to get in touch with us and participate!

Dave Methvin
President, jQuery Foundation

jQuery UK 2014

Posted on by

jQuery UK is back for 2014!

The jQuery Foundation is pleased to announce that the third annual jQuery UK will take place on May 16, 2014 in Oxford, UK. This event is organised by White October Events.

jQuery UK is the UK’s largest front-end developer conference. Over one day and three tracks,  pioneers of the world’s favourite JavaScript framework and wider industry experts will deliver technical content to inspire front-end and full stack developers to do more in the browser and beyond.

Confirmed speakers include Tilde co-founder and jQuery Board member Yehuda Katz, CSS expert Lea Verou, and the author of this very blog post (and jQuery developer relations lead), Adam J. Sontag.

There are also four hands-on workshops taking place the day before the conference. Choose from:

  • Advanced jQuery Techniques
  • Web Developers Toolbox
  • jQuery UI Foundations
  • Diving into AngularJS

Space for these workshops is strictly limited, so book early to secure your spot!

A limited number of Early Bird tickets are on sale until January 31, for £130 + VAT or until they sell out. Full price tickets will be available for £175 + VAT.

To book tickets or sign up for updates, visit jqueryuk.com. You can also track jQuery UK on lanyrd.com and follow @jquk for updates.

jQuery 1.11.0/2.1.0 Beta 3 Released

Posted on by

Put down the egg nog and get ready to test. The latest (and most likely last) betas of jQuery 1.11 and 2.1 are now submitted for your inspection and approval. You can get them here:

We know you’ve got a few days off over the holidays, so give us a big present and help us test! Don’t forget that jQuery 1.x supports IE 6/7/8 and jQuery 2.x does not. In other ways the two versions should echo the same feature sets, so it should be possible to switch between the two without too much trouble.

Notable changes

Asynchronous Module Definition (AMD): jQuery components are now built with AMD. jQuery has supported having the library itself loaded by an AMD loader ever since version 1.7. Now, we’re using AMD internally as well, replacing our old modular build system. If you want to know more, see the README file.

Published on npm: The 2.x branch of this beta and all our future 2.x releases will be published on npm so that you can use it with node or packages like browserify. If you want to install the beta, you can use npm install jquery@2.1.0-beta3.

Still to come: No global for the npm version: After polling potential npm/browserify users, we have decided to keep the global namespace clean and not to expose the jQuery global in these situations. Instead, you can do it yourself with window.jQuery = window.$ = require("jquery"). That ticket didn’t make it into the beta, but you should assume you’ll need to set it yourself.

Performance: Our new “lazy feature detects” reduce the startup time for the library, which is especially good for mobile devices. If you never call the API, you never even need to run that code! We also found and removed some situations where jQuery unnecessarily forced a page layout to occur.

Bug fixes: Lots and lots of bug fixes are in this release, including several to ensure the latest versions of browsers like IE11 work smoothly and eliminate console warnings in Chrome. Many fixes are shared across both versions. You can see the complete changelog below.

Breaking changes: None! We’re committed to making this an easy update for you if you already did an upgrade to 1.9+ or are using the jQuery Migrate plugin. So don’t be a chicken, test this beta!

Release Notes

Twas the week before Christmas, when all through the house
Not a creature was stirring, not even a mouse.
The code was checked by the team with such care,
In hopes that a new beta soon would be there.

Contributors nestled all snug in their beds,
While visions of working code danced in their heads.
The pull requests landed, commits all now pushed,
GitHub issues closed, the whole team is bushed.

When on the CDN there arose such a clatter,
I sprang from the bed to see what was the matter.
Away to the laptop I flew like a flash,
Popped open a window and started up bash.

My wondering eyes barely processed the data,
It’s release 3 of jQuery 1.11 and 2.1 beta!

And then, on the roof, I heard at the ready,
The loading of code that was solid and steady.
As I drew in my head, and was turning around,
Down the chimney St. jQuery came with a bound.

“I’m needing your help,” St. jQuery exclaimed,
“If we ship code with bugs I know I’ll be flamed!”
“Just run this beta with your best sites and apps,
so we know if our changes avoided the traps.”

More rapid than eagles contributors came,
He whistled, and shouted, and thanked them by name!
“Now Timmy! now, Richard! now Michał and John!
On Oleg! On Chris! On Jakob and Hong!
To the top of the list, your reward won’t be small!
Now cache away! Cache away! Cache away all!”

He sprang to his sleigh, to his team gave a whistle,
And away they all flew like the down of a thistle.
But I heard him exclaim, as he drove out of sight,
“Happy beta to all, and to all a good-night!”

Changelog

Common to both jQuery 1.11 Beta 3 and jQuery 2.1 Beta 3

Ajax

Attributes

Build

Core

Css

Data

Effects

Event

Selector

Support

jQuery 1.11 Beta 3

Ajax

Core

Effects

Support

jQuery 2.1 Beta 3

Ajax

Build

Core

Event

Unfiled

jQuery 1.11.0/2.1.0 Beta 2 Released

Posted on by

The latest betas of jQuery 1.11 and 2.0 have arrived! You can get them here:

Don’t forget that jQuery 1.x supports IE 6/7/8 and jQuery 2.x does not.

What’s in the beta

Asynchronous Module Definition (AMD): The biggest change in 1.11/2.1 continues to be AMD. jQuery has supported having the library itself loaded by an AMD loader ever since version 1.7. Now, we’re using AMD internally as well, replacing our old modular build system. If you want to know more, read the README file.

Published on npm: The 2.x branch of this beta and all our future 2.x releases will be published on npm so that you can use it with node or packages like browserify. Note that the main jquery page is currently not up to date, and won’t be until we push the final 2.1.0 to it. If you want to install the beta, you can use npm install jquery@2.1.0-beta2. Many thanks to Domenic Denicola who has already reported bugs #14548 and #14549 that will be fixed in the next go-round.

Performance: Our new “lazy feature detects” reduce the startup time for the library, which is especially good for mobile devices. If you never call the API, you never even need to run that code! We also found and removed some situations where jQuery unnecessarily forced a page layout to occur.

Bug fixes: Lots and lots of bug fixes are in this release, including several to ensure the latest versions of browsers like IE11 work smoothly and eliminate console warnings in Chrome. Many fixes are shared across both versions. You can see the complete changelog below.

Breaking changes: None! We’re committed to making this an easy update for you if you already did an upgrade to 1.9+ or are using the jQuery Migrate plugin.

Please do give these betas a try and let us know whether everything is working as you’d like. It’s always frustrating to us when we make a new production release and people find bugs that could have been fixed during the beta process. It only takes a few minutes to smoke-test your code against these betas, and it will save both you and us a lot of future heartache!

Sad sourcemap story

One of the changes we’ve made in this beta is to remove the sourcemap comment. Sourcemaps have proven to be a very problematic and puzzling thing to developers, generating scores of confused questions on forums like StackOverflow and causing users to think jQuery itself was broken.

We’ll still be generating and distributing sourcemaps, but you will need to add the appropriate sourcemap comment at the end of the minified file if the browser does not support manually associating map files (currently, none do). If you generate your own jQuery file using the custom build process, the sourcemap comment will be present in the minified file and the map is generated; you can either leave it in and use sourcemaps or edit it out and ignore the map file entirely.

We will be encouraging browser makers to come up with better ways to handle sourcemaps for situations like jQuery’s, where there are widely distributed files on CDNs. We’d like sourcemaps to be robust and gracefully handle situations like file renaming or missing files. See our bug ticket for more information.

Let’s give thanks

As Thanksgiving Day approaches, let’s give a hand to the great people who have contributed to jQuery core code since the last release: Amey Sakhadeo, Anthony Ryan, Chris Antaki, Chris Price, Corey Frang, Daniel Herman, Dominik D. Geyer, George Kats, Guy Bedford, Ilya Kantor, Jeremy Dunck, Jörn Zaefferer, Lihan Li, Marian Sollmann, Michał Gołębiowski, Mike Sidorov, Noah Hamann, Oleg Gaidarenko, Richard Gibson, Ronny Springer, Scott González, Sindre Sorhus, Terry Jones, Timmy Willison, and Timo Tijhof.

jQuery 1.11 and 2.1 Beta 2 Changelog (common to both)

Ajax

Attributes

Build

Core

Css

Data

Effects

Event

Selector

Support

jQuery 1.11 Beta 2

Ajax

Core

Effects

Support

jQuery 2.1 Beta 2

Ajax

Build

Core

Event

jQuery Conference Set to Roost in San Diego

Posted on by

With 2013 rapidly drawing to a close, we’re excited to announce that jQuery’s first stop in 2014 will be in lovely San Diego, California on Wednesday, February 12 and Thursday, February 13! It’s our first trip to San Diego, and we’re hoping you’ll join us at the Town and Country Resort & Convention Center to beat the winter doldrums for a week that will be chock-full of jQuery, JavaScript, and front-end development, and how the latest and greatest relates to what you do every day.

The early bird gets the worm – and saves fifty bucks – so get your tickets now!

Call for Speakers

As always, we’re looking for great speakers to help us make jQuery San Diego into a conference that’s both edifying and entertaining. In the same way that jQuery is but one of the many tools that front-end developers use regularly, jQuery Conference is an opportunity to present and learn about the many technologies and practices that help us build web apps today. In other words, we’re eager to hear proposals about HTML5, JavaScript, CSS, testing, tooling, deploying, mobile, responsive design, and pretty much anything else relevant to front-end engineering today. (Of course, proposals about jQuery, jQuery UI, and jQuery Mobile are happily welcomed as well.)

Our call for speakers is open from now through November 10, 2013, and we’re hoping to hear from speakers with a diverse range of experience as conference speakers, web developers, and people! If you have any questions about speaking at jQuery San Diego, please get in touch with us on Twitter @jqcon or via e-mail at content at jquery dot org.

Level Up With Roost

For San Diego’s pre-conference training, we’re partnering with Bocoup to bring you Roost, a two-day training conference that’s a great opportunity to increase your skills with many aspects of web development, including jQuery & JavaScript, HTML & CSS, unit testing, and more. If you’re a beginning-to-intermediate web developer looking to make the most of your trip and warm up before jQuery Conference, Roost’s two days of practical guidance on February 10-11 make a great complement to your week.

Roost and jQuery Conference will both be at the Town and Country Resort, with individual tickets available for each event, as well as a discounted combination ticket to both events.

That’s All…For Now

Tickets for jQuery Conference and Roost are on sale now, and supplies of early bird tickets are limited! We can’t wait to start reviewing your proposals and announce the speaker lineup, but until then, follow @jqcon for news and updates! We’re also looking for sponsors to team up with us and help make our time in San Diego as awesome as possible, so if your company wants to get involved, get in touch with us for a sponsorship packet and more information.

jQuery 1.11 and 2.1 Beta 1 Released

Posted on by

Ahoy Matey! Do you know what today is? It’s Talk Like a Pirate Day!

Before the jQuery team weighed anchor and ran for the grog, we left a treasure chest on the jQuery CDN filled with beta versions of jQuery 1.11 and 2.1. Here be the treasure map to the bounty:

Don’t forget that jQuery 1.x supports IE 6/7/8 and jQuery 2.x does not. Here are the highlights of what changed:

Asynchronous Module Definition (AMD): In this release we’re going full-mast with AMD. jQuery has supported having the library itself loaded by an AMD loader ever since version 1.7. Now, we’re using AMD internally as well, replacing our old modular build system. Colin Snover started it with some fine cutlass work, then Timmy Willison made sure the whole library was drawn and quartered properly with AMD. He even mollycoddled you with a fine README file so you can be buildin’ yer own custom version. And because we’re pirates, we’re using aaaarrrrr.js to build it.

Performance: Michał Gołębiowski led the charge to reduce jQuery’s startup time by deferring much of the feature detection code so that it runs the first time you use an API call, rather than on page load. If you never call the API, you never even need to run that code! We also found and removed some situations where jQuery unnecessarily forced a page layout to occur.

Bower support: We’re now using Bower for a lot of our internal dependency management, and plan to publish production versions of jQuery to Bower in the future.

Bug fixes: We keelhauled a few scurvy bugs since the last versions. There’s a list down the way if you want to be knowin’.

API changes: None! With all the internal code changes for AMD, we didn’t want to change a lot of APIs in this version. Your old scurvy code should work with no problems as long as you already did an upgrade to 1.9+ or are using the jQuery Migrate plugin.

Now we know some of you may not be takin’ the time to try this beta. We got a name for you: bilge rats. Don’t be comin’ to us after the release and complainin’ about bugs. Get on board and man the lines so we can get this code shipshape before the beta is over!

A tip of the pirate hat to the sea dogs and scallywags who got this release under way: Timmy Willison, Michał Gołębiowski, Oleg Gaidarenko, Richard Gibson, Amey Sakhadeo, Jörn Zaefferer, Chris Price, Daniel Herman, Guy Bedford, Jeremy Dunck, Mike Sidorov, and Terry Jones. And of course an aye-aye shout-out to the original jQuery pirate, Long John Resig!

jQuery 1.11 and 2.1 Changelog (common to both)

Ajax

Attributes

Build

Core

Css

Effects

Event

Selector

Support

jQuery 2.1

Build

Core

jQuery 1.11

Effects

jQuery Austin Speaker Lineup

Posted on by
jQuery Conference Portland logo

With just over a month until jQuery Austin starts, I wanted to take a few minutes to point out the highlight of our conference program: our talks! With a single-track conference, it’s our job to select individual talks that will appeal to the entire conference audience. At the same time, we want to make sure we cover a broad range of subjects related to jQuery and front-end engineering so that every attendee can take home something that will make a difference in their day-to-day development. Those were our goals with our Call for Papers, and we hope you’ll agree our 20 selections fit the bill.

jQuery

One of the main focuses of #jqcon is to bring you the latest on what’s going on in the jQuery libraries, and there’s no one better for that than keynote speakers Dave Methvin and Scott González, development leads for jQuery and jQuery UI. Dave will be talking about more than just recent changes to jQuery core; he’ll be delving into how to diagnose what does (and doesn’t) cause performance woes in modern web apps. And with the jQuery UI and jQuery Mobile projects merging, you’ll want to be sure to hear Scott tell what the future has in store.

As increased modularity comes to jQuery, Timmy Willison will describe how and why we’re making the switch to AMD in core, and how to leverage these forthcoming changes in your apps. Julian Aubourg is going to take a dive into Deferreds and Promises, which have been proven to be a useful tool for managing asynchronous code, even since before their incorporation into jQuery a few years ago.

Mobile

We’re excited to have a number of talks on taming the burgeoning beast that is mobile development. Alex Schmitz will be reviewing the results of the Mobile team’s serious look at the performance of jQuery Mobile for the upcoming 1.4 release, and outline new features that have been added with performance in mind, and Asta Gindulyte will examine how to use jQuery Mobile across a wide variety of screen sizes, from phones right on up to televisions.

Figuring out how to serve the right images to your application’s users across devices and bandwidths has been one of the more interesting discussions in web development for the last year or two, and that’s why we’ve brought Christopher Schmitt to help you make sense of it all. Building applications that work offline is another challenge, and Seth Hallem will explain how to persist, search, update, and display data in HTML5 mobile apps.

Application Development

Debugging is the constant task of software development, and Brian Arnold will be walking us through the constantly-improving tools that can help improve your skills in this dark art. Sometimes, apps appear to work fine until they get into the hands of users who require a screenreader, so Jörn Zaefferer will be giving a primer on the important subject of how to make your web application accessible to all users.

Client-side MVC frameworks are certainly all the rage these days; after having talks on Backbone and Ember at jQuery Portland, we’re thrilled to bring AngularJS into the mix, with Burke Holland bringing you up to speed on directives, one of the framework’s coolest features. If you’ve been using MVC frameworks, one question that you’ve likely wrangled with is where to draw the line between reusable UI widgets and custom application code – which just happens to be one of the subjects Richard Lindsey will be presenting in his discussion of the jQuery UI Widget Factory.

Front-End Ops

Web applications are continuously becoming more JavaScript-centric, bringing increased rigor to the client-side. Grunt has taken off as a popular tool for building and minifying code, and Aaron Stacy‘s talk will explore how to use this JS task runner for even more. Many more developers are recognizing the importance of writing unit tests, and Travis Tidwell will be in Austin to help you incorporate running tests into your deployment process with PhantomJS.

All the technology in the world doesn’t change the fact that web applications are still written by human beings, and Monika Piotrowicz will analyze how we can improve our workflows to better accommodate all the different people who are involved and perhaps even build better products! The jQuery Foundation itself is one organization where we’ve made significant changes to how we work in order to get more developers involved in the project, and Anne-Gaelle Colom will be on hand to detail her experiences as she’s grown to become the Documentation lead for jQuery Mobile.

mind === blown

The open web platform continues to evolve and bring with it exciting new possibilities for what we can do in the browser. Jenn Schiffer will enlighten you on the canvas tag and how it can let you use your coding abilities to be creative and make art, and Vlad Filippov will bring this discussion into a full three dimensions as he shows off voxel.js, a WebGL-based toolkit for creating Minecraft-like worlds and interactive visualizations.

If you’ve got pockets and a phone that vibrates, then you’re surely aware of the utility of push notifications, and Kris Borchers will explain the finer points of their journey to the web platform. Web Components are another emerging spec that have the potential to change how we develop and share reusable widgets, and Juan Pablo Buritica will illuminate the current state of affairs and show tools that will let developers get started writing more modular code today.

Join Us

With so much in store, we hope you’ll head deep in the heart of Texas with us on September 10 and 11! Head on over to the conference site to read more about the program and buy your tickets today. In fact, we’re celebrating the renaissance of our RSS feed with $25 off coupon for anyone who uses the coupon code JQBLOG until we run out of tickets!

If you’re able to attend #jqcon, you’ll probably want to stay within walking distance of the Austin Convention Center in our room blocks at the Hyatt Place and Radisson hotels, especially if you want to be able to explore downtown Austin and rub elbows with your fellow attendees.

If you have any questions, always feel free to get in touch with us on Twitter or via e-mail. If not…see you there!

jQuery Heads to Austin

Posted on by
jQuery Conference Austin logo

This year, we’re happy to be able to resume our tradition of throwing two jQuery Conferences and announce that we’re headed for the first time to Austin, Texas! jQuery Austin is set for Tuesday, September 10 and Wednesday, September 11 at the Austin Convention Center, and we’re planning to host a discussion of the latest developments in jQuery, as well as other tools and techniques from around the world of front end development.

Call for Proposals

We’re looking for speakers who can bring a broad array of perspectives on subjects that cross the spectrum of technologies that are used in tandem with jQuery every day. We love listening to ideas about jQuery, jQuery UI, and jQuery Mobile, but we know there’s a lot more out there. JavaScript, HTML5, CSS, mobile, testing, deployment, and growing as a developer are all subjects jQuery users are eager to hear more about, so if you’ve got something you want to share with the community, we’d love to hear from you.

Our Call for Proposals will be open through July 14th, so we’re hoping to hear from you soon! We’re returning to a single-track format for jQuery Austin, so we’re expecting to have to make some tough decisions once we’ve reviewed the proposals; nevertheless, the only way to be considered is to submit in the first place!

Pre-Conference Training

If you’re looking to understand how to become a better developer and leverage newer features in jQuery, Bocoup‘s jQuery Essentials course on Monday, September 9 is just such an opportunity. The class is taught by Query plugin auteur extraordinaire and Grunt creator Ben Alman, and it’s a great chance to bone up on your skills before the conference begins.

Tickets and Accommodations

Tickets are on sale now, with early-bird pricing available through July 16. You can buy a single ticket for both events, or you can choose to attend only the conference or the training.

We’ve reserved blocks of rooms at the nearby Hyatt Place and Radisson hotels, both of which will leave you just steps from the convention center and downtown Austin.

See You There!

We’re thrilled to be adding some southwestern flavor to #jqcon. The city offers a great backdrop for a few days of learning and connecting with the of the jQuery community while enjoying the BBQ and music. As the saying* goes, “You’ll always remember an Austin September!” Follow @jqcon for news and updates as we have them, we look forward to having you join us in Austin! In the meantime, consider submitting a talk and polishing your cowboy boots!

* This is not actually a saying.

jQuery 1.10.2 and 2.0.3 Released

Posted on by

It’s nearly Independence Day here in the USA, so we’re delivering something fresh off the grill: jQuery 1.10.2 and 2.0.3. These releases fix a few pesky bugs that have been reported over the past month, but the list is refreshingly small. Since some of the bugs spanned both the 1.x and 2.x branches we’re releasing new versions of both to keep them in sync.

You can get the latest files from the jQuery download page, including sourcemap files and links to helpful tools such as jQuery Migrate. If you’re upgrading from a version of jQuery before 1.9, please do read through that page carefully to make your migration as pain-free as possible. Remember that it may take a few days for the CDNs at Google, Microsoft, and CDNJS to respond to the rocket’s red glare and post the latest versions. In the meantime, use the copy on the jQuery CDN.

We’re pretty optimistic that these latest bug-fix releases should be free of surprises. If you drop the new files into your site and see fireworks, please do your patriotic duty and report a bug with a test case (preferably using jsFiddle) at our bug tracker.

These releases wouldn’t have happened without the contributions of Jason Bedard, Jason Merino, Jörn Zaefferer, Michał Gołębiowski, Nguyen Phuc Lam, Oleg Gaidarenko, Richard Gibson, Rick Waldron, Terry Jones, and Timmy Willison.

jQuery 1.10.2 and 2.0.3 Changelog (common to both)

Build

Css

Selector

jQuery 2.0.3 Changelog (specific to 2.x)

Data

Manipulation