Comments on: Inside Microsoft's new mobile browser
CNET News' Ina Fried gets a peek at the version of Internet Explorer 6 that the company will bring to Windows Mobile later this year.
CNET News' Ina Fried gets a peek at the version of Internet Explorer 6 that the company will bring to Windows Mobile later this year.
Web sites launch all the time, but they also shut their doors. We highlight 15 that bit the dust this year.
Let the debate begin: Was the iPhone more important than iTunes? Was anything bigger than Google finding a great business model? CNET offers its list of the 10 most important stories of the '00s.
During her years at CNET News, Ina Fried has changed beats several times, changed genders once, and covered both of the Pirates of Silicon Valley. These days, most of her attention is focused on Microsoft.
Beyond Binary is a look at how technology is changing our lives and the people behind all that life-changing stuff, with an extra emphasis on that which emanates from Redmond, Wash.
Add this feed to your online news reader
What is the problem over at Microsoft? Are the Windows Mobile programmers not allowed to see the source code for Explorer 7? Is Explorer 7 so bloated and clunky there's no way to squeeze it onto a mobile device? Is everyone on the development team for Mobile using drugs?
Now that I think about any of you Windows mobile developers with a hankering can go get webkit (www.webkit.org) and do it yourselves.
In the meantime, my iPhone and me will be surfing away...
Windows Mobile is designed to run even on very constrained devices (not just phones but in-dash nav systems, portable media players, etc.) having as little as 32MB (!) of total RAM. So the memory budget for Mobile IE + Flash + Silverlight is probably 10MB. The fact that they can shove in a full IE rendering engine is a great accomplishment.
Safari on the iPhone can access 128MB or RAM yet still struggles. Just Google "iphone safari reset" to see how crappy Safari really is on a memory-constrained system.
Also remember WM 6.1 is just a minor upgrade to WM 6 (release last year) and must run on the same generation hardware. The next version of Windows Mobile (WM 7) will require more capable hardware and maybe we can see the IE7 engine running on it.
Safari would be awesome on a Windows Mobile device, as would a slimmed down Firefox.
I too would love to see a good FF port to WM though.
I am looking forward to seeing what the IE upgrade will look like, if it's going to enable Flash support. That's the one thing I really miss when I browse on my cell phone, which I do on a regular basis.
Internet Explorer Mobile is a completely separate build from the desktop IE versions, not a port. The only thing they share is the name.
What IEM really needs is good zoom support ala iPhone's Safari or even Opera Mini. Something, anything that allows quicker and easier navigation. The current version is just too clunky - I only utilize it for pages that Opera Mini has trouble loading. I would really love to be able to just use one full-feature browser, instead of parts of two.
Unfortunately, as you can see with everyone else on the forum, many people do not understand. To make things simpler or dumber, I strongly suggest that Microsoft should keep the version consistent between mobile and desktop. Done properly with a modularized approach, they could simply take the desktop version, trim out the module they don't need and have it on the mobile.
For the comment
"Windows Mobile is designed to run even on very constrained devices"
Then maybe they should use windows mobile instead of Vista.
When I look at the web I want to see the original version, not the crappy version. Safari could be a memory hog, But I prefer the full version to a half baked one.
Come on Ina... I know you can do better.
It says they are using the IE6 "engine". This doesn't mean it won't have certain IE7 or 8 features. The web has been constructed to support IE6. More pages will look right in IE6 than in IE7, trust me.
This isn't a bad move at all. Hopefully it's a free release/upgrade and/or WinMo 6.2 option.
At least, that was their intent earlier was to bring it to the 6.1 series. Maybe 6.0.
- by donovan1983 September 12, 2008 8:22 AM PDT
- I sincerely hope they updated the absolutely dismal standards support in IE6 before porting it. I refused to design sites to work in it since doing so meant using convoluted and non-standard code that didn't always render properly in standards compliant browsers. I do understand why they used IE6 instead of IE7 as the base since IE6 was released in an era when machines with 64MB of RAM were very common still and 128MB had just become the new standard. I am betting that you will need a device with at least 128MB of RAM to be able to run this, though, so even many current Windows Mobile 6 or 6.1 devices won't be able to use this.
- Like this Reply to this comment
-
Showing 1 of 2 pages (34 Comments)