Safari Code Benefiting Open Source Community 66
saha writes "Thought this article about Apple's Safari contribution back to the open source community may interest some of the readers. KDE adds Safari feel to desktop Linux: The Konqueror Web browser, which shares its basic engine with Apple's Safari, has benefited from Apple's Safari work, KDE said. Konqueror now loads and renders more quickly and has better support for Web standards. One of Apple's major efforts with Safari has been to encourage users to report sites that don't work properly with the browser, in order to improve compatibility."
Re:on the other hand (Score:3, Informative)
Re:on the other hand (Score:2)
KDE 3.2 (Score:3, Funny)
I really hate corporations (Score:5, Interesting)
Odds are what you mean is that you do not like the actions of iirresponsible people.
Re:I really hate corporations (Score:2, Insightful)
They made tons of changes (Score:2, Interesting)
Now it's definitely a worthy adversary of Mozilla and IE.
Win version (Score:2)
Maybe I'm just not aware of it and it already exists, but a windows version of Konqueror would be nice for those who want a consistent feel across their multiple OSes (like with Mozilla, Open Office, etc).
Why is this newsworthy? (Score:3, Insightful)
Lets see Sun, IBM, RedHat, Novell, CodeWeavers, oh and Apple (isn't the underlying OS for MacOS X open source?) not even mentioning the INDIVIDUALS who contribute (who arguably get less out of the deal since there is no direct profit motive)
Oh wait, is this news because you would normally assume Apple to be parasitic and not give back to anyone?
Re:Why is this newsworthy? (Score:5, Interesting)
To my ( somewhat limited ) knowledge, most of the effort companies you've listed have put in show up only for administrators and developers, not desktop users. Arguably because that's where effort has been needed most ( maybe up until now ), but still...
OpenOffice is equally newsworthy, but maybe not exactly as easily usable and feature-complete, though I'd argue that's mainly due to it's larger feature set as compared to the KHTML engine. I think it'd be interesting to know how many resources Apple has thrown at KHTML compared to the resources Sun has thrown at OpenOffice, for example. If the manhours are comprable, shame on Sun. I personally feel that OpenOffice may be the single most important open source project right now. If I didn't spend all of my spare time surfing
Of course, I'd like to see Apple pick up and work on OpenOffice as an AppleWorks replacement ( they need one ) but there are so very, very many reasons I can't expect that to happen.
Re:Why is this newsworthy? (Score:5, Interesting)
Re:Why is this newsworthy? (Score:5, Insightful)
Re:Why is this newsworthy? (Score:2)
Since I don't have any direct experience with Ximian, and keep thinking of it as a separate company distinct from Novell, I'd failed to make that connection.
On the other hand, Ximian releases are often Slashdot stories, and thus just as "newsworthy" as this story, I guess... anyway, my point was just to counter that this is actually slightly newsworthy for several reasons; mainly, it's nice to see Apple living up to their promises.
I certainly didn't mean to downplay the great contributions of t
Re:Why is this newsworthy? (Score:5, Interesting)
Following the release of Safari, MS dropped support for IE on Mac, directly citing the existence of Safari as the reason.
Apple need Microsoft Office, so I can't see them daring to touch an actually competitive office suite.
Re:Why is this newsworthy? (Score:2)
As much as running programs via X11 sucks, I use OpenOffice instead of OfficeX. At first, MSOfficeX was just too expensive. Later on I had access to OfficeX, but I was much happier with OpenOffice.
Apple does not need OfficeX.
Re:Why is this newsworthy? (Score:3, Informative)
The key to this is compatibility with Office for Windows. As much as we hate to admit it, it is the standard by which all others is judged. Any suite that wants to replace Office, or at least become a major player in the office suite arena, has to be fully compatible with M$ Office.
Re:Why is this newsworthy? (Score:1, Interesting)
Re:Why is this newsworthy? (Score:1, Troll)
Re:Why is this newsworthy? (Score:2)
Re:Why is this newsworthy? (Score:2)
Considering that Konqueror is GPL'd [gnu.org] and KHTML is LGPL'd [wikipedia.org], it would be fruitless for Apple to even consider being parasitic. You're seeing the GPL family of licenses at work, where proprietary and open source companies mutually benefit one another. Everyone wins, specially the users.
= 9J =
Can Konqueror be embedded easily like Mozilla? (Score:1, Interesting)
Re:Can Konqueror be embedded easily like Mozilla? (Score:1, Informative)
Re:Can Konqueror be embedded easily like Mozilla? (Score:2)
Re:Can Konqueror be embedded easily like Mozilla? (Score:1)
yup... (Score:5, Interesting)
Of course it isn't entirely stable yet, I do get the occasional SEGFAULT, but I've seen that happen even with browsers that theoretically *are* stable.
Re:yup... (Score:5, Interesting)
key:
mozi
IE: supports the xsl but not the css
konq/opera: doesnt support the xsl.
Considering XSL is an old(5 or so years) spec needed for the web to develope further, especially in a way the OSS community would prefer, its pathetic that some browsers still just don't render it at all.
Re:yup... (Score:4, Insightful)
Re:yup... (Score:5, Insightful)
For now they've WON the browser wars.
They have 95% of the browsers and webpages are coded to whatever crap IE renders whenever necessary. No need to fix anything. No need to add anything new, no need to try to conform to any type of standard at all.
They have a long time before any other browser challenges them, so they might as well put it to good use writing proprietary lock-ins for people to stumble into and never be heard from again.
Re:yup... (Score:3, Insightful)
You do have to be a bit careful with repeating this sort of claim, because many of the statistics you'll read fall into the "87% of all statistics are just made up" category. It's very easy to interpret web-server logs and sales figures in radically different ways.
Thus, I recently installed the latest Opera on my Powerbook, as part of my collection of browsers for testing web pages. I checked with
Re:yup... (Score:2)
All XSL does is transform your XML into HTML/CSS (or another format). It's a meta-markup language. Look at the stylesheet at your link. This isn't some new standard, it's plain old HTML and CSS in disguise.
Re:yup... (Score:2)
It would be so much easier to parse a webpage like that and actually get usable data, than fudging through lots of crappy html parsing thats easy to paste. It also allows you to provide much more data than you actually use, and transform it later. Look at the file list page, and the screenshot/pictures galleries. Same xml, lots more info than I use. This dat
Re:yup... (Score:5, Interesting)
KHTML doesn't implement XSL because practically nobody uses XSL. Personally, I doubt it will ever catch on; it's just too complex and the syntax is way too ugly. I haven't seen any compelling reason to use it. If it does catch on, though, you can bet the next release of Konqueror will support it. KHTML developers just don't see the need to waste their time implementing complex standards that nobody wants to use in real webpages. Besides, it's not like KHTML supporting XSL will catapult it into wide acceptance or anything, because KHTML is in a different position than Gecko or IE.
If you want to talk about pathetic, just consider that Mozilla still doesn't support SVG. KDE 3.2 ships with native SVG support. SVG is a well-liked, widely supported standard that is getting a lot of attention and has the potential to change the browsing experience for the better, today. KDE developers realize this, and that's why Konqueror now supports SVG.
Re:yup... (Score:5, Insightful)
I dislike this extension. I have no idea whether this is a Microsoft-introduced extension, but I would strongly suspect so. Microsoft has a general policy of building a browser that trusts remote web sites to do a good job of presenting content and not being malicious, and can make it easy to make poor design decisions. I cannot think of a good reason to change scrollbar colors -- from a HCI perspective, this is an extremely poor idea. The user spends a long time learning to immediately recognize the scrollbars on the system, and this would make scrollbars look different at different sites. Mozilla and most other browsers have taken a much more restrictive approach, not letting remote sites have as much control over a user's computer. This approach is more security-centric, and, I've found, works better.
It's not just this one extension, but a vast number of things -- sites bookmarking themselves, sites popping up windows, and all kind of other nastiness that I boggle at every time I use IE on someone's computer.
Re:yup... (Score:2)
Re:yup... (Score:4, Interesting)
As far as I can tell, the overwhelming majority of people who try and change scrollbar colours do so to make them blend in with the colour scheme used on their website. This usually makes them far less obvious.
No they aren't. Scrollbars can appear in frames, iframes, <object> elements, textarea fields and elements with overflow: scroll set. It's very easy to miss them in a large number of cases, even if you are an experienced surfer.
In any case, anybody who dislikes this misfeature should vote for the bug [kde.org].
Re:yup... (Score:2)
Chicken and the egg. Why did NCSA Mosaic implement HTML? No one uses it, this gopher thing is all we'll ever need.
XSL isn't really complex, check the w3school tutorial on it, you'll learn it in about an hour or two of messing around.
It does get a little ugly when working with tags that have arguments, but HTML gets ugly to when working on highly redundant elements (think news posts or other such repeated blocks of html), and XSL cleans that
Re:yup... (Score:2)
Personally, I think putting XSL in the browser is retarded. If you really like to construct your HTML from XML using XSL then that's your business, but do it on the server
I want to use XSL (Score:2)
Using XSL allows me to seperate Content, Presentation, and Navigation.
By putting just article text in an XML file, presentation in XSL and CSS, and Navigation in RSS files, I can make a site way more flexible.
If a site detects XSL capable browsers, Once the XSL, RSS, CSS, and images are in the viewers cache, article downloads are really fast.
It also means I don't have to dynamically generate or hand edit a zillion HTML files every time there's a new article to link to.
Re:I want to use XSL (Score:2)
Personally, I think that if they added the equivalent of C's #include to HTML (not like iframes but a
Re:I want to use XSL (Score:2)
With server side XSL, many XSL transformations have to share the same CPU. With client-side XSL, the viewer's CPU does the transformation. All the server CPU needs to do is blast bits from the filesystem to the network. This saves the website money, and the viewer time.
Re:I want to use XSL (Score:2)
Re:yup... (Score:1)
http://www.mozilla.org/projects/svg/
Re:yup... (Score:1)
Re:yup... (Score:2)
What a dumbass. It actually is his problem because next to no one is going to visit his site... It looks like his intention is to only cater to Moz fanboys
Re:yup... (Score:2)
I much prefer Firefox for surfing, though I admit Konq is a good file manager.
To be fair to the KDE developers (Score:5, Informative)
shouldn't it be apple's (Score:5, Funny)
Re:shouldn't it be apple's (Score:2)
LiveConnect in Konqueror? (Score:1)
Apple giving back would be a better title. (Score:1)
Cecil