bourbon_sensei
10-26-2006, 01:38 PM
With the launch of IE7 underway enthusiasts are already enjoying a glance of the <st1>Vista</st1> branded browser, eyes shift however in anticipation of the advent of the next Microsoft browser release. IE7 was promising although it suffered attacks and was exploited through vulnerabilities as is becoming the trademark of most applications bearing the Microsoft name, I can most definitely say that IE7 quenched the thirst of most longing for a “good” IE browser. With a mixture of good looks and stability IE7 brings users closer and builds up even more anticipation of the hype that is Windows Vista. Looking past <st1>Vista</st1> we now gaze upon the advent of IE8.<o></o>
<o></o>
Original Article:<o></o>
<o></o>
While the Microsoft-sanctioned name of the next version of Internet Explorer (IE) is IE "Next," it seems it will likely be christened IE 8.0.<o></o>
That's according to Chris Wilson, the new platform architect for IE. (IE-team veteran Wilson, until a few days ago, was the group platform manager of IE. In his new role, <st1:city w:st="on"><st1>Wilson</st1></st1:city> will be spending his time focusing on making IE a better Web-development platform.)<o></o>
<st1:city w:st="on">Wilson</st1:city> delivered a couple of addresses at the Ajax Experience 2006 conference in <st1:city w:st="on"><st1>Boston</st1></st1:city> this week. In addition to dropping the IE 8.0 name, <st1:city w:st="on"><st1>Wilson</st1> </st1:city>shared a few other IE-related tidbits, too:<o></o>
* In the first four days following the release of the final IE 7.0 bits to the Web, 3 million copies were downloaded. And that's before Microsoft began pushing it to users via Automatic Updates.<o></o>
"IE 7 does more than fix minor features," <st1:city w:st="on"><st1>Wilson</st1></st1:city> said. "It maks <st1:city w:st="on"><st1>Ajax</st1></st1:city> fun to develop on."<o></o>
* As of last month, 90 percent of Windows users were running Windows XP or Windows Server 2003, according to <st1:city w:st="on"><st1>Wilson</st1>.</st1:city> This means Microsoft increasingly will be assuming that developers are — and should be — designing for newer versions of Windows and not worrying so much about older releases.<o></o>
* Currently, about one-third of the browser-compatibility problems encountered by IE 7 are attributable to applications and Web sites assuming IE 6.0 as the default browser. This has been a big problem for online banking applications, <st1:city w:st="on"><st1>Wilson</st1> </st1:city>conceded.<o>
</o> While <st1:city w:st="on"><st1>Wilson</st1></st1:city> didn't share many meaty IE 8.0 details, he noted that security, privacy and compatibility will all be top priorities in the next IE release, which is expected some time in the next 12-18 months.<o></o>
"Mash-ups will continue to drive innovation. Componentization and semantic tagging of data will be supported,"<st1:city w:st="on"><st1></st1></st1:city> told the Ajax Experience crowd. <st1:city w:st="on"><st1>Wilson</st1> </st1:city>touted the harnessing of microformats, like Microsoft has done with its Live Clipboard effort, as "real world stuff" that will "make the Web much more usable."<o></o>
"Microformats add meaning to content in HTML," <st1:city w:st="on"><st1>Wilson</st1> </st1:city>said.<o></o>
Wilson sounded a few warning bells, as well, telling the Ajax-friendly crowd that the Ajax programming model has "increased attack vectors on the Web," given that it is easier for hackers to get directly at content and data sources.<o></o>
And while Web frameworks can help developers, by providing a base for more rapid development and application semantics, they also can create a "<st1>Tower</st1> of <st1>Babe</st1>l" situation for developers attempting to integrate applications developed with different frameworks, <st1:city w:st="on"><st1>Wilson</st1> </st1:city>said.<o></o>
He also noted that one of the most commonly requested IE features — the ability to run side-by-side versions of IE on the same machine — is not trivial. <st1:city w:st="on"><st1>Wilson</st1> </st1:city>didn't say this, but I'd say don't count on it showing up in IE 8.0.)<o></o>
"We (IE) are a set of system DLLs that are used by other parts of the system, so this makes it really hard," <st1:city w:st="on"><st1>Wilson</st1> </st1:city>said. "We are trying to figure out how to make IE capable of this in the future."<o></o>
For now, the best solution is virtualization, he conceded. And while "Virtual PC is now free, we are still trying to figure out the story around images and the licensing of images," <st1:city w:st="on"><st1>Wilson</st1></st1:city> said.<o></o>
It also sounds as if IE support for XHTML is not going to be an IE 8.0 thing.<o>
</o> "We don't want to do a half-formed job" of XHTML support, <st1:city w:st="on"><st1>Wilson</st1></st1:city> said. He did note that Microsoft is testing a parser and experimenting with integrating multiple schema, however.<o></o>
What about JavaScript support?<o></o>
"We've started working on JavaScript again at the company" <st1:city w:st="on"><st1>Wison</st1> </st1:city>said. But the question remains: What do developers and users want JavaScript for? The answer to that question "will determine if we make JavaScript 2 part of our priority list," he said.<o></o><o></o>
<o></o>
Original Article:<o></o>
<o></o>
While the Microsoft-sanctioned name of the next version of Internet Explorer (IE) is IE "Next," it seems it will likely be christened IE 8.0.<o></o>
That's according to Chris Wilson, the new platform architect for IE. (IE-team veteran Wilson, until a few days ago, was the group platform manager of IE. In his new role, <st1:city w:st="on"><st1>Wilson</st1></st1:city> will be spending his time focusing on making IE a better Web-development platform.)<o></o>
<st1:city w:st="on">Wilson</st1:city> delivered a couple of addresses at the Ajax Experience 2006 conference in <st1:city w:st="on"><st1>Boston</st1></st1:city> this week. In addition to dropping the IE 8.0 name, <st1:city w:st="on"><st1>Wilson</st1> </st1:city>shared a few other IE-related tidbits, too:<o></o>
* In the first four days following the release of the final IE 7.0 bits to the Web, 3 million copies were downloaded. And that's before Microsoft began pushing it to users via Automatic Updates.<o></o>
"IE 7 does more than fix minor features," <st1:city w:st="on"><st1>Wilson</st1></st1:city> said. "It maks <st1:city w:st="on"><st1>Ajax</st1></st1:city> fun to develop on."<o></o>
* As of last month, 90 percent of Windows users were running Windows XP or Windows Server 2003, according to <st1:city w:st="on"><st1>Wilson</st1>.</st1:city> This means Microsoft increasingly will be assuming that developers are — and should be — designing for newer versions of Windows and not worrying so much about older releases.<o></o>
* Currently, about one-third of the browser-compatibility problems encountered by IE 7 are attributable to applications and Web sites assuming IE 6.0 as the default browser. This has been a big problem for online banking applications, <st1:city w:st="on"><st1>Wilson</st1> </st1:city>conceded.<o>
</o> While <st1:city w:st="on"><st1>Wilson</st1></st1:city> didn't share many meaty IE 8.0 details, he noted that security, privacy and compatibility will all be top priorities in the next IE release, which is expected some time in the next 12-18 months.<o></o>
"Mash-ups will continue to drive innovation. Componentization and semantic tagging of data will be supported,"<st1:city w:st="on"><st1></st1></st1:city> told the Ajax Experience crowd. <st1:city w:st="on"><st1>Wilson</st1> </st1:city>touted the harnessing of microformats, like Microsoft has done with its Live Clipboard effort, as "real world stuff" that will "make the Web much more usable."<o></o>
"Microformats add meaning to content in HTML," <st1:city w:st="on"><st1>Wilson</st1> </st1:city>said.<o></o>
Wilson sounded a few warning bells, as well, telling the Ajax-friendly crowd that the Ajax programming model has "increased attack vectors on the Web," given that it is easier for hackers to get directly at content and data sources.<o></o>
And while Web frameworks can help developers, by providing a base for more rapid development and application semantics, they also can create a "<st1>Tower</st1> of <st1>Babe</st1>l" situation for developers attempting to integrate applications developed with different frameworks, <st1:city w:st="on"><st1>Wilson</st1> </st1:city>said.<o></o>
He also noted that one of the most commonly requested IE features — the ability to run side-by-side versions of IE on the same machine — is not trivial. <st1:city w:st="on"><st1>Wilson</st1> </st1:city>didn't say this, but I'd say don't count on it showing up in IE 8.0.)<o></o>
"We (IE) are a set of system DLLs that are used by other parts of the system, so this makes it really hard," <st1:city w:st="on"><st1>Wilson</st1> </st1:city>said. "We are trying to figure out how to make IE capable of this in the future."<o></o>
For now, the best solution is virtualization, he conceded. And while "Virtual PC is now free, we are still trying to figure out the story around images and the licensing of images," <st1:city w:st="on"><st1>Wilson</st1></st1:city> said.<o></o>
It also sounds as if IE support for XHTML is not going to be an IE 8.0 thing.<o>
</o> "We don't want to do a half-formed job" of XHTML support, <st1:city w:st="on"><st1>Wilson</st1></st1:city> said. He did note that Microsoft is testing a parser and experimenting with integrating multiple schema, however.<o></o>
What about JavaScript support?<o></o>
"We've started working on JavaScript again at the company" <st1:city w:st="on"><st1>Wison</st1> </st1:city>said. But the question remains: What do developers and users want JavaScript for? The answer to that question "will determine if we make JavaScript 2 part of our priority list," he said.<o></o><o></o>