The Browsium team will be at Microsoft TechEd in Atlanta May 16-19. We have a booth on the exhibit floor and will be showing the latest features in UniBrows along with some other cool new technologies we’ve been working on in our labs.
You’ll find us in Booth #1736. Email us at email@example.com to schedule a meeting or just stop by during exhibition hours and we’ll make room to meet with you.
We’re often asked a very simple question: “Doesn’t UniBrows promote continued use of IE6 rather than help companies eradicate it?” Very much to the contrary, we believe UniBrows helps organizations reduce reliance on IE6 more quickly, cleanly, and optimally than any of the alternatives.
How do we make this happen? The answer is at the core of how UniBrows delivers Web Application Continuity by taking an approach that centers on containment of legacy browser components. By this we mean that UniBrows restricts IE6 usage (and exposure) to only the line-of-business applications designated by IT that require the native IE6 engine so that they may function properly. All other sites, whether they are located on an intranet or the Internet, are accessed using the most modern browser engine available from Microsoft – IE8 on Windows XP and IE8 or IE9 on Windows 7.
UniBrows not only reduces the IE6 attack surface by enabling organizations to carefully control the legacy engine’s exposure. As an added bonus, our technology helps drive IE6 usage on the web to zero by providing organizations with the tools needed to manage their browser and web application upgrades more smoothly than other solutions. Nothing helps Microsoft’s IE6 Countdown initiative succeed faster than UniBrows.
Most organizations we speak with need the IE6 engine and legacy add-ons for only a handful of applications – but they are mission critical. It’s this ‘vocal minority’ holding back the company, making them unable to move their browser platform forward and putting the company at unnecessary risk every day. In addition, running IE6 as the primary browser severely limits the ability to innovate or adopt the latest technologies so many companies are forced to continue building on top of the IE6 platform – which just serves to extend its life even further into the future. By comparison, companies running UniBrows for their legacy applications are able to deploy a standards-based, modern browser platform now, while leaving IE6 locked away in the closet.
But there are other ways to limit use of IE6. How do these other approaches stack up to UniBrows? Let’s take a quick look at each:
We know many web developers would love to go back in time and kill IE6 before it ever shipped. As far as we know Doc Brown’s flux capacitor didn’t really ship in 1985 and Skynet’s Terminator T1000 is still in early beta testing. So rewriting browser history, while fun to discuss at tweet-ups, does not seem to be a viable option.
Returning to the premise of this post, it appears there really is only one way to eradicate IE6 from the web today. Contain it … with UniBrows.
We’re here in Las Vegas at Microsoft’s MIX11 web developer conference showing off some of our newest browser compatibility solutions. This morning Microsoft surprised all the attendees by announcing the release of a platform preview of IE10, just one month after the release of IE9.
Microsoft’s accelerated development of IE was welcomed by many attendees who want to see Redmond catch up and even lead the charge on the implementation of web standards. This new rapid release cadence by Microsoft is great for web developers who would love to see all browsers on equal footing relative to web standards. It’s also good for consumers who will see richer, more beautiful websites as leading-edge web developers take advantage of this innovation. But what about enterprises? What do they think of the rapid pace of web standards development, which by its nature, means legacy support is almost always left behind?
An article about rapid development of Firefox in Computerworld last November captured the spirit of this dilemma quite clearly:
Automatic updates and pushing the latest version out may work fine for consumers, but businesses–especially large businesses–are much slower to adapt and adopt new applications. Part of the reason that it is so hard to kill IE6 is that businesses built internal Web applications to be compatible with IE6–they are invested in that outdated browser platform and reluctant to invest the time, money, and effort necessary to test and deploy a more current browser. Imagine how difficult it will be to introduce a new major browser release every few months.
A problem for sure. The cost and time required to assess and fix web applications for even the most minor platform changes can be enormous. But Browsium was created with the mission to solve this problem for enterprise IT, enabling them to take advantage of new technology innovations without fear of breaking their fragile web applications. We call this Web Application Continuity. It extends the ROI of already deployed and paid-for applications by freezing the platform for Web applications at a ‘known good state’, and providing granular control for side-by-side compatibility regardless of the browser engine or configuration required by each application. No other solution provides this level of compatibility and control.
While web developers applaud, and enterprises say “no más”, we say “bring on the platform improvements”. Because you can have your cake and eat it too.