Got a tip for us?
Let us know
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
Samsung L870 Uses 'Safari'
- Thread starter edesignuk
- Start date
- Sort by reaction score
Somehow, I don't think Apple would want to stop them. Wouldn't that be an awesome PR victory
It would also be a web-coder victory. No more IE headaches! (well, in a few years anyway).
"Webkit" != "Safari"
Apple's lawyers will be all over this trademark violation, can't wait!!! It is unfortunate some Japanese press release translator will feel the pain over this.
Apple's lawyers will be all over this trademark violation, can't wait!!! It is unfortunate some Japanese press release translator will feel the pain over this.
hmmm...
well, the issue I see with this is that any critism for the phone's web browser will obviously be directed at Apple.
I don't think the software alone makes the mobile web browsing experience so popular on the iPhone (although it does play a key role.) I think the hardware (the high resolution touch screen) plays a much larger role.
...
But if Apple wants to start porting Safari, could they give it to the Wii? The Wii's web browsing experience is total bull. It's missing tabs. And plugins to play QuickTime among other things. Inquisitor wouldn't hurt a bit either. (Especially considering how slow it is trying to type on the onscreen keyboard.)
well, the issue I see with this is that any critism for the phone's web browser will obviously be directed at Apple.
I don't think the software alone makes the mobile web browsing experience so popular on the iPhone (although it does play a key role.) I think the hardware (the high resolution touch screen) plays a much larger role.
...
But if Apple wants to start porting Safari, could they give it to the Wii? The Wii's web browsing experience is total bull. It's missing tabs. And plugins to play QuickTime among other things. Inquisitor wouldn't hurt a bit either. (Especially considering how slow it is trying to type on the onscreen keyboard.)
I suspect this whole thing is an oversight by whoever put the brochure together.
No, competition is healthy. The last thing we want is one single rendering engine. Gecko has so far proved inadequate for use on the mobile (where the only real players are Opera and Webkit). Why would Webkit team want all that cruft shoved into their nice, clean code-base?
I've never had much of an issue supporting both. There are some minor differences, but overall if you follow the best practice you should be fine targeting both.
True, especially with all the new HTML 5 support. Maybe one day Firefox will drop Gecko and move to Webkit and find a way of taking their plugin architecture with them! I feel it is unlikely though. And I wouldn't want it to happen either — competition is healthy.
No, competition is healthy. The last thing we want is one single rendering engine. Gecko has so far proved inadequate for use on the mobile (where the only real players are Opera and Webkit). Why would Webkit team want all that cruft shoved into their nice, clean code-base?
I've never had much of an issue supporting both. There are some minor differences, but overall if you follow the best practice you should be fine targeting both.
True, especially with all the new HTML 5 support. Maybe one day Firefox will drop Gecko and move to Webkit and find a way of taking their plugin architecture with them! I feel it is unlikely though. And I wouldn't want it to happen either — competition is healthy.
Since Apple are actively trying to push Safari - the recent iTunes on Windows thing springs to mind - it wouldn't surprise me if they are licensing Safari to third parties.
S60v3 uses a variety of browsers - the Nokia N95's native browser is OK but Opera mobile is better. It'd be great if Safari becomes an available download too.
As for a blow to Windows Mobile, well not really: S60 is a completely different OS.
S60v3 uses a variety of browsers - the Nokia N95's native browser is OK but Opera mobile is better. It'd be great if Safari becomes an available download too.
As for a blow to Windows Mobile, well not really: S60 is a completely different OS.
I'm pretty sure the iPhone and Windows version were doing that just fine with that.
I really think they're risking it by letting another phone company use it... unless Apple is being allowed to oversee some portion of the quality assurance... it seems very possible the other company will cut corners and screw up the hardware so that Safari won't run smoothly.
How is this a bad thing for windows mobile users as we got three different versions of opera(opera 8, 9 and mobile), skyfire, IE, Minimo beta, and deepfish. We got so much choices that equal and in some ways best Safari(after all we can use adobe flash on our devices). But, yeah competition is great for us consumers and I am looking forward for more advancements. I would not be surprised we see this hacked and working on Nokia and possibly even Sony Symbian based devices.
agreed. If Apple is helping port Safari around to different mobile devices, it just makes developing to safari that much more important, and then Ipod/phone devices will benefit. iPhone will not be put out as the key interface benefits will still be there, and the iPhone SDK will allow killer apps unique to the Apple mobile line.
And Anything to move closer to the W3C standards and away from IE7 is a good thing, and if smartphones are the way to do it, then let's all of us welcome our new cell phone overlords.
Haha is that suppose to be a joke because a lot of Korean products are copies of Japanese? I'm not trying to be racist here, it's just a lot of Korean products have been known to be illegally copies Japanese products, just Google it.
Since that should be obvious to even the worlds dumbest executive, I would assume that Samsung has Apple's permission to use the "Safari" name.
Updated Info
Um, not sure if anyone posted this info or informed longofest, on this.
BUT Webkit is NOT only founded by Nokia, nor created by them. Something I get tisick about because they always state this ... yet "they" (Nokia) contacted Apple to develop it with them.
http://webkit.org/
Cheers.
Um, not sure if anyone posted this info or informed longofest, on this.
BUT Webkit is NOT only founded by Nokia, nor created by them. Something I get tisick about because they always state this ... yet "they" (Nokia) contacted Apple to develop it with them.
http://webkit.org/
Cheers.
I've always agreed myself.
Samsung is the Korean Sony, and Hyundai is the Korean Honda.
Those Korean companies produce similar products and target the same market as their Japanese counterparts.
However, the products are typically of less quality standards and lower price point to the consumer.
Errr....
.... just like the Japanese did before them on the American automobile, JUST like the USofA did years ago against the British, just like every other culture in the history of man! China's 5000 years of history shows plenty of periods of native innovative countered by periods of importing technology and making it their own (aka, "infringing IP").
Sorry, by singling out Koreans you ARE being racist, plain and simple.
.... just like the Japanese did before them on the American automobile, JUST like the USofA did years ago against the British, just like every other culture in the history of man! China's 5000 years of history shows plenty of periods of native innovative countered by periods of importing technology and making it their own (aka, "infringing IP").
Sorry, by singling out Koreans you ARE being racist, plain and simple.
Sorry if I didn't write a 20 page report of the history of copyright. I was just saying that a lot of Korean products are copies of Japanese products, they do have original innovations too.
How about if I bring up Apple copying Xerox.
Spread the Webkit!
Agreed.
As a web developer I've seen Safari/Webkit behaving quite nicely along with Firefox/Gecko since Safari 3. I few months ago I was on a site build that had to "support" Safari 2.0.4, and therefore I had to work around some of its CSS bugs. As always, the real pain for all of us are IE6 and IE7. I will not detail their weaknesses since that is well covered.
(to everyone) Perhaps you disagree. Maybe you think IE8 sounds like a good promise. Have you tried the beta? I did. It has this neat auto-recover feature for your session. You know, like Firefox has had for awhile now? Except that it has no way (yet) of gracefully failing. Default behavior. I discovered this when I took IE8 for a test drive on a site I had in QA. IE8 loaded part of the page and then crashed. Auto-recover to the rescue! Quick, load that last page! Crash. Repeat. Between each crash were 2, yes TWO *modal* dialogs informing me about what had happened and most unhelpfully presented choices that led to same condition. Has anyone at Microsoft read Kafka?? Yes, yes, this is beta software. But betas of other browsers have rarely seemed this bad. I mean, I have to use Task Manager in tandem with IE8 on the first site I load. Smooth.
Agreed.
As a web developer I've seen Safari/Webkit behaving quite nicely along with Firefox/Gecko since Safari 3. I few months ago I was on a site build that had to "support" Safari 2.0.4, and therefore I had to work around some of its CSS bugs. As always, the real pain for all of us are IE6 and IE7. I will not detail their weaknesses since that is well covered.
Competition. Yes, Safari vs. Firefox. And those two vs. Opera and whatever other rendering engines / flagship apps we can get into the melee. Anything we can do to speed the process of taking this lumbering behemoth of Internet Explorer and laying it to rest. It is and has been obsolete and *obtusely* non-standard for what feels like eons.
(to everyone) Perhaps you disagree. Maybe you think IE8 sounds like a good promise. Have you tried the beta? I did. It has this neat auto-recover feature for your session. You know, like Firefox has had for awhile now? Except that it has no way (yet) of gracefully failing. Default behavior. I discovered this when I took IE8 for a test drive on a site I had in QA. IE8 loaded part of the page and then crashed. Auto-recover to the rescue! Quick, load that last page! Crash. Repeat. Between each crash were 2, yes TWO *modal* dialogs informing me about what had happened and most unhelpfully presented choices that led to same condition. Has anyone at Microsoft read Kafka?? Yes, yes, this is beta software. But betas of other browsers have rarely seemed this bad. I mean, I have to use Task Manager in tandem with IE8 on the first site I load. Smooth.
Agreed on the odd part
I didn't see this coming but am excited about it if it boosts usage for the browser
I still use FireFox the most but am 70/30 FireFox/Safari
I still get some crashes with Safari which annoy me a bit
There's no reason why Wii Opera can't do plugins now - its likely due to the limited storage space. Apple would have to approve any QuickTime plug in, probably.
"Originally Posted by SqueegyX
Mozilla and Apple need to get together."
Apple rejected Gecko because its too bloated. Webkit was far lighter.
Nokia also investigated Gecko, but finally decided upon Webkit and produced a S60 browser - which is what this device uses. The Nokia webkit browser actually, at this moment in time, has more functionality than the iPhone does.
I've had webkit on my phone for coming up to 2 years, and its pretty damned good - very good rendering.
