Jeffrey Zeldman interviews Jake Archibald of Google Chrome about upcoming web caching standards, how the network connection is merely a layer of progressive enhancement and why you should build your app offline, communicating with non-developers, accessibility standards at BBC and The Guardian, the forking of Webkit, native versus web part 99, and why the much-linked article "Why Mobile Web Apps are Slow" proves no such thing.
Tagged with “browsers” (14)
Chrome recently announced they will replacing the webkit rendering engine with a new one, named Blink. What’s up with that? To find out, Chris Wilson and Paul Irish join Jen Simmons to explain rendering engines and vendor prefixes.
Tantek Çelik talks about creating Internet Explorer 5 for Mac, doctype switching, a bit about semantic data formats, and much more.
What’s the best way to handle responsive images? There’s been a lot of discussion flying around over the last many months, big debates and fast changes… where have we landed? What’s coming in the future? Responsive Images Community Group chair Mat Marquis joins Jen Simmons to sort it all out.
While at NDC, Carl and Richard talk to Remy Sharp about HTML 5. Remy discusses the state of things, how the diversity of browsers is as much a strength as a problem. He digs into the idea that you need to build your web app for the audience you have - perhaps it needs more support for older browsers, or focus on the latest features for the newest browsers. Check out the great collection of links to different services and sites that Remy mentions in the discussion!
The browser wars panel has been an SxSW institution, and gives us a forum to bring browser vendors to to the table to take stock of new developments on the web. As in years past, we’ll bring Mozilla (Firefox), Google (Chrome), Microsoft (IE), Opera (Opera), and maybe Apple (Safari) to the table to speak of developments on the web, and to share their unique perspectives as those who make the platforms on which the web is viewed.
Our tag line this year places tongue firmly in cheek. Interesting chatter continues about applications on the web. What’s the story with browser-based app stores? While we’re at it, microdata has been embraced by Google, Microsoft, and Yahoo, but the web seems underwhelmed by schema.org. And why hasn’t HTML5 video changed our lives already, and why aren’t there any real peer-to-peer apps on the web yet? And, is WebGL ready or just sodden in hype? We’ll get candid on this panel, and take stock of the era of modern browsers, mobile apps, and Angry Birds.
In the early days of CSS the web industry cut its teeth on blogs and small personal sites. Much of the methodology still considered best-practise today originated from the experiences of developers working alone, often on a single small style sheet, with few of the constraints that come from working with large distributed teams on large continually changing web projects.
The mechanics of CSS are relatively simple. But creating large maintainable systems with it is still an unsolved problem. For larger sites, CSS is a difficult and complex component of the codebase to manage and maintain. It’s difficult to document patterns, and it’s difficult for developers unfamiliar with the code to contribute safely.
How can we do better? What are the CSS best practises that are letting us down and that we must shake off? How can we take a more precise, structured, engineering-driven approach to writing CSS to keep it bug-free, performant, and most importantly, maintainable?
The range of devices accessing the web is increasing. We are faced with a choice in how we deal with this diversity. We can either fracture the web by designing a multitude of device-specific silos, or we can embrace the flexibility of the web and create experiences that can adapt to any device or browser.
With HTML5, we can now cache our applications and the data that goes with them. This means our favourite programming platform can now be used to build apps that work offline, survive intermittent downtimes, and gain in performance from cached content. In this session we’ll get hands-on with the application cache to make the app run when it’s not online. We’ll check out the techniques for client-side persistence: web storage and indexed database. Finally, we’ll look at the latest techniques for file access — reading and writing files on the user’s hard drive from a web app is being defined by web standards and implemented in today’s modern browsers.
Michael Mahemoff is a Chrome Developer Advocate for Google, based in London, always looking at ways to make the web a more habitable place for users and developers alike. He’s been programming on the web since the mid ’90s, in a range of public-facing and enterprise (Java, what else?) contexts, and is the author of Ajax Design Patterns (O’Reilly, 2006) and a blogger for Ajaxian.com. Server side, he’s mostly a Ruby, PHP, and NodeJS guy and sushi is his preferred coding fuel. Michael holds a PhD from the University of Melbourne, covering software design patterns for improving user experience.
In this session, representatives from major browser vendors including Chrome, Microsoft, Opera and the W3C will pull back the curtain revealing some of the challenges with implementation and interoperability. The goal is to have designers and developers get a glimpse into how CSS has struggled and finally gained its footing as the presentation layer in everything we do for the Web.
Elika Etemad, Invited Expert, W3C Invited Experts. Elika J. Etemad (fantasai) is a W3C Invited Expert on the CSS Working Group and a longtime contributor to the Mozilla Project. She edits CSS specifications, does layout engine QA, and occasionally codes for Gecko. Within the CSSWG she specializes in internationalization, testing, and generally getting things done.
Molly Holzschlag, Developer Rel, Opera Software. Having achieved a modicum of balance after her midlife crisis, Molly decided to finally get a job. She is now a Web Evangelist focusing on developer relations for the upstart Norwegian browser company, Opera Software. Earlier in life, Molly avoided a regular job including those silly start-up ventures and chose instead to write a lot of books and articles and stuff on Web standards, and talk a lot about them, too. She now avoids the former, while the latter is an ongoing inevitability. To learn more about Molly and her work, you can check out her blog at molly.com or interact with her on Twitter @mollydotcom. Better yet, come have a chat F2F at SXSW!
Sylvain Galineau, Program Manager, Microsoft. Sylvain spent many years working on web application servers and now helps design Internet Explorer. He represents Microsoft on the CSS Working Group and will buy everyone a round when IE6 goes away. Everyone.
Page 1 of 2Older