Add your comments
DLS Archives
June 2013
| Sun | Mon | Tue | Wed | Thu | Fri | Sat |
|---|---|---|---|---|---|---|
| 1 | ||||||
| 2 | 3 | 4 | 5 | 6 | 7 | 8 |
| 9 | 10 | 11 | 12 | 13 | 14 | 15 |
| 16 | 17 | 18 | 19 | 20 | 21 | 22 |
| 23 | 24 | 25 | 26 | 27 | 28 | 29 |
| 30 | ||||||
Essential Windows Apps | Do Not Track | Microsoft Office | SayNow | LibreOffice | Zeam Android Launcher | Dead Space iPhone | Firefox 4 Mobile | Firefox 4 Release | PlayStation iPhone App | Excel Tips | Android Launcher | Google One Pass | Dead Space | Google Cloud Print | Songbird for Android | NBA Jam | Internet Explorer 9 | Windows 7 Connector for Mac | Office Mac 2011 | IE9 RC
Gadget News
- Researchers able to predict iOS-generated hotspot passwords, takes under a minute
- Raspberry Pi gets its own media center kit: £46 for easy XBMC and controller (hands-on)
- Bloomberg: Next Surface RT will use Qualcomm chip, may come in multiple versions
- Evernote Web Clipper's new Gmail function saves copies of emails and attachments
Reader Comments (Page 1 of 1)
(Unverified)Oct 23rd 2006 1:15PM
While it is true that for pragmatic reasons we have to support IE whether we like it or not, it is certainly not the case that "If you are a real DESIGNER or PROGRAMMER you know that you design for IE and then make it work in FireFox", as Jason seems to believe.
I am a 'real' web designer, and like all 'real designers' that I know, I develop for Firefox or Safari first and then add the necessary hacks for IE. I do this because I know that if I build a site using standards-compliant code then it will work on 90% of browsers (even if together they only form 15% of the market) and that I can then (relatively) easily work around the bizarre bugs and behaviours in IE to make it work for that too.
If I was to design for IE first, I would still have to work around all its weird bugs, but once I'd finished I would have a site that works reliably in exactly one version of IE for Windows, and I'd know that since all browsers (including IE) are moving towards better standards compliance, my site will become increasingly broken on an increasing number of browsers as time goes on.
To my mind, anyone who believes that they have a secure career designing broken code for a buggy six-year-old browser provided by one vendor who is rapidly losing credibility and market share, is extremely naive, and as a prospective employer I would regard the value of their so-called 'experience' as questionable at best.
There is no question that IE dominates both the past and present of the web. I don't know any competent web developer who believes that IE - as it stands - has any place in the future of it.