A key component of this development has been Nokia’s cooperation with Apple, as the Series 60 browser will use the same open source components, WebCore and JavaScriptCore, that Apple uses in its popular Safari Internet browser. Based on KHTML and KJS from KDE’s “Konqueror” open source project, this software has enabled Safari to achieve industry-leading features and performance. Nokia intends to continue its collaboration with Apple and actively participate in the open source community to further develop and enhance these components, contributing Nokia’s expertise in mobility.
Nokia develops a new browser for Series 60 using KHTML
About The Author
Eugenia Loli
Ex-programmer, ex-editor in chief at OSNews.com, now a visual artist/filmmaker.
Follow me on Twitter @EugeniaLoli
Apple should create a version for Linux and Windows! It would allow their browser to gain market share beyond the Mac platform, just like iTunes. The more competition in the marketplace the better it is for us consumers. Good Choice Nokia!!!
P.S. I guess Internet Explorer wont get ported to Symbian
Someone has post this Screenshot on Slashdot and I would like to know more about it if possible. Looks quite promising and from further comments it seems that this is based upon NOKIA’s recently released version of GTK+ WebCore.
http://img130.echo.cx/my.php?image=screenshotgenesihome2hl.png
The version found on the Homepage seems to be an older version and I have it running here. Looks quite promising and it’s damn fast.
That’s Atlantis.
http://www.akcaagac.com/index_atlantis.html
didn’t apple completely rewrite the JS portion of webcore in order to achieve breakneck speed enhancements in javascript for 2.0 in Tiger?
Doesn’t that mean that they aren’t even really using KJS anymore?
im happy than nokia do it, because porting app to symbian is a pain in the ***.
Nope, the speed increase in javascript comes directly from KDE, from changes the KDE developers made to KJS after Apple forked the code. If I remember correctly those changes vent into KDE 3.3, I’d guess Apples developers have some problems keeping up with the KDE developers:-)
Agreed. Reduced C++ support I hear…
Somewhat misleading title, since the text says they’re using WebCore, not KHTML. The two may be related, but the confusion between them is what sparked all the recent arguments.
Opera’s business has been trying to sell web browsers to embedded devices. Now their whole business is basically gone.
That is patently untrue, Morty. Apple has done a bunch of performance improvements across the board, especially in JS. Those changes did not come from KDE.
I would say it increases the chances for Opera. I doubt Sony or Motorola will base their technology on something controlled by Nokia.
Apple has done some performance improvement work, but several major ones comes from the khtml developers. Looks like people forget that even if the Safari team contains several coders working full time, most of them do NOT work on WebCore. The rest of Safari, which Apple had to write from scratch, are also a big piece of code. Basic resource management btw.
Just a minor comment Eugenia: When just quoting press releases without adding your personal comments to the news item, I think you should e.g. add quotation marks or make it all italics. That way it’d be easier to distinguish what is your personal opinion and what is a rehash of press release propaganda. Not that it wasn’t obvious in this case; it’s just something I’ve noticed from time to time…
>>>I would say it increases the chances for Opera. I doubt Sony or Motorola will base their technology on something controlled by Nokia.
If Nokia can use WebCore/KHTML, then Sony or Motorola or other embedded device makers can also use WebCore/KHTML. Nokia doesn’t control WebCore/KHTML.
I’d like to support Qwilk’s opinion. Eugenia, by using quotes or italics to delimit your words and other people’s words, you will make things easier and more useful for readers, and will also avoid founded accusations of plagiarism. Also, you will want to be careful with quoting significant passages from other sites, as that may infringe copyright regardless of any clear delimitation. Doing all that undoubtedly requires more work on your part, but who says life is simple?
Cheers,
Vesselin
KHTML is lighter and stabler than Gecko. Why is GNOME still using Mozilla?
Is it connected with GNOME’s hatred to KDE?
Probably because KHTML has a lower compatibility rating. Gecko (Mozilla) may be slower and have uglier code, but it just works! KHTML developers are playing catch-up with WebCore as we speak, so sometime in the future KHTML may become a viable choice again.