Sidebar Sidebar
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.

No more Safari leaks

damn i just got that e-mail *cries* :'(
i wanted more safari builds so bad and now some deranged and stupid developer ruined it for all the other people who want safari :'(
why why oh why do you have to do this apple?
 
Well, that answers some questions about whether or not Apple was allowing the leaks just to get user feedback on rumors sites. I have a feeling we'll see some form of Safari pop up again, before it goes into public release.

Dan
 
Wow that sux, you would think they were just letting it slide so that they could get free feedback but I guess not.
attachment.php


Just seems silly to me that they didn't release them all pubicly, what have they got to lose, bandwith costs?

Ah well, v67 seems ok for me, I guess........

<patiently waits for next version>
 
They apparently didn't feel that those were ready for public consumption--that the problems needed a more savvy user or programmer to deal with failures until the next public release.
 
I guess we brought this upon ouselves. Every leaked beta was spread around so quickly, Apple had to do something. I just wish it wasn't this. But Apple shouldn't slow down development in order to ensure that the public won't get unreleased builds. That is just plain stupid in my opinion.

Oh well. Hopefully that June 30, 2003 beta expiration for Safari still holds true. :)
 
wouldn't you think the more we get it, the more feedback they'd recieve, I'm sure they recieved a heaps of stuff about v64 and how crap it was.
 
i tried version 67 too, and it didn't work at all; it quit when I chose New Window from the File menu.

But what was interesting, was that it was half-localized to norwegian (because of my norw. os version). Previous versions have been english only. Lots of "localization string not found", though. Maybe an OS update is needed before it works properly. :)

Also, it broke my favorites in safari 64, i think it moved them to another folder named something else in norwegian. god knows what.
 
Originally posted by NavyIntel007
If Apple wasn't like freakin Fort knox all the damn time they wouldn't have to worry about it.
Click to expand...
dude what is your problem? apple didn't even have to make a program like Safari!
The more buggier and newer builds were for developers to check out and fix, not for people like you to play with, yell about the bugginess of the program and send bug reports.
There's a reason why Apple has a developer seed program :rolleyes: :eek:
 
Originally posted by übergeek
dude what is your problem? apple didn't even have to make a program like Safari!
The more buggier and newer builds were for developers to check out and fix, not for people like you to play with, yell about the bugginess of the program and send bug reports.
There's a reason why Apple has a developer seed program :rolleyes: :eek:
Click to expand...

Releasing regular nightly builds never hurt Mozilla or the Camino projects.
 
Originally posted by NavyIntel007
Releasing regular nightly builds never hurt Mozilla or the Camino projects.
Click to expand...
So? Safari isn't really open source and even if it was Apple doesn't have to release nightly builds.
 
ha ha...this is no surprise...

I'm sure Apple has seen the numerous posts regarding the latest seeds of Safari and all of the unqualified users with it... :rolleyes:
 
Originally posted by mac15
wouldn't you think the more we get it, the more feedback they'd recieve, I'm sure they recieved a heaps of stuff about v64 and how crap it was.
Click to expand...

Now that is incredibly helpful feedback. I'm sure that's just the kind of feedback they were really seeking to avoid.

Enthusiasm does not equal helpfulness. :rolleyes:
 
RE: just make it public

Except what about damage control - what if there's a serious problem that causes safari to meddle with the system in a serious way? Now, suddenly, Apple has to deal with all these inexperienced mac users whining about their computers on apple help lines and support pages. Even if Apple said they would not provide any support for these beta versions, it is unrealistic to think that they will not have to deal with a serious problem if it affects mac users on such a large scale.
 
Re: RE: just make it public

Originally posted by maxterpiece
Except what about damage control - what if there's a serious problem that causes safari to meddle with the system in a serious way? Now, suddenly, Apple has to deal with all these inexperienced mac users whining about their computers on apple help lines and support pages. Even if Apple said they would not provide any support for these beta versions, it is unrealistic to think that they will not have to deal with a serious problem if it affects mac users on such a large scale.
Click to expand...

Correct. At first I also thought why not post nightly builds? Get as much feedback as possible! But like stated above, I'm pretty sure that Apple would be facing more support-problems than feedback.... if ya know what I mean.
Still, I think it's a pity. It was fun keeping up to date with Apple's gr8 browser.
 
Originally posted by kjottbein
i tried version 67 too, and it didn't work at all; it quit when I chose New Window from the File menu.

But what was interesting, was that it was half-localized to norwegian (because of my norw. os version). Previous versions have been english only. Lots of "localization string not found", though. Maybe an OS update is needed before it works properly. :)

Also, it broke my favorites in safari 64, i think it moved them to another folder named something else in norwegian. god knows what.
Click to expand...

I noticed the same thing (in Dutch). The fact that Safari is translated probably means that no new features are planned and that we will see the final version soon.

Also I noticed that Safari works fine if you set english as language in system preferences. Other languages seem to crash Safari.
EDIT
Just remove (inside Safari.app) /Contents/Resources/CrashingLanguage.lproj
/EDIT

Seems that Apple leaked 1 build too much.
 
Remember the first Safari build was very buggy, deleting many people's /tmp directory. We don't want another fiasco like that again.
 
67? Hmm, so I guess all those 'smart' guys who so aggressively defended and declared without any knowledge that ALL Safari builds were by 2's (60, 62, 64, etc) are feeling pretty STUPID right now as noted in the Safari 65 thread.

A real shame. I was enhjoying the seeded program and it's a shame that almost every verrsion was leaked or info about each.
 
I don't know why some people are so upset about this. Apple didn't say there wouldn't be any more public betas, just no more seeds to developers. Kinda sucks from a developer standpoint, but Apple had no other choice.
 
Originally posted by Hmm
I don't know why some people are so upset about this. Apple didn't say there wouldn't be any more public betas, just no more seeds to developers. Kinda sucks from a developer standpoint, but Apple had no other choice.
Click to expand...

People are upset because now they won't get leaked builds, or leaked info on the beta software. I was a seeded beta tester for Safari and I'm saddened that some idiot had to leak the latest build to get the beta program shut down. I hadn't received an email for the 67 build so that guy must've done it immediately after the email because I never got an email or a chance to download the build.

The seeded program has been shut down as I logged into the program to find more info.
 
You must log in or register to reply here.
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.
Top Bottom
Back