@OMG! Toesies on the Nosies!: Agreed-iWant is one of my personal favorites-regularly updated, with categories added as necessary & a pretty decent UI. Oh, and free, which is always awesome.
@Kraken: Doesn't work where I am, only seems to work in big American cities where the Wi-Fi has all been mapped out. So if you're not in one of them, doesn't work :(
@VaatiKaiba: well thats not totally true. it deff doesn't work every where tho. i was in PA at a friends place a couple weekends ago and it didn't work. but where i live "largest town in the county, smallest population* if i connect to my wifi i can get a location. so i think it depends on a lot more than just being in a large city.
Edit: woah i got a star? :) when did that happen? yayyy stars. (i hope its not just a bug)
you have it bass akward... safari is based on webkit, not the other way around. how the hell can you be writing this story and not have any idea of what the hell your are talking about.
webkit come from the rendering engine from the konqueror browser that was used as a part of KDE (an open source UNIX windowing system).. apple used the open source code and has been adding to the project ever since..
webkit is not even a browser it's a rendering engine... Google Chrome and Palms new bowser also used webkit actually lots of new browsers use it and are adding to the code base... it's not an apple or a safari thing at all..
@doctorSpoc: This has been typical of late. Its what happens when you have a blog being run by people who are tech addicts, but not necessarily tech savvy. Unfortunately more often than not it means the wrong information is put out there, as unlike reporters, bloggers have a tendency to write now, research after the fact, though a lot of reporters as of late like to do that too.
@doctorSpoc: I don't see the issue. They said "but they're all based on Safari's WebKit." I guess technically it's not only Safari's webkit rendering engine, but do you really expect them to site the history all the way back.
"these browsers are based on webkit, which is safari's rendering engine, which apple took from konqueror, which is kde's browser, which is a graphical desktop environment for many linux distributions, linux of course being the brainchild of Linus Trovalds, grandson of poet Ole Torvalds..."
Seriously, if people don't know that webkit is Safari's rendering engine then they're not paying much attention anyhow. Lighten up.
@apt94jesse: Except they make it sound like its Apples which it isnt. Google, Palm, even some forks of Mozilla are all including aspects of Webkit into their browsers as of late.
Saying it has to be "based" on Safari is just plain wrong, as Chrome is certainly not based on Safari.
@Jim Topoleski: Dudes, the main issue is that you can only implement browsing functions in your app if it calls on Safari's engine. Yes, that's WebKit. But it's Apple's fork of WebKit, not any other--you couldn't use Chrome's, for example.
The issue is that the rendering engine does not vary from the one in Safari's, so these aren't really new browsers.
It doesn't look like you could bring in your own branch of webkit here, or even interfere with any of the rendering functions at all. As Long As They're Based On Safari Mobile's Branch of WebKit would be a totally accurate (goofily long) title.
I like it. The guy knew that his patent would never be granted by anyone who understood what he was trying to patent, so he threw in the word "matrix" a couple of times to make it sound like he wasn't trying to patent web browsing.
Hey guys, sorry, the key to the charts could use a little explanation. Post updated, and here it is:
CHART KEY: Number value is time for complete page load in seconds; page rendering is rated from "Fail" to "Excellent" for each; and the color (red, yellow, green) indicates overall performance taking into account both speed and rendering accuracy: Green = good overall, Red = fail overall.
Sorry, but the Mobile Safari does not compare to Opera when on a proper phone. Try the HTC Touch Pro when using Opera and you will be very happy.
Yes this is all user opinions in the end, but after leaving both the EDGE iPhone and 3G iPhone for the HTC Touch Pro (on AT&T), Safari just feels lacking when compared to Opera on the right phone. Plus you should take into account the amazing amount of times Safari crashes while the stability of other web browsers is a step above (namely Opera).
07/16/09
Second, there's already a bunch of apps for that. I'm not going to go through Google; I'll go through iWant or Vicinity or Zagat.
07/16/09
07/16/09
07/16/09
07/16/09
07/16/09
07/16/09
Edit: woah i got a star? :) when did that happen? yayyy stars. (i hope its not just a bug)
01/14/09
you have it bass akward... safari is based on webkit, not the other way around. how the hell can you be writing this story and not have any idea of what the hell your are talking about.
webkit come from the rendering engine from the konqueror browser that was used as a part of KDE (an open source UNIX windowing system).. apple used the open source code and has been adding to the project ever since..
webkit is not even a browser it's a rendering engine... Google Chrome and Palms new bowser also used webkit actually lots of new browsers use it and are adding to the code base... it's not an apple or a safari thing at all..
idiots!
01/14/09
01/14/09
"these browsers are based on webkit, which is safari's rendering engine, which apple took from konqueror, which is kde's browser, which is a graphical desktop environment for many linux distributions, linux of course being the brainchild of Linus Trovalds, grandson of poet Ole Torvalds..."
Seriously, if people don't know that webkit is Safari's rendering engine then they're not paying much attention anyhow. Lighten up.
01/14/09
Saying it has to be "based" on Safari is just plain wrong, as Chrome is certainly not based on Safari.
Face it, it was poor reporting.
01/14/09
01/14/09
The issue is that the rendering engine does not vary from the one in Safari's, so these aren't really new browsers.
01/14/09
01/14/09
no kidding! While the crashes have been less frequent with 2.2, they still happen and it is damn annoying.
01/14/09
01/14/09
01/14/09
It doesn't look like you could bring in your own branch of webkit here, or even interfere with any of the rendering functions at all. As Long As They're Based On Safari Mobile's Branch of WebKit would be a totally accurate (goofily long) title.
01/14/09
01/14/09
11/25/08
11/25/08
I'll need to get a pic of him to submit with it..
11/25/08
11/19/08
You had a chance to be honest, and at least tie the Android and the iPhone. Instead, it's the same ol', um, 'Apple' polishing.
Enjoy the kickback check, guys.
11/19/08
CHART KEY: Number value is time for complete page load in seconds; page rendering is rated from "Fail" to "Excellent" for each; and the color (red, yellow, green) indicates overall performance taking into account both speed and rendering accuracy: Green = good overall, Red = fail overall.
11/19/08
Instinct takes 2+ min to load WSJ = Excellent, but Dare fails at 38 seconds (both red?)
Bold gets an excellent at 2.5 mins on Wiki (red), instinct does 52 sec (green)?
11/19/08
11/19/08
11/19/08
Yes this is all user opinions in the end, but after leaving both the EDGE iPhone and 3G iPhone for the HTC Touch Pro (on AT&T), Safari just feels lacking when compared to Opera on the right phone. Plus you should take into account the amazing amount of times Safari crashes while the stability of other web browsers is a step above (namely Opera).
11/19/08