Browser Smackdown: Side-by-Side Feature Comparison
272342
As part of our Browser Smackdown, here's a close-up look at how Firefox 2, Internet Explorer 7, Opera 9 and Safari 2 handle popular browsing features and functions.
385734
This free browser has more features than the most recent version of Internet Explorer. Check out our first impressions. Mozilla.org, an open-source effort created by some of the original pre-AOL Netscape designers
638963
This is an updated and revised annotation to the HTML 4.01 Specification published by the World Wide Web Consortium (W3C), detailing the differences between the specification and its implementation in Netscape Navigator 7.2 and Microsoft Internet Explorer 6.0. By Lee Underwood. 1116
414512
Results from competing engines appear side by side on Australian search site SearchBoth.
316418
Preview version seeks best of both worlds, is based on Firefox.
592829
Firefox fans can get a preview look at the next version of their favorite browser now.
687388
The latest release of Mozilla's lightweight browser for the Mac hints at a major upgrade around the corner. In Monkey Bites.
337538
How far is too far when it comes to the freedom of software? Plus: Palm slipping, Windows sliding.
5345
Microsoft's popular Internet Explorer has a serious rival in the Firefox browser.
385267
a little -- while would-be rival Mozilla gains. A new report says the number of Web visitors using IE dropped from
481653
I'm back, with a very interesting topic too!  Joel Spolsky, ex-Microsoft Manager and software engineering guru has a new essay, How Microsoft Lost the API War that is creating quite a big storm in the blogging communitiy.  Joel posits that the priests in the holy Temple of Microsoft have lost their way, because it has split into two factions, and the wrong faction is winning. One faction worships on the alter of backward compatibility, while the other is led by fervent priests who are proselytizing to raise up the new gods of .NET and Longhorn. Joel suggests that the new gods will cause the destruction of the holy Temple because Microsoft's great victories were built on the altar of keeping customers happy with backward compatibility. Furthermore the old gods of the Windows API continue to grow more grotesque and cruel with the passing of time, driving former worshipers into the arms of the friendlier gods of World Wide Web.  This story sounds extremely plausible. I must admit that i fit the profile of the developer who used to develop on the Window's API, is familiar with COM and Win32 who now develops mostly using PHP and Python. However I continue to develop and maintain Windows apps that keep our customers happy, and we still plan to develop new Windows apps. Some points:  Temple of the Blind? Firstly, Microsoft is still a compelling place to work for to people who feel that they can make a difference. The Temple continues to attract talented people with a Unix background. For example we have the recent hiring of Ward Cunningham, author of the Wiki.  Microsoft is still able to keep talented people like Raymond Chen, and others like him who continue to look after the Windows API, and Longhorn apparently will still give high priority to backward compatibility. Open sourcerers like Miguel Icaza are sufficiently attracted to the .NET vision to stake their careers on Mono. Longhorn and .NET are compelling technologies, so even if Win32 is not so cute anymore, M'soft is providing something that remains very attractive.  What i do see M'soft doing wrong is that they aren't disseminating the .NET runtime fast enough. It remains an optional install in XP Service Pack 2 for example. Also their IE dev team appears to be hog-tied due to political reasons; nevertheless IE remains good enough, particularly when I can embed IE as an activeX control, something I cannot do with Mozilla (AFAIK) - Update: I'm wrong.  Temple of the Spider?  Secondly, people don't merely use a web browser. They run the web browser in the OS.  So let me ask you, if you are using DreamWeaver or HomeSite or Photoshop or vi or emacs or Gimp, how many of you are willing to give it up for a java applet (or whatever your favorite technology is) running in your web-browser? Precisely.  Temple of the Abandoned?  Third, Joel makes the claim that developers are not developing to the Windows API. Well he could be right. But I bet a lot of them are still calling Win32.  If you are using a framework or IDE like Delphi or wxWindows (or .NET or VB) then you certainly are insulated from the Windows API, but that doesn't mean that you're not calling the Windows API all the time. I don't see Borland dropping their Windows version of Delphi at any point in time.   In fact, the fact that many developers are using some form of framework is a compelling argument for Microsoft to enhance the .NET framework to attract developers who are using other frameworks.  Today, not that many students learn x86 assembler, but that doesn't mean that Intel lost the CPU wars. Just because fewer people are learning Win32 doesn't mean Microsoft has lost the API wars, if the frameworks run predominantly on Win32.  Temple of the Lost  Joel even warns you in the beginning that "because I'm talking about big trends, I need to exaggerate and generalize". But you still get sucked in because Joel Spolsky is a first-class writer, in the same order as Philip Greenspun or Eric Raymond. That makes him so persuasive and plausible. But this is not Indiana Jones and doomed temples, but Steve Jobs and reality distortion fields.  Other opinions:  Harry Fuecks (PHP is ASP's upgrade path),  Dennis Hamilton (M'soft is just covering all bases), Robert McLaws (Joel is wrong in 7 points), Oliver Travers (the web is not good enough), One Run-time to Rule them all....
474830
When hard a work coding, browser windows with manual entries have a nasty habit of multiplying (at least when I work). So, neededless to say, I was happy to find GotAPI.com, a site that compiles the reference materials for several different web development languages into one handy browser window.  The page, by default, searches HTML resources, including the W3C specs and Microsoft's MSDN materials. Those and the w3schools website show up often in the other languages available - CSS, XSL, XML, and XPath. The PHP manual that's referenced is just pulled from the PHP.net site, but it's still nice to have it all right there.  When searching, a "suggeted terms" box pops up to help you narrow down the search faster. It searches not only the beginnings of the words for your term, but it looks inside them as well, matching anywhere.   It would be nice if the site had some kind of bookmarking system built into it - then you could keep a reference and just flip back and forth between the pages with a single click of the mouse.
238632
The future appears rosy for Firefox. Just two years after its start, and even before reaching version 1.0 (now imminent), the little open source browser has already left behind its elder
208782
Will the search engine leviathan end the hunt for a commercial hybrid? In Autopia.
279167
In my Firefox series last week, I overlooked one of the browser's most powerful search functions: An 'always on' find as you type feature.
740071
A closer look at some behind-the-scenes tweaks for speeding up page loads, reducing memory drain and making the interface behave the way you want it to.
503397
Despite the options available with HTML, CSS, and JavaScript, accommodating their differences can be maddening. Enter Silverlight, a plug-in for multiple Web browsers on multiple platforms that makes it easier to create rich content. By Adam Nathan. 1202