The Problem with Native JavaScript APIs
āđāļāļĩāđāļĒāļ§āļāļąāļ eBook āđāļĨāđāļĄāļāļĩāđ
In this report, Nicholas Zakasâconsultant and former front-end tech leader at Yahoo!âprovides a case study to show how different browsers can develop native APIs for the same specification and still end up with different interpretations. Youâll discover how these APIs can tie your code to specific browsers, forcing you to upgrade application logic whenever new browsers and new browser versions are released.
āļŠāļģāļĢāļ§āļāļŦāļāļąāļāļŠāļ·āļāđāļĨāđāļĄāļāļ·āđāļāđ
āļāļēāļĢāđāļŦāđāļāļ°āđāļāļāđāļĨāļ°āļĢāļĩāļ§āļīāļ§
āđāļāļĩāđāļĒāļ§āļāļąāļāļāļđāđāđāļāđāļ
Nicholas C. Zakas is a front-end consultant, author, and speaker. He worked at Yahoo! for almost five years, where he was front-end tech lead for the Yahoo! homepage and a contributor to the YUI library. He is the author of Professional JavaScript for Web Developers (Wrox, 2012), Professional Ajax (Wrox, 2007), and High Performance JavaScript(OâReilly, 2010). Nicholas is a strong advocate for development best practices including progressive enhancement, accessibility, performance, scalability, and maintainability. He blogs regularly at http://www.nczonline.net/ and can be found on Twitter via @slicknet.
