Saturday, April 23, 2011
Monday, April 18, 2011
A Quick Glance at Firefox in 2011
So back in February I posted about Mozilla’s new release schedule for Firefox in 2011. At that time the actual schedule hadn’t been fully drawn up yet as they were waiting on the release of Firefox 4. Now, I did mention the different channels or phases of the release schedule on the Firefox 4 Aurora Release post. Again these channels or phases are: Nightly, Aurora, Beta and Release and normally each phases lasts 6-weeks and will usually start on a Tuesday (except Nightly which will be the day after the Aurora release of the prior version). Firefox 5 is on a shorter schedule. So here is the plan for 2011 (and this could very well change):
Firefox 5
Firefox 5
- Nightly: March 23rd
- Aurora: April 12th
- Beta: May 17th
- Release: June 21st
- Nightly: April 13th
- Aurora: May 24th
- Beta: July 4th
- Release: August 16th
- Nightly: May 25th
- Aurora: July 4th
- Beta: August 16th
- Release: September 27th
- Nightly: July 5th.
- Aurora: August 16th
- Beta: September 27th
- Release: November 8th
By The Guru
Wednesday, April 13, 2011
Next For Chrome GUI: Scrolling Tabs, Full Screen, Touch Evolution
Google is currently working on apparently more than 1000 minor and major modifications of Chrome browser features and we are seeing plenty of new items hitting Chromium releases this week. In the past week alone, we noticed about three dozen core and GUI changes that highlight the fast pace of Google’s browser team.
There are few application areas at this time that move as quickly as browsers. After a number of substantial improvements especially in Chrome 6/7 and 8, it almost appeared that the Chrome team took a breather with version 9 and 10 and slowed the development speed. However, the opposite is the case, as Chrome’s nightly builds are advancing quickly.
If you are running one of the recent Chromium 12 nightly builds, you are already used to the new touch tabs that let you select you multiple homepages with app icons, similar how you would organize a sfumartphone app screen. A “Recently Closed” option was added a few days ago that is now fully functional and opens a pop-up window with a listing of the pages that were closed. The individual screens are now labeled. The underlying Webkit now supports Windows 7 gestures. There is also note of new fav icons for the touch interface that will be 32 x 32 pixels in size, up from the standard 16 x 16 pixel size. Another welcome upgrade is the fact that Webkit can now support Chrome’s Skia backend, which will be used to enable PDF rendering in Chrome’s print preview.
The primary tabs are also seeing some changes. Tab scrolling is being introduced in horizontal and side tabs and the tab labeling now fades on Chrome for Windows as it does on the Mac version. Multi-tab-Select is also moving forward (by using SHIFT or CTRL). Not yet visible is a new full screen button that forced the Chrome team to move the profile button on the right top a bit to the left. Expect more focus on multi-profiles in Chrome, which should be supported by default in Chrome soon (you need to run the Google Pack to use more than profile at any given time today.)
There are plenty of relatively quiet, but ongoing performance upgrades. We discussed yesterday the integration of SPDY, but there are also smaller efforts such as the enhancement of simple drawing capabilities as well as more significant upgrades, such as the accelerated WebM encoder Bali, which was released about a month ago. Depending on the platform, Bali is about 30 – 40% faster than the preceding WerbM encoder, according to Google. We should note that Google almost exclusively shows ARM hardware to highlight the performance of Bali, which lets us still believe that now only will Chrome OS get a touch interface, but Google will also bringing a version of the Chrome browser to Android in the foreseeable time.
Also, I should mention some changes to the content security policy that addresses Chrome’s needs to be much more attractive for corporate use and will be critical for Google’s cloud computing strategy that will use Chrome to pitch and advertise Google’s cloud services. System administrators are now able to block very detailed content types, such as plug-ins, images, styles, fonts and inline scripts.
There are few application areas at this time that move as quickly as browsers. After a number of substantial improvements especially in Chrome 6/7 and 8, it almost appeared that the Chrome team took a breather with version 9 and 10 and slowed the development speed. However, the opposite is the case, as Chrome’s nightly builds are advancing quickly.
If you are running one of the recent Chromium 12 nightly builds, you are already used to the new touch tabs that let you select you multiple homepages with app icons, similar how you would organize a sfumartphone app screen. A “Recently Closed” option was added a few days ago that is now fully functional and opens a pop-up window with a listing of the pages that were closed. The individual screens are now labeled. The underlying Webkit now supports Windows 7 gestures. There is also note of new fav icons for the touch interface that will be 32 x 32 pixels in size, up from the standard 16 x 16 pixel size. Another welcome upgrade is the fact that Webkit can now support Chrome’s Skia backend, which will be used to enable PDF rendering in Chrome’s print preview.
The primary tabs are also seeing some changes. Tab scrolling is being introduced in horizontal and side tabs and the tab labeling now fades on Chrome for Windows as it does on the Mac version. Multi-tab-Select is also moving forward (by using SHIFT or CTRL). Not yet visible is a new full screen button that forced the Chrome team to move the profile button on the right top a bit to the left. Expect more focus on multi-profiles in Chrome, which should be supported by default in Chrome soon (you need to run the Google Pack to use more than profile at any given time today.)
There are plenty of relatively quiet, but ongoing performance upgrades. We discussed yesterday the integration of SPDY, but there are also smaller efforts such as the enhancement of simple drawing capabilities as well as more significant upgrades, such as the accelerated WebM encoder Bali, which was released about a month ago. Depending on the platform, Bali is about 30 – 40% faster than the preceding WerbM encoder, according to Google. We should note that Google almost exclusively shows ARM hardware to highlight the performance of Bali, which lets us still believe that now only will Chrome OS get a touch interface, but Google will also bringing a version of the Chrome browser to Android in the foreseeable time.
Also, I should mention some changes to the content security policy that addresses Chrome’s needs to be much more attractive for corporate use and will be critical for Google’s cloud computing strategy that will use Chrome to pitch and advertise Google’s cloud services. System administrators are now able to block very detailed content types, such as plug-ins, images, styles, fonts and inline scripts.
By Wolfgang Gruener in Products on April 12
Firefox 5 And 6 On Track: First Aurora Release Posted
Mozilla has taken the first major step in its new browser release schedule and transitioned Firefox 5 from its initial mozilla-central to the new aurora channel where the browser will be brought up to beta status.
The first Aurora release is still labeled as version 4.2a1pre and is not likely to change its version number to version 5.0 until it will go into beta on May 17. Mozilla said that it will also create the first Firefox 6.0 build today for mozilla-central, but has not done so yet. The Aurora builds for Linux, Mac and Windows were posted between 4 and 6 am PST this morning.
There aren’t any visible changes compared to Firefox 4.0 yet and we do not anticipate to see any of the upcoming GUI changes until mid May or shortly before the beta release arrives. It appears that Mozilla is pretty busy with this new release schedule so we expect that some previously mentioned GUI upgrades will be moved to Firefox 6 and 7.
However, Mozilla has to make sure that it regularly upgrades not just the version number, but also Firefox’ features, given Chrome’s crazy development pace. Firefox 5 is set for a June 21 release.
The first Aurora release is still labeled as version 4.2a1pre and is not likely to change its version number to version 5.0 until it will go into beta on May 17. Mozilla said that it will also create the first Firefox 6.0 build today for mozilla-central, but has not done so yet. The Aurora builds for Linux, Mac and Windows were posted between 4 and 6 am PST this morning.
There aren’t any visible changes compared to Firefox 4.0 yet and we do not anticipate to see any of the upcoming GUI changes until mid May or shortly before the beta release arrives. It appears that Mozilla is pretty busy with this new release schedule so we expect that some previously mentioned GUI upgrades will be moved to Firefox 6 and 7.
However, Mozilla has to make sure that it regularly upgrades not just the version number, but also Firefox’ features, given Chrome’s crazy development pace. Firefox 5 is set for a June 21 release.
Microsoft Releases First IE10 Preview
Microsoft today released the first preview of IE10, indicating a much faster browser development pace as well. Future platform previews will be updated in a cycles of 8 – 12 weeks.
Microsoft browser release cycle was 2 years with IE8 and IE9, now it appears that the cycle has been cut to at least 1 year, as the first developer preview of IE10 has been released earlier today. Microsoft said that it has been developing IE10 for about three weeks and will be supporting native HTML5 as well as several new CSS3 features such as color gradients and multi-column layouts – as well as ES5 Strict Mode.
We did not notice JavaScript performance improvements, but Microsoft has posted several new demonstrations at ietestdrive.com how to take advantage of the hardware acceleration features of the browser. We will be posting a review of the new browser platform as soon as we have a better idea how this new browser is evolving.
You can download IE10 PP1 at ietestdrive.com.
Microsoft browser release cycle was 2 years with IE8 and IE9, now it appears that the cycle has been cut to at least 1 year, as the first developer preview of IE10 has been released earlier today. Microsoft said that it has been developing IE10 for about three weeks and will be supporting native HTML5 as well as several new CSS3 features such as color gradients and multi-column layouts – as well as ES5 Strict Mode.
We did not notice JavaScript performance improvements, but Microsoft has posted several new demonstrations at ietestdrive.com how to take advantage of the hardware acceleration features of the browser. We will be posting a review of the new browser platform as soon as we have a better idea how this new browser is evolving.
You can download IE10 PP1 at ietestdrive.com.
By Kurt Bakke in Products on April 12
Friday, April 1, 2011
Nokia Vs. Apple Patent Battle: It’s All Or Nothing
Nokia has taken off the gloves and now accuses that all Apple products violate Nokia products in one way or the other. It’s surely attention getting move, but will it help Nokia to survive?
Nokia said that it has filed a second patent complaint with the ITC, following the first case in which the ITC determined that Apple did not infringe on Nokia’s patents. With this new filing, Nokia now claims that Apple illegally takes advantage of 46 Nokia patents and has cases pending in The U.S., Germany, U.K., and in the Netherlands.
According to Nokia, Apple infringes patents ”in virtually all of its mobile phones, portable music players, tablets and computers.” Those patents relate to “the areas of multi-tasking operating systems, data synchronization, positioning, call quality and the use of Bluetooth accessories.”
“Nokia is a leading innovator in technologies needed to build great mobile products and Apple must stop building its products using Nokia’s proprietary innovation,” said Paul Melin, Vice President, Intellectual Property at Nokia. Nokia said that it has invested almost $61 billion in research and has about 10,000 patent families. While the company has every right to defend its innovations, there is not enough detail publicly available to determine whether Nokia has a case against Apple or not, or whether Nokia simply uses a stalling strategy against Apple.
This new lawsuit as well as Nokia’s decision to move to the Windows 7 platform could also suggest that other phone manufacturers are a potential target as well. However, such industry-wide lawsuits rarely work and tend to isolate the suing party from the industry and possibly the market as well. Rambus, for example, has experience in that.
Can a lawsuit save Nokia? Probably not, as – even if Nokia has an opportunity to win – it can dragged out by Apple long enough to potentially bring Nokia down to its knees and awarded damages could be used to pay out Nokia investors. Given the current state of the phone industry and Nokia’s “burning platform”, one could also suggest that those $61 billion were not invested in the right areas of research. Stephen Elop’s letter to Nokia’s employees indicates that the company’s situation is very much based on its own inability to innovate and recognize shifting consumer interests. Only new devices that are more than just copies of Apple’s iPhone and iPad will give Nokia a future.
However, that isn’t just Nokia’s problem. That is a problem the entire phone and PC industry has.
Nokia said that it has filed a second patent complaint with the ITC, following the first case in which the ITC determined that Apple did not infringe on Nokia’s patents. With this new filing, Nokia now claims that Apple illegally takes advantage of 46 Nokia patents and has cases pending in The U.S., Germany, U.K., and in the Netherlands.
According to Nokia, Apple infringes patents ”in virtually all of its mobile phones, portable music players, tablets and computers.” Those patents relate to “the areas of multi-tasking operating systems, data synchronization, positioning, call quality and the use of Bluetooth accessories.”
“Nokia is a leading innovator in technologies needed to build great mobile products and Apple must stop building its products using Nokia’s proprietary innovation,” said Paul Melin, Vice President, Intellectual Property at Nokia. Nokia said that it has invested almost $61 billion in research and has about 10,000 patent families. While the company has every right to defend its innovations, there is not enough detail publicly available to determine whether Nokia has a case against Apple or not, or whether Nokia simply uses a stalling strategy against Apple.
This new lawsuit as well as Nokia’s decision to move to the Windows 7 platform could also suggest that other phone manufacturers are a potential target as well. However, such industry-wide lawsuits rarely work and tend to isolate the suing party from the industry and possibly the market as well. Rambus, for example, has experience in that.
Can a lawsuit save Nokia? Probably not, as – even if Nokia has an opportunity to win – it can dragged out by Apple long enough to potentially bring Nokia down to its knees and awarded damages could be used to pay out Nokia investors. Given the current state of the phone industry and Nokia’s “burning platform”, one could also suggest that those $61 billion were not invested in the right areas of research. Stephen Elop’s letter to Nokia’s employees indicates that the company’s situation is very much based on its own inability to innovate and recognize shifting consumer interests. Only new devices that are more than just copies of Apple’s iPhone and iPad will give Nokia a future.
However, that isn’t just Nokia’s problem. That is a problem the entire phone and PC industry has.
Kurt Bakke in Business on March 29
NASA Obtains First Orbital Image Of Mercury
The Messenger spacecraft sent the first orbital image of Mercury in stunning resolution.
The image (full resolution here), depicting the Debussy crater (light rays) as well as the Matabei crater (dark rays, to the west of Debussy), shows the region near the south pole of the planet – an area that has not been shown on any previous image yet. The picture was taken on March 29 at 5:20 am EDT, as part of a series that consists of a total of 363 images that are still being transferred. Over the next three days, NASA expects to receive a total of 1186 images and eventually cover the entire Mercury surface during Messenger’s 1-year orbital mission.
Messenger was launched six years ago with the goal to orbit Mercury and investigate the surface, magnetic field and composition of the solar system’s innermost planet. It follows the Mariner 10 craft, which flew by the planet in 1974 and 1975 and collected data and imagery of only about 45% of the planet’s surface. Messenger was launched in August 2004 and has flown 15 times around the sun, twice past Venus (2006 and 2007) and three times past Mercury (January 2008, October 2008 and September 2009). During the fly-bys, NASA fine-tuned Messenger’s track and speed and added more image data, which already increased the existing coverage of Mercury’s surface area to 75%.
NASA has activated the seven experiments onboard on March 24. The science phase is scheduled to begin on April 4. What makes Messenger special is that it can run its experiments almost at room temperature levels, despite the extreme temperature levels emitted by the planet’s surface. Messenger uses a heat-radiation system and will pass only briefly over Mercury’s hottest regions to limit the exposure to the intense heat. NASA estimates that the planet’s surface reaches surface temperatures of about 840 degrees F, while the floors of the deep craters at the poles never see direct sunlight and are below -276 degrees F.
On March 18, Messenger entered Mercury’s orbit and has been prepared for its critical mission since then. It is orbiting Mercury once every 12 hours at an altitude as los was 124 miles. When Messenger entered Mercury’s orbit, the craft was only about 28.7 million miles from the sun and 96.7 million miles from Earth. The total distance traveled by the spacecraft is more than 4.7 billion miles.
Messenger's First Mercury Picture
Messenger was launched six years ago with the goal to orbit Mercury and investigate the surface, magnetic field and composition of the solar system’s innermost planet. It follows the Mariner 10 craft, which flew by the planet in 1974 and 1975 and collected data and imagery of only about 45% of the planet’s surface. Messenger was launched in August 2004 and has flown 15 times around the sun, twice past Venus (2006 and 2007) and three times past Mercury (January 2008, October 2008 and September 2009). During the fly-bys, NASA fine-tuned Messenger’s track and speed and added more image data, which already increased the existing coverage of Mercury’s surface area to 75%.
NASA has activated the seven experiments onboard on March 24. The science phase is scheduled to begin on April 4. What makes Messenger special is that it can run its experiments almost at room temperature levels, despite the extreme temperature levels emitted by the planet’s surface. Messenger uses a heat-radiation system and will pass only briefly over Mercury’s hottest regions to limit the exposure to the intense heat. NASA estimates that the planet’s surface reaches surface temperatures of about 840 degrees F, while the floors of the deep craters at the poles never see direct sunlight and are below -276 degrees F.
On March 18, Messenger entered Mercury’s orbit and has been prepared for its critical mission since then. It is orbiting Mercury once every 12 hours at an altitude as los was 124 miles. When Messenger entered Mercury’s orbit, the craft was only about 28.7 million miles from the sun and 96.7 million miles from Earth. The total distance traveled by the spacecraft is more than 4.7 billion miles.
Kurt Bakke in Business on March 30
Microsoft: IE9 Downloads? What Downloads?
Seriously. There is no reason to get excited about download numbers yet. Microsoft may have bragged about those 2.35 million IE9 downloads within 24 hours, but that was entirely unintentional. Microsoft did not really want you to download IE9. The IE9 update isn’t even active yet. So don’t get too excited over those gazillion Firefox and Chrome downloads, please.
You have to wonder sometimes. What is the purpose of launching a product when you aren’t ready for a launch? Is that a recipe for disaster and if you have learned in the past that such an approach is likely to fail, why would you do it again? For the reason of keeping a tradition?
All right. It was just a matter of time until Microsoft would reply to the headlines that stated a thousand times how David Mozilla crushed Goliath Microsoft in first day, second day, third day, etc. browser downloads. We had some speculations and bets here how Microsoft would be spinning the story in an attempt to make its own browser downloads look better against the 45.5 million Firefox 4 downloads (at the time of this writing). For the record, Microsoft has only said – so far – that 2.35 million IE9 packages were downloaded on the first day of its availability. There has been no update so far, but the daily market share numbers that have been posted for IE9 suggest that the total downloads are less than 10 million (since March 14).
Microsoft said that it only counts completed downloads, while it suggests that others may also count every started and not completed download. We would, however go a step further and suggest to only count those browsers that are downloaded and actually used. If that is the case, then we know that only about 25% all those 40 million downloaded IE9s (36 million betas and RCs, plus those 2.35 million + X final IE9s – Microsoft said that 90% of IE9 final downloads came from non-beta and non-RC users) are in use (if we compare the market share numbers of IE9 and Firefox 4, as provided by StatCounter.)
Lowering Expectations
So it only makes sense that Microsoft now says that the update process hasn’t started yet. In fact, the IE9 release to the web (RTW) was just activated on Windows Update yesterday – or two weeks after the initial release. And that update only works for IE9 Beta and RC users. IE8 users can’t automatically update the browser yet. There has been no information (“sometime next month”) when that update will be turned on. Seriously, Microsoft? Should that browser have been launched later? A lot later and when everything is ready? I mean – everything? That strategy reminds me a bit of the graphics card paper launches of the mid-2000s when Nvidia and ATI announced out graphics cards to the press no one could actually buy, but simply admire on a spec sheet. Admitted, you can download IE9 (as long as you have Windows 7 or Vista SP2), yourself, but the lack of the update process is a serious miss.
You can almost always spin a story in a different direction and Microsoft finds lots of others to blame, just not itself. It’s the web developers who are to blame this time. They aren’t ready to fully support IE9. In fact, Microsoft asks us to ignore IE9 share and wait a few months until there is going to me a more reasonable view of IE9 downloads. However, there is an even more creative way to explore IE9 usage share: Addressable user base.
We are told that we should really triple IE9′s share, because it is an unfair comparison to Firefox and Chrome as those browsers support all Windows operating systems and IE9 does not. Huh? So we are blaming Mozilla and Google for a screw-up of Microsoft? Isn’t it Microsoft’s problem that it decided not to support Windows XP – and more than half of the OS market today? Microsoft may be focusing on Windows 7, but that won’t help the company in the fight for market shares. Those users Microsoft loses today, may be tough to win back. Essentially, Microsoft leaves the entire Windows XP market open to be attacked by Mozilla and Google. Tripling IE9 market share on paper may help Microsoft’s marketing, but it just won’t work in overall browser statistics.
The browser game has changed dramatically and browser market share development strongly depends on update cycles these days. Google updates Chrome every 6 weeks, Mozilla will roll out a final version every 16 weeks and previews of Firefox 5 are already available. Microsoft needs more than a month to just activate its update servers and is still on a 2-year development cycle for IE. Besides bleeding plain browser market share, Microsoft will soon have to surrender technology trends to a much stronger competition: For example, With Firefox 4 being available, a growing Chrome and a loyal Opera user base, Google’s WebM video format will soon be supported by nearly half of all browser users (according to StatCounter). Microsoft’s bet on H.264 in IE9 is unlikely to pay off.
We aren’t sure whether the most recent blog post from Microsoft is the actual inside opinion on IE9 downloads inside Microsoft or whether it is just an attempt to limit the IE9 launch problems. If it is the real problem, Microsoft needs to get its ship in order and adapt to a changing browser environment quickly. Otherwise, Chrome and Firefox will simply roll over Microsoft and turn IE9 into an irrelevant browser by the time IE10 is released.
IE9 is, in our view, a great browser, even if it has its weaknesses in its target area. But the marketing behind it is a mess.
You have to wonder sometimes. What is the purpose of launching a product when you aren’t ready for a launch? Is that a recipe for disaster and if you have learned in the past that such an approach is likely to fail, why would you do it again? For the reason of keeping a tradition?
All right. It was just a matter of time until Microsoft would reply to the headlines that stated a thousand times how David Mozilla crushed Goliath Microsoft in first day, second day, third day, etc. browser downloads. We had some speculations and bets here how Microsoft would be spinning the story in an attempt to make its own browser downloads look better against the 45.5 million Firefox 4 downloads (at the time of this writing). For the record, Microsoft has only said – so far – that 2.35 million IE9 packages were downloaded on the first day of its availability. There has been no update so far, but the daily market share numbers that have been posted for IE9 suggest that the total downloads are less than 10 million (since March 14).
Microsoft said that it only counts completed downloads, while it suggests that others may also count every started and not completed download. We would, however go a step further and suggest to only count those browsers that are downloaded and actually used. If that is the case, then we know that only about 25% all those 40 million downloaded IE9s (36 million betas and RCs, plus those 2.35 million + X final IE9s – Microsoft said that 90% of IE9 final downloads came from non-beta and non-RC users) are in use (if we compare the market share numbers of IE9 and Firefox 4, as provided by StatCounter.)
Lowering Expectations
So it only makes sense that Microsoft now says that the update process hasn’t started yet. In fact, the IE9 release to the web (RTW) was just activated on Windows Update yesterday – or two weeks after the initial release. And that update only works for IE9 Beta and RC users. IE8 users can’t automatically update the browser yet. There has been no information (“sometime next month”) when that update will be turned on. Seriously, Microsoft? Should that browser have been launched later? A lot later and when everything is ready? I mean – everything? That strategy reminds me a bit of the graphics card paper launches of the mid-2000s when Nvidia and ATI announced out graphics cards to the press no one could actually buy, but simply admire on a spec sheet. Admitted, you can download IE9 (as long as you have Windows 7 or Vista SP2), yourself, but the lack of the update process is a serious miss.
You can almost always spin a story in a different direction and Microsoft finds lots of others to blame, just not itself. It’s the web developers who are to blame this time. They aren’t ready to fully support IE9. In fact, Microsoft asks us to ignore IE9 share and wait a few months until there is going to me a more reasonable view of IE9 downloads. However, there is an even more creative way to explore IE9 usage share: Addressable user base.
We are told that we should really triple IE9′s share, because it is an unfair comparison to Firefox and Chrome as those browsers support all Windows operating systems and IE9 does not. Huh? So we are blaming Mozilla and Google for a screw-up of Microsoft? Isn’t it Microsoft’s problem that it decided not to support Windows XP – and more than half of the OS market today? Microsoft may be focusing on Windows 7, but that won’t help the company in the fight for market shares. Those users Microsoft loses today, may be tough to win back. Essentially, Microsoft leaves the entire Windows XP market open to be attacked by Mozilla and Google. Tripling IE9 market share on paper may help Microsoft’s marketing, but it just won’t work in overall browser statistics.
The browser game has changed dramatically and browser market share development strongly depends on update cycles these days. Google updates Chrome every 6 weeks, Mozilla will roll out a final version every 16 weeks and previews of Firefox 5 are already available. Microsoft needs more than a month to just activate its update servers and is still on a 2-year development cycle for IE. Besides bleeding plain browser market share, Microsoft will soon have to surrender technology trends to a much stronger competition: For example, With Firefox 4 being available, a growing Chrome and a loyal Opera user base, Google’s WebM video format will soon be supported by nearly half of all browser users (according to StatCounter). Microsoft’s bet on H.264 in IE9 is unlikely to pay off.
We aren’t sure whether the most recent blog post from Microsoft is the actual inside opinion on IE9 downloads inside Microsoft or whether it is just an attempt to limit the IE9 launch problems. If it is the real problem, Microsoft needs to get its ship in order and adapt to a changing browser environment quickly. Otherwise, Chrome and Firefox will simply roll over Microsoft and turn IE9 into an irrelevant browser by the time IE10 is released.
IE9 is, in our view, a great browser, even if it has its weaknesses in its target area. But the marketing behind it is a mess.
Subscribe to:
Comments (Atom)