Sponsorised links
This month
June 2009
Run Linux Applications on Windows | PC Plus
When can I use...
Adobe Labs - Adobe BrowserLab
Sponsorised links
May 2009
Testing Software for Web Professionals - Litmus
April 2009
About - cufon - GitHub
When can I use...
March 2009
CSS - Contents and compatibility
Windows: Products Designed for Microsoft Windows
February 2009
7 Fresh and Simple Ways to Test Cross-Browser Compatibility | Freelance Folder
About - cufon - GitHub
When can I use...
IEBlog : Just The Facts: Recap of Compatibility View
C'est ce qui est reprochéSite owners can choose to use the X-UA-Compatible tag to be absolutely declarative about how they’d like their site to display and to map Standards mode pages to IE7 Standards. Use of the X-UA-Compatible tag overrides Compatibility View on the client.
When can I use...
Compatibility tables for features in HTML5, CSS3, SVG and other upcoming web technologies
January 2009
Building desktop Linux applications with JavaScript: Page 1
How to get Cross Browser Compatibility Every Time | Anthony Short | Web Design & Development
December 2008
Let's talk about Python 3.0
Of course, this is causing some people to ask whether it was a good idea; all other things being equal, it’s better to maintain compatibility than to break it, and if the break doesn’t seem to offer anything really major or impressive over the previous compatible version, then it’s natural to ask what, exactly, made this necessary. Jens Afke has rather notably posted some thoughts along those lines, and this post is an attempt to respond and explain, as clearly as I can, why I think Python 3.0 is and will be a good thing even though it’ll create a staggering amount of work for me, my co-workers and my friends and colleagues (since I deal with two large Python 2.x codebases on a daily basis, the migration is not going to be simple or short for me).
