Slashdot Mirror


Apple Terminates Safari Seed Program

coolmacdude writes "This morning Safari beta v67 was leaked to the Internet. Because this is the third time it has happened (v62 and v64 were leaked), Apple has apparantly had enough and decided to terminate the seed program that provided unreleased beta verisons to selected developers. In a email sent to all developers and posted on Mike Wendland's blog, Apple says: 'Due to Safari 67 postings to the internet, we have closed the Safari Seed project. We know that the majority of you are not responsible for the leaks to the internet, and we sincerely appreciate your feedback, time and effort with this project.'"

31 of 404 comments (clear)

  1. License by gmuslera · · Score: 0, Interesting

    This is not violating any kind of license, like GPL? After all, Safari is Konqueror based. Or that will run when the final version is released?

  2. Who woulda thunk it by jbellis · · Score: 5, Interesting

    given apple's history of siccing lawyers on sites that dare to post pics of the latest & greatest before they're officially unveiled, the only surprising thing is that it lasted this long...

    1. Re:Who woulda thunk it by Lewisham · · Score: 4, Interesting

      Actually, Apple has a pretty good past record of "leaking" pre-release code. The Register has gotton pretty blaise about it all. You only know if something shouldn't have happenend if heads publically roll, like the time the mirror face PowerMac designs were released to eWeek.

  3. I'm Confused... by terraformer · · Score: 5, Interesting

    Doesn't it make more sense for them to have as many testers as possible on pre-release builds? This way they find potential issues missed through the undoubtedly small QA team on the project.

    --
    Who are you? The new #2 Who is #1? You are #617565. I am not a number, I am a free man! Muhahaha.
    1. Re:I'm Confused... by disneyfan1313 · · Score: 5, Interesting

      It does and that's why there are public betas. Once the software gets out there in the open apple becomes liable (not from a legal but from a public relations standpoint) from any damage or drama the software causes. Would you like your software to be labled instable or buggy simply because someone in corprate wanted more testers out there?

      --
      -=SiGH=-
    2. Re:I'm Confused... by iabervon · · Score: 3, Interesting

      But why would Apple be liable (even from a PR standpoint) for problems with a beta leaked by somebody else? If it's being distributed by somebody else, the problems you have with it could just as easily come from the intermediary rather than Apple. It makes sense for them to limit who they actually give the software directly to, but they shouldn't care who ends up with what purports to be an unreleased version, whether or not it matches an intermediate Apple code base.

    3. Re:I'm Confused... by ydlman · · Score: 5, Interesting

      Another main reason that Apple may not want all these beta builds out is that they may contain features that may or may not make it into a 1.0 release. Perhaps they wanted to try out feature X (say tabs) and find that it doesn't work the way that they had planned and they don't want it in a 1.0 release. But now if they release 1.0 without a feature that has been in the seeds the public uproar will be incredible.

    4. Re:I'm Confused... by 90XDoubleSide · · Score: 4, Interesting

      Just go on the Apple support forums and look at how many people are compaining about the bugs in leaked builds. If people actually had the level of common sense you're giving thhem credit for, this wouldn't be a problem, but sadly they don't.

      --
      "Reality is just a convenient measure of complexity" -Alvy Ray Smith
    5. Re:I'm Confused... by constantnormal · · Score: 2, Interesting
      I remember in the pre 0.9.x days, when they were still called Milestone X, the releases were multiple months apart. And with the last beta release of it coming out about a month ago, I don't really thing you have anything to complain about.

      I remember those days also, but I also recognize that Mozilla is targeting a very broad spectrum of hardware platforms and operating systems, whereas Safari has an exceedingly narrow focus. And the KDE code base Safari uses was supposedly selected because it has an order of magnitude fewer lines of code to deal with. Given the hoopla with with Apple has rolled it out, and dangled their "public beta" in front of me, I expect pretty frequent updates. The last one was 2-18-2003, and "about a month ago" happened at the beginning of the week just ended. It looks as if it will be some weeks/months before we see another one released to the public.

      Mozilla has thousands of developers, whereas Safari has what, a couple dozen if that?

      I wish (at least, I think I wish -- I'm not sure that having so many developers wouldn't make the whole thing dissolve into unmanageable slop) it were true that Mozilla had thousands of developers. The reality is that there are a handful (probably fewer than Apple commits to Safari, but one cannot know, as that is Apple's business and not the public's) of full-time developers and on the order of hundreds (not thousands) who have contributed on a part-time basis over the years.

      The real advantage the Mozilla development methodology brings has little to do with the product being Open Source, Shared Source, or Closed Source -- although I believe that those in the Open Source camp will have a mindset that finds it easier to adopt this style... The Mozilla folks seem to care a whole lot more about the product they produce than those who mindlessly manufacture lines of code for a living. I have only rarely had a software provider respond to a bug report within hours of filing it with suggestions of things to try or requests for additional information -- except for the Mozilla and Camino(Chimera) development teams, who regularly respond within hours.

      There's a concept in software engineering called egoless programming.

      There have been a lot of programming concepts rolled out over the years. Personally, I think things called pride of craftsmanship or pride of ownership are going to stand the test of time a lot better than egoless programming. Yes, it's true that code has a very short useful lifetime, given the rate of change in the environment it operates in. And a fixation to one's work in such an environment is not a Good Thing. But I don't believe that people who are not somewhat emotionally involved in what they do are very good at it. It's part of a thing called Motivation. I'll take professional pride over egoless programming every time.

      Apple would rather release their browser on their terms, and fix the bugs on their terms. I'm content knowing that the engine of it is open source. Why isn't that enough? It's their code after all.

      This is from the Apple Safari page:

      As with Mac OS X itself, Safari uses open source software at its core. For its Web page rendering engine, Safari draws on KHTML and KJS software from the KDE open source project. And of course, being a good open source citizen, Apple

      shares its enhancements with the open source community.

      Certainly sounds to me like they're trying to convey the notion that Safari is open source. But it's pretty clear that it's a closed development process.

      To summarize my feelings on this -- no, a software provider does not have to be responsive to me as a user of their software. But if they do, I like it better. If they roll out a "public beta" of a product that they also advertise as "open source", and then slam the development

  4. Post Milestones with Talkback by The+Ape+With+No+Name · · Score: 3, Interesting

    Why not just post the thing with a Talkback-like client and get feedback/bug reports from everybody? I know it is closed source but why not develop a Safari fan base by letting a community build around it. This is what Apple is best known for, right?

    --
    Comparing it to Windows will be a moot point, since El Dorado is going to have a 40% larger code base than XP.
  5. Forget Safari seeds by Znonymous+Coward · · Score: 3, Interesting

    If you want to be on the bleeding edge use Camino nightly builds :)

    http://ftp.mozilla.org/pub/camino/nightly/latest /

    --

    Karma: The shiznight, mostly because I am the Drizzle.

  6. Why not release it on ADC? by ShatteredDream · · Score: 4, Interesting

    How hard would it be for them to put in the developer builds a little code to pop up a splash screen everytime that safari loads that reminds the user that it is a developer, not end-user build unless they disable that in the preferences?

  7. Perhaps they should look at Mozilla's approach by gusnz · · Score: 4, Interesting

    With the KHTML engine still undergoing internal tweaking for better DOM/CSS/etc support, I think Apple should look to the Mozilla project for their approach to browser development. Why not publicly release nightly betas, so users can post feedback on development as with BugZilla? Users don't expect the nightlies to be perfect, but it would keep the tweakers (and web designers like me) happy, and the developers would get a lot more feedback on their progress, whereas most casual users can happily download milestone releases.

    Otherwise, the standards compliance of the browser will possibly be delayed (all the esoteric little implementation issues, especially with CSS and DHTML). After all, many eyeballs results in better code, especially with something as complex as a web browser.

  8. Leaked builds probably helped Safari by RedX · · Score: 4, Interesting

    Without getting into the neverending "tabbed browsing" argument, I'll go out on a limb and say that these leaked builds will probably help Safari's marketshare in the long run. In browsing various Mac messageboards before and after v60 was leaked, I can tell you that many people dumped Camino the moment that tabs were discovered in Safari's debug menu. Had Safari's tabs been kept under wraps until the next public beta, Camino would have only matured and captured more users, which in the long run could've decreased the number of users using Safari. Of course this is all speculation. And I won't even get into the benefit that Apple realized by having a larger user base testing these builds.

  9. It's out? by krray · · Score: 3, Interesting

    It's out? Thanks. Quick Google search. Got it. Love it.

    Should I notify Apple that when you leave the tabs on all the time and "Open in tabs" a docked bookmark that the first tab always looks "active" (though the windowing for the tabs works fine)?

    It's too bad Apple is taking this stance. They should understand, realize, and if they were smart: CAPITALIZE on that fact that there _is_ a reason why us lowly end users are clamoring for the latest builds of Safari.

    It works. Like most Apple software it works very well -- even at the beta level. Yes, this is too bad...

  10. easter eggs by Anonymous Coward · · Score: 5, Interesting


    They should have done that trick where each developer gets a slightly different copy, possibly each having a different easter egg embedded inside. All they then have to do is download the version from the internet and trigger the easter egg to find out which copy was leaked and cut that developer off.

    --
    Dreamweaver Templates

  11. I disagree with the crowd on this by Henry+V+.009 · · Score: 5, Interesting

    1) They should have known that it would be available for download on the net as soon as they handed it out. If they didn't take that into account before starting the program they're idiots.

    2) A lot of people justify Apple here by posting the standard shit about it being terrible for the public to see an unfinished product. This is wrong and silly. Most people who come across this type of thing and are willing to install a beta are a) warez people who aren't gonna buy it anyway, or b) early adopters who are itching to try it out and are going to buy it no matter what.

    3) And finally some people are going to whine about the humanity of programmers having to see their beautiful program that they love like a child being stolen by the masses. Tell them to stop whining. The programmers are wage slaves. If the company earns more money because of massive warezing (that should be 'When the company inevitably earn more...') the programmers should shut up about the hurt to their souls and get back to fulfilling their contracts.

    Software companies act like this because they are run by idiots. You have no clue of the true magnitude of the crass stupidity they are capable of.

    And Apple just likes to throw temper tantrums. They probably lost more customers by canceling this program and making a stink than they would have lost by having betas escape into the wild.

    1. Re:I disagree with the crowd on this by JohnG · · Score: 4, Interesting
      "And Apple just likes to throw temper tantrums. They probably lost more customers by canceling this program and making a stink than they would have lost by having betas escape into the wild."

      Considering Safari is a free download I don't think they are complaining much about lost customers.

  12. Re:Not everyone distributes that way by Crass+Spektakel · · Score: 2, Interesting

    > One is confusion among a less educated (some might
    > also say intelligent)

    I wont jump for your "Mac users are stupid" trollbait, but let me me use my words to describe your theory:

    "the average mac user runs in danger downloading sources and binaries from a nearly secret cvs-like structure aside of the official updatemanager without noticing his wrongdoing"

    Only the paranoid survives .-)

    --
    "Life is short and in most cases it ends with death." Sir Sinclair
  13. Comment removed by account_deleted · · Score: 5, Interesting

    Comment removed based on user account deletion

  14. Re:Not everyone distributes that way by Ratso+Baggins · · Score: 2, Interesting

    Fair enough in principle, but what unique features & goodies are there in safari? Is it not "just a wrapper" to WebCore?

    --

    --
    "we live in a post-ideological world..." - Billy Bragg.

  15. Poor understanding by stewby18 · · Score: 2, Interesting
    I know that Apple probably has good reason not to make the various beta releases of Safari available to the public

    But they are still making beta's available to the public, just not every single beta. I imagine that their public beta releases (which seem to be based on more or less completing a new feature) will stay steady, just like they have been so far, and just like the X11 betas.

    Far too many people here are confusing the seeding program with the public betas, and blowing this way out of proportion.

  16. Why didnt they (Apple) take the same approach as.. by Anonymous Coward · · Score: 4, Interesting

    many game developers take when using a seed program.

    All seeds are digitally signed in one or more ways, so that when the seed is found on the internet, the guilty party can be identified and removed from the program.

    Another case of throwing the baby out with the bathwater.

  17. Re:So what? by oingoboingo · · Score: 2, Interesting

    Nowadays the only people using them are die-hards and people who got them in order to play with their version of Unix. I'd like to play with their unix too, but I'll be damned if I'm going to buy a whole new computer to do it.

    Interesting comment...I just bought an old PowerMac 7600/120 from eBay for exactly that purpose (ie: to play around with OS X). A few bucks on upgrades (a 500MHz G3 card from Sonnet and an additional 256MB of RAM, plus a 18GB Seagate Barracuda I had lying around, and an old Sony SCSI CD-RW drive), and the thing runs OS X pretty well. Of course I would have never paid the prices Apple wants to buy their equipment new. If Apple does OS X on Intel, Windows and Linux better watch out...

  18. Weird "beta" anyhow by yroJJory · · Score: 2, Interesting

    For a beta that's really alpha or dev (I thought the definition of beta was "All features in, bug fixes only"), I don't really understand why only certain "beta" releases are acceptable for the general public to use.

    Either it's a public "beta" or it's not. Which is it?

    --
    Jory
  19. Re:Why not just open the beta to everyone? by domeng24ph · · Score: 2, Interesting

    i use mozilla all the time but sorry to burst your bubble, it ain't the best browser...

  20. Watermarking, unique copies, etc. by isj · · Score: 4, Interesting

    I think it is quite interesting that people recommend that Apple should have embedded watmermarks, unique identifcation, steganography and other stuff in the beta download to identify who leaked the copy.

    Isn't this the same posters that normally oppose DRM? :-)

  21. Re:Too bad by cbreaker · · Score: 2, Interesting

    At first it was a hacked XP with the activation stuff disabled or worked-around.

    Unfortunately, many of these installs of XP were rendered unusable when SP1 was applied, forcing a switch to the "Corporate" (or as you say, VLK) edition.

    Either way, I'm sure MS is cooking up some way to have VLK in businesses without compromising the "security" of the product. Perhaps you'll be able to set up your own license authentication server/proxy in shop.

    Who knows, but if they are going to keep trying to enforce the product protection they won't stop at Windows XP that you buy at the store.

    As it's been stated before, MS needs new sources of revenue to continue functioning. It's the way the company is set up. This is one way to keep money coming in.

    I for one would never buy Windows, but there's other people out there that would if they couldn't easily get a copy from a friend, online, or from work.

    --
    - It's not the Macs I hate. It's Digg users. -
  22. Re:LGPL is viral by fault0 · · Score: 3, Interesting

    /me thinks you need to releive your repressed sexual energy somewhere. And please wipe off your keyboard afterwards, thanks.

    Anyhoo, replace "LGPL" with "GPL" in your post, and you're going in the right step.

  23. Nerr, duh? by DAQ42 · · Score: 5, Interesting

    Okay, I think some of you need a little education on how Apple operates.
    First off, the whole beta program fro Safari is/was managed by a small team. Second, that team has a goal to release either the next public beta or the full 1.0 release by June 30th, 2003. You can verify this by opening up the terminal and navigating to /Applications/Safari.app/Content/MacOS/ and typing in the command 'strings Safari | grep June'. You will see two line in the binary that read "Safari Beta will expire on June 30, 2003.
    Safari Beta expired on June 30, 2003."
    This means that they are on a deadline and have a lot of work to do. A lot of people who have posted here are suggesting that they should do MORE work and add easter eggs/stenographics/blah-blah/security tracking to the seeded releases. Now you tell me, does that sound like a good way to reach a deadline? Especially one that is hard coded into the binary of the public beta? Now you could argue that putting in an arbitrary deadline is a "bad idea" or whatever, but I think it's a great way to keep a project both on track and managable. Pressure to perform and all that rot.
    The other thing a lot of people are apparently misguided in thinking is that Apple was naive about releasing these developer seeds. For this you have to understand a little bit about Apple's corporate culture and social philosophy. While you may not agree with it, I and a lot of others, think it's a great experiment and helps move our culture along. To understand thier philosophy, just look at Apple's public stance on music piracy. They have put in place some very basic and easily defeatable mechanisms with the iPod that prevents users from sharing music freely with thier iPod. They have not completely crippled your ability to share music, however they do put s little sticker on the iPod's that says "Don't steal music." They have also publicly stated in many debates about music piracy that it is a social problem, not a technological one, and that technology will not solve the issue. So in that statement, they have made reasonably clear that they don't really want to spend a lot of time working on something that they see as inevitable.
    They also want to trust those that they sign up for the seed programs. If you can't trust your testers to give you good reliable feedback, you are wasting your time and effort and you won't get your project completed or your bug fixed.
    Now the thing with the Safari seeds is that they gave the seed users 3 chances, basically 3 strikes, your out. After the 3rd strike, they pulled the program because they saw it as more detrimental that useful. I'm sure they started getting an unmanagable amount of negative feedback or duplicate bug reports, or even worse, useless ones because all these people that downloaded the seeds that were not part of the seed program probably started sending in incomplete bug reports or even worse, stupid things like "the thingy with the buttons, doesn't work on my puter, fix it now assholes", or something to that effect. This means that those managing the bug database and trying to glean useful information or even just track any real bugs now have to sift through thousands of shit reports. Needle in haystack time.
    Any of this sound reasonable.
    And finally, the most telling thing would be the reports on rumor sites. Apple hates rumor sites. They are counter productive to thier business (believe it or now, they are). If someone reads on a rumor site that such and such feature is missing/broken/doesn't work or whatever on a rumor site, and bases thier judgement on that rumor sites word (I know, stupid people, but it does happen, I have plenty of ad hom proof), they end up loosing a potential customer, or thier market image gets tarnished.
    I don't know about most of you, but these are the reasons that I see Apple's decision to pull the plug as both necessary and smart on Apple's part. Argue all you want about "the way it should be" or whatever, but these are the realities of this business. If you

    --
    Don't Ask Questions. I don't know the answers and even if I did I wouldn't tell you.
  24. Re:Why not just open the beta to everyone? by feldsteins · · Score: 2, Interesting

    you say that all PC-motherboard makers are ignoring the market needs

    No, I'm saying that their business heavily relies upon being as backward compatible as possible so that corporate types buy truckloads of their desktops. That means not doing anything radical like omitting ISA (heh) and making damned sure to have every other port created since time began. Apple doesn't do things this way. Their business relies heavily on innovation and most importantly, in providing a total software-hardware experience. THey can do things like omit the PCI slots that virtually no home user takes advantage of in order to experiment wildly with the form factor. The iMac sold very well. Therefore I think my remarks match very well with reality. Home users aren't buying Dells because they have PCI slots. They're buying them because they can get a deal on last years model and because their brother-in-law has one. Period. Not that there's anything wrong with that, but it's definetly not because they have PCI slots. That is reality.

    it's only Apple's greed preventing PPC-CPUs and motherboards from appearing in stores at reasonable prices.

    I really don't think you understand their business. If CPUs and motherboards were available in stores for consumers to buy then people would build their own Macintoshes. THis would instantly drive prices down and everyone would rejoice. In fact, Mac whitebox makers would spring up in every city and you'd be able to have one custom built for you out of off-the-shelf parts for half what Apple charges for a computer. And it would also be the end of Apple itself. Even if they survived the transition to essentially a software-only company, they would lose the very things that makes them attractive - innovation and vertical integration.

    Apple would no longer be in a position to control the entire software-hardware continuum of the platform. That means cheaper prices, yes, but it also means "iffy" compatibility and the loss of the "one company designed this experience" feel. Scoff if you must, but this is the heart of the platforms appeal. That and software-hardware innovation like the firewire/imovie deal. Someone in Apple decided it was a good idea to bring digital video editing to consumers. The port didn't exist. The applications didn't exist. Now they do. Hard to do that when you have to convince seventy other companies to get onboard, each with their own idea on how to do it.

    In short, the "make the whole widget" vertical integration Apple has in the Mac platform is both the worst and the best thing about them. It keeps prices high and marketshare low, but without it they'd dissapear in a sea of other boxmakers and software makers, with no means of distinguishing themselves.

    --
    You like your Macintosh better than me, don't you Dave? Dave? Can you hear me Dave?