Mozilla Exec Claims Apple is Hunting OSS Browsers 539
Rob writes with a link to a Computer Business Review article on the negative impact Mozilla COO John Lilly sees Apple is having on Open Source. Lilly claims that Jobs' recent discussion of Safari on Windows is an attempt to create a duopoly of browsers (IE and Safari), with Firefox and the rest on the outside looking in. "The graph 'betrays the way that Apple, so often looks at the world,' Lilly said. 'But make no mistake: this wasn't a careless presentation, or an accidental omission of all the other browsers out there, or even a crummy marketing trick,' he said. 'Lots of words describe Steve and his Stevenotes, but 'careless' and 'accidental' do not. This is, essentially, the way they're thinking about the problem, and shows the users they want to pick up.'" We discussed an analyst's opinion on this subject this past Friday.
I have a MBP... (Score:3, Informative)
Re:what Apple/Jobs should do is: (Score:4, Informative)
So apple spends no time/money, opens a new source of google search bar revenue, AND gets a wider iphone "sdk"
Safari on windows was a success before Jobs announced it
Ummm...it is open source...well sorta.... (Score:2, Informative)
"Safari uses open source software -- for its web page rendering engine, Safari draws on KHTML and KJS software from the KDE open source project. Being a good open source citizen, Apple shares its enhancements with the open source community"
Re:On not being #3 (Score:5, Informative)
Unfounded (Score:3, Informative)
The exec also highlighted Mozilla's attitude about market share: "We've never ever at Mozilla said that we care about Firefox market share at the expense of our more important goal: to keep the web open and a public resource,"
I don't see how Safari and IE will be causing problems. The nature of the web/internet is that it's open (except in extreme cases, of course). If Apple/MS does something nasty, the community will cry foul and move to an alternative, or make one themselves. Isn't that how mozilla got started?
Personally, I'm more worried about careless legislation and government regulation, and politicians who may still refer to the web as the Information Superhighway. yeah, I'd trust those guys to be in charge
Re:Imminent Death of FireFox Predicted. JPGs at 11 (Score:5, Informative)
Re:Apple on Windows (Score:3, Informative)
1996 called (Score:5, Informative)
Re:what Apple/Jobs should do is: (Score:3, Informative)
No, not really. (Score:4, Informative)
Re:Not about market share (Score:5, Informative)
Re:Um... what? (Score:5, Informative)
So you're not Apple's target audience for Safari on Windows anyway.
what part of this picture [flickr.com] and this picture [flickr.com] is everyone having such a hard time comprehending? Apple's target audience, is all the users that don't use IE. Steve Jobs has clearly shown this.
Here's what I'm referencing. [jubjubs.net] Jobs says: "Well we dream big. We would love for Safari's marketshare to grow substantially. That's what we'd love." Steve Jobs doesn't just want Safari available so people can test their websites quickly at their same Windows box, he want's all of the market share from Opera/Firefox/etc. If his graph would've shown market share eaten up from IE there wouldn't even be these discussions going on, but instead what we see is an inside look into Steve's view on how he wants the market to change.
Re:Um... what? (Score:4, Informative)
It's not terribly useful, though, because auto-complete is faster -- and Firefox's autocomplete also takes advantage of Google's suggestions feature to show me a list of searches I haven't even made yet. (Maybe Safari's does too... I haven't tried it, because Apple hasn't released a version that will work on any of the operating systems I use.) What's the point? If I want to close a tab, I middle-click on it, which is the default behaviour in Firefox. It's more convenient, because I don't have to hit a tiny close button, I can aim for anywhere on the tab. It's safer, because when I just want to select a tab, I can click anywhere on it with the left button, and not risk accidentally closing it. And it leaves more room on the tab for the name of the site.
Hey, it's not my fault if you bought a computer that only came with a one or two button mouse.
That said, I'd use Safari as well if I could - some sites don't work properly in Firefox, and Konqueror is painful to use. Sadly, Apple haven't released a Linux Safari, so I don't have that option.
Re:I have a MBP... (Score:3, Informative)
Ever use Mail.app for IMAP? For multiple IMAP accounts? If you didn't have problems with IMAP you are lucky.
I've used Mail.app for a while with IMAP. There were workarounds I had to do to get it to work with 1 account and that was problematic enough even after the workaround. With 2 accounts it was unusable.
I switched back to Thunderbird as well, at least it has working IMAP support. It also has a few features Mail.app doesn't have, like tags.
I'll give Mail.app another chance with Leopard. But until then, I'll have to agree with the other guy, Mail.app is weak.
Re:Pie Chart is all about marketing (Score:5, Informative)
Re:Um... what? (Score:2, Informative)
No. (Score:2, Informative)
Safari is not a "third standard". First, it's based off of KHTML, and second, it adheres to the W3C standards, just like good browsers should.
Unintentional quirks aside, there are only two standards: The W3C's, and Microsoft's de-facto one. So where's this "third standard"?
Re:Who Cares About Motivation or Desires? (Score:3, Informative)
No, it was Safari. Take it from someone who followed Acid2 from the time it was announced. Even this list of Acid2 in major browsers [howtocreate.co.uk], made by an Opera employee, credits Safari with making it there first.
The scrollbar controversy you're thinking of was with Konqueror and in iCab. Safari developers (well, mainly Dave Hyatt) wrote a lot of code to pass Acid2, but WebKit had already diverged enough that Konqueror's developers weren't able to just apply the patches he released. They had to reimplement most of the changes themselves. They and iCab both missed the scrollbar -- as did the Web Standards Project when they looked at the results -- because it wasn't mentioned in the guide. Months later, some Opera folks pointed out the scrollbar issue in those two browsers.