Next week the YUI team will begin planning for release 2.9.0 to be shipped in the second half of Q1 2011. YUI 2.9.0 will be the last major dot-release of the 2.x codeline, and the team will be aggressively reviewing all open tickets against the YUI 2 project and either assigning them to be a part of the 2.9.0 release, closing them as “WON’T FIX”, or moving them to the YUI 3 project.
The reality of time and resource constraints forces us to focus on top priority items that will provide some closure to YUI 2.x and allow us to redouble our efforts on 3.x development. Here are some of the criteria that we’ll be using to guide us in deciding what should be included in release 2.9.0:
Issues that negatively impact core use cases.
Emerging issues related to new browser releases on the A-grade matrix.
Enhancements and new features will be de-prioritized for YUI 2 and considered for YUI 3.
The transition of the YUI team from developing two parallel codelines to focusing solely on YUI 3 does not mean the end of the YUI 2 project. All present and future YUI 2 releases will continue to be hosted on the Yahoo! CDN, the YUI 2 codebase will continue to be hosted in GitHub, and we’d like to explore community-based maintenance of YUI 2 in the future.
As we continue our planning process, we’ll be fine-tuning our schedule, looking for feedback from the community, and communicating progress updates throughout the release cycle.
Google Tech Talks November 13, 2007 ABSTRACT Yahoo!’s Exceptional Performance Team has identified 14 best practices for making web pages faster. These best practices have proven to reduce response times of Yahoo! properties by 25-50%. They focus on the front-end, for example, why it’s bad to use “@import” for including stylesheets and why ETags disable browser caching. In this talk I’ll go in-depth on these best practices and the research behind them. I’ll also demonstrate YSlow and do some live performance analysis of popular web sites. Relevant links: Exceptional Performance: developer.yahoo.com YSlow: developer.yahoo.com Speaker: Steve Souders Steve Souders holds down the job of Chief Performance Yahoo! at Yahoo! He’s been at Yahoo! since 2000, working on many of the platforms and products within the company He ran the development team for My Yahoo! before reaching his current position. As Chief Performance Yahoo!, he has developed a set of best practices for making web sites faster. He builds tools for performance analysis and evangelizes these best practices and tools across Yahoo!’s product teams.
Google Tech Talk September 24, 2009 slides: www.slideshare.net Web Exponents: www.youtube.com ABSTRACT Presented by Chris Anderson. CouchDB’s web API and offline replication capabilities make it ideally suited to power a sea-change in the relationships between users and service providers. I’ll give a 10000 foot overview of CouchDB, as well as discuss the benefits and challenges of writing applications that can be replicated transparently from the cloud to local machines. Chris Anderson is an Apache CouchDB committer and co-author of the forthcoming O’Reilly book “CouchDB: The Definitive Guide”. He is a director of couch.io, offering commercial hosting, support, consulting, and custom development. He enjoys working on JavaScript CouchApps which can be peer-replicated just like any other data. Chris is obsessed with bending the physics of the web to give control back to users.
Google Tech Talk May 18, 2009 ABSTRACT Presented by Mark Miller, Waldemar Horwat, and Mike Samuel. Slides for this talk are available from google-caja.googlecode.com Today’s JavaScript is a decent language for writing small scale scripts. But even for beginners, it has too many minefields between what beginners learn and what they need to know. And JavaScript is now increasingly used for serious software engineering projects — straining to carry a load it was not designed for. After 10 years, the world of JavaScript standards is moving again. The next version, EcmaScript 5, is in “final draft standard” status with implementations about to appear. The “Harmony” agreement sets the direction for future versions beyond EcmaScript 5. The “Secure EcmaScript” working group is working towards an EcmaScript 5 subset suitable for the security needs of inline gadgets, mashups, and more. In this first talk, we’ll explain changes in EcmaScript 5, the problems they’re meant to address, the de-facto standards they codify, and how these changes are likely to affect web applications. Waldemar Horwat has been involved with JavaScript standardization and implementation since the 1990′s when he was working on Netscape’s implementation. He is a former editor of the standard and wrote parts of the existing ECMAScript Edition 3 standard. He participates in the ECMA TC39 committee and is the Google representative at the ECMA General Assembly. Mark S. Miller is a research scientist at Google <b>…</b>
I have received a ton of requests for Lightbox2 tutorials. I have gone ahead and created one using Dreamweaver and by the time you watch this video you will be able to setup and edit your very own LightBox 2 JavaScript Photo Gallery. Download Lightbox 2 for free right here: www.huddletogether.com Twitter! www.twitter.com Be sure to check out www.tutvid.com Check out the blog @ http
Google Tech Talks August 17, 2007 ABSTRACT This talk explores all the techniques used to build a robust, reusable, cross-platform JavaScript Library. We’ll look at how to write a solid JavaScript API, show you how to use functional programming to create contained, concise, code, and delve deep into common cross browser issues that you’ll have to solve in order to have a successful library. John Resig is a JavaScript Evangelist, working for the Mozilla Corporation, and the author of the book ‘Pro Javascript Techniques.’ He’s also the creator and lead developer of the jQuery JavaScript library and the co-designer of the FUEL JavaScript library (included in Firefox 3). He’s currently located in…
Google Tech Talks Web Exponents presented by Doug Crockford February 27, 2009 blog post: google-code-updates.blogspot.com JavaScript is a language with more than its share of bad parts. It went from non-existence to global adoption in an alarmingly short period of time. It never had an interval in the lab when it could be tried out and polished. JavaScript has some extraordinarily good parts. In JavaScript there is a beautiful, highly expressive language that is buried under a steaming pile of good intentions and blunders. The best nature of JavaScript was so effectively hidden that for many years the prevailing opinion of JavaScript was that it was an unsightly, incompetent abomination. This session will expose the goodness in JavaScript, an outstanding dynamic programming language. Within the language is an elegant subset that is vastly superior to the language as a whole, being more reliable, readable and maintainable. Speaker: Douglas Crockford Douglas Crockford is a product of our public education system. A registered voter, he owns his own car. He has developed office automation systems. He did research in games and music at Atari. He was Director of Technology at Lucasfilm. He was Director of New Media at Paramount. He was the founder and CEO of Electric Communities/Communities.com. He was founder and CTO of State Software, where he discovered JSON. He is interested in Blissymbolics, a graphical, symbolic language. He is developing a secure programming language. He <b>…</b>
A couple of years ago, web developers were banging their head against the first wall in Ajax: the same-origin policy. While we marveled at the giant step forward enabled by cross-browser support for the XMLHttpRequest object, we quickly bemoaned the fact that there was no way to make a request to a different domain from JavaScript. Everyone setup proxies on their web sites, which was the onset of a new host of open redirect problems, as a way to get around the restriction. Although developers were working around this limitation using server-side proxies as well as other techniques, the community outcry was around allowing native cross-domain Ajax requests. A lot of people are unaware that almost all browsers (Internet Explorer 8+, Firefox 3.5+, Safari 4+, and Chrome) presently support cross-domain Ajax via a protocol called Cross-Origin Resource Sharing.
