Informationweek Influencer
Paul Irish (@paul_irish)
- Twitter Bio:
- I want the web to win • Chrome dev relations • currently fascinated with front-end tooling and browser devtools • big fan of rye, research and whimsy
- Location:
- San Francisco
- Website:
- http://paulirish.com
Paul Irish's Selections From the Web
On the same day as announcing that Opera has 300 million users, we're also announcing that for all new products Opera will use WebKit as its rendering engine and V8 as its JavaScript engine. It's built using the open-source Chromium browser as one of its components. Of course, a browser is much more than just a renderer and a JS engine, so this is primarily an "under the hood" change. Consumers will initially notice better site compatibilty, especially with mobile-facing sites - many of which have only been tested in WebKit browsers. The first product will be for Smartphones, which we'll demonstrate at Mobile World Congress in Barcelona at the
For many of us developers, WebKit is a black box. We throw HTML, CSS, JS and a bunch of assets at it, and WebKit, somehow.. magically, gives us a webpage that looks and works well. But in fact, as my colleague Ilya Grigorik puts it…Now, especially with the news that Opera has moved to WebKit, we have a lot of WebKit browsers out there, but its pretty hard to know what they share and where they part ways. Below we’ll hopefully shine some light on this. As a result you’ll be able to diagnose browser differences better, report bugs at the right tracker, and understand how to develop against specific browsers more effectively.There are different
Disclaimer: Having a background in C-like languages like Java, JavaScript, PHP, and C# has caused a problem for me to embrace languages like Python, Ruby, and CoffeeScript. I'd consider myself more of a laggard than a trend-setter when it comes to new technologies and languages. I've often questioned why? even when the answer is clear. This attitude has made me biased against CoffeeScript, even though it provides useful benefits and features that provide justification to why a developer would maintain a codebase with it. While I may not be a fan of coding with CoffeeScript, I'm absolutely hating writing configurations with JavaScript. There
University-level education has never really touched too directly on what we do as frontend developers. I know I was self-taught in the ways of the browser, as were all of my friends. Luckily the sort of webapp work we do these days is quite sophisticated so those CS graduates bring much of the great ideas to the JavaScript community. (Alex Sexton has been a personal inspiration here)Early last year, something clicked in my head when I saw this video: Crossing the Chasm: Pitching Security Research to Mainstream Browser Vendors.You mean.. there are academics… who are doing research on browsers.. in universities? My my! You mean bright minds think
Preface: Nothing in this post is necessarily new, or even anything I thought of first (save for a name or two). However, I’m writing it because I’d like to start building some consistency and naming conventions around a few of the techniques that I am using (and are becoming more common), as well as document some processes that I find helpful.Much of this comes from my experience deploying applications at Bazaarvoice as a large third party vendor, and should probably be tailored to your specific environment. I’m sure someone does the opposite of me in each step of this with good results.Also, I fully understand the irony of loading a few MBs
The "final" URL that the request is made on. For example, one may enter "example.com" for a URL. Internally, our system will go through a series of forwards and/or redirects, and may end up with "http://www.example.com" as the effective URL.
The total size (in KB) of the requested URL. Note that this is the size of the initial page, and not the total size of all resources on the site. Resource statistics are seen in a separate table.
The URL of an individual resource. These are links directly to resources of the site (for example, CSS + javascript files).
The HTTP code returned by the remote server when
Upcoming Events
Live Events
- Information Streams - Going Beyond the Activity Stream - E2 Conference Boston
- How to Choose a SaaS Vendor - E2 Conference Boston
- The E2 Social Business Leaders - E2 Conference Boston - E2 Conference Boston
- Mobile Connect - E2 Conference Boston - E2 Conference Boston
- Evaluating Emerging Technologies for the Enterprise - E2 Conference Boston
This Week's Issue
Free Print Subscription
SubscribeSpecial Issue
Current Government Issue
- The Government CIO 25: These influential and accomplished government IT leaders are finding ways to be cost efficient and still innovate.
- Rethink Video Surveillance: It's not just about networked cameras anymore. New technology provides analytics, automation, facial recognition, real-time alerts and situational-awareness capabilities.
- Read the Current Issue
Featured Whitepapers
Featured Reports
