InfoQ

InfoQ

News

My Bookmarks

Login or Register to enable bookmarks for unlimited time.

The content has been bookmarked!

There was an error bookmarking this content! Please retry.

Internet Explorer 8 Beta 1 Released to Developers

Posted by James Vastbinder on Mar 11, 2008

Sections
Enterprise Architecture,
Operations & Infrastructure,
Process & Practices,
Architecture & Design,
Development
Topics
Announcements ,
.NET
Tags
Microsoft ,
Standardization

Last week on March 5th, Microsoft released beta 1 of Internet Explorer 8.  This beta currently supports Windows XP/Windows Server 2003, Windows Vista and Windows Server 2008. 

This version of Internet Explorer is now standards compliant and can operate in three distinct rendering modes: Quirks mode, IE7 mode, and IE8 mode which is the W3C standards compliant mode.  Quirks mode is aptly named and refers to IE5 legacy compatibility.

New features include:

  • Developer Toolbar for FireBug-like debugging
  • Favorites Bar
  • Automatic Crash Recovery
  • Activities
  • WebSlices
  • An improved Phishing Filter 
  • Improved Script Performance

Rick Strahl lauded the addition of the Developer Toolbar for IE8:

This is a very worthwhile improvement IMHO because the debugging experience in IE has always been one of pain having to go through dialog pop ups and really to get anything useful having to run the Visual Studio script debugger.

And then pointed out areas for improvement:

I would like to see one additional step taken though and that is to get rid of the modal dialog if script debugging is enabled and rather have a more FireBug like model where you can see that an error occurred with a way to click the error icon and then be transported into the this developer toolbar debugger window - preferably to the appropriate line of code as FireBug does. This is easily one of the nicest and most productive features in FireBug.

On a similar note Jeff King, a Microsoft Program Manager, pointed out a useful tip the Visual Studio Web Tools team added to Visual Studio 2008 in anticipation of IE8.

IE8 now enables debugging on-demand.  Thanks to a feature we tucked into VS2008 about 1/2 year ago in anticipation, when you F5, VS gives a hint to IE to flip on debugging... just for that tab you are on.  This means you no longer need to leave script debugging enabled in IE.  VS will do it for you.  Simple.

Special thanks to the debugger folks and the IE team for lining this one up!

Links to Developer resources for IE8 provided by John Hrvatin, Microsoft IE Program Manager:

anticipated features by Vasudevan M Posted
  1. Back to top

    anticipated features

    by Vasudevan M

    Is there anything added about "resumable or retry-able" file download option? This is something which is highly anticipated. Yes modal script error dialog boxes are very irritating. Another option I would like is to have easier access to enable or disable pictures and plugins on pages.

Educational Content

New-age Transactional Systems - Not Your Grandpa's OLTP

John Hugg discusses high volume transaction processing applications with high and low frequency profiles, and how VoltDB can be used for that purpose.

Cool Code

Kevlin Henney examines code samples to see what can be learned from them starting from the premise that one won’t write great code unless he knows how to read it.

Collaboration: At the Extremities of Extreme

Jason Ayers share the observations he made watching a team of developers collaborating in real time on the same code base, pushing XP, pair programming and continuous integration to their extremes.

Yesod Web Framework

Michael Snoyman presents Yesod, a web framework written in Haskell and containing a web server, templating, ORM, libraries (templating, gravatar, etc.).

Transactions without Transactions

Richard Kreuter and Kyle Banker on how to avoid classical RDBMS transactional systems by using compensation mechanisms, transactional messaging or transactional procedures.

Attila Szegedi on JVM and GC Performance Tuning at Twitter

Attila Szegedi talks about performance tuning Java and Scala programs at Twitter: how to approach GC problems, the importance of asynchronous I/O, when to use MySQL/Cassandra/Redis, and much more.

10 tips on how to prevent business value risk

One category of risk that project teams need to ensure they address is business value failure – delivering a product that fails to provide value for the business investor.

Interview: Software Systems Architecture: Working With Stakeholders Using Viewpoints and Perspectives

InfoQ spoke to the authors of Software Systems Architecture on a couple of new topics, the System Context viewpoint and Agile, which have been added to the second edition.