[Athens]

hey im guessing most of you saw the tiger pictures on macrumors, since they are all directory listings only I made them into thumbnails and full screen shots at my site
http://brian.is.a.rootboy.net/tiger.php

I cant wait for tiger but I just hope that a 800Mhz G4 can handle it with out lag.

[Disgruntled Head of C-3PO]

Originally posted by Athens:
I cant wait for tiger but I just hope that a 800Mhz G4 can handle it with out lag.

News for ya, a Dual G5 can't handle it with out lag.

[Athens]

Originally posted by Disgruntled Head of C-3PO:
News for ya, a Dual G5 can't handle it with out lag.

Its still beta, I expect something different when it is released.

[Disgruntled Head of C-3PO]

Originally posted by Athens:
Its still beta, I expect something different when it is released.

I was talking about 10.3

[Ghoser777]

Lag? What lag?

[Athens]

Originally posted by Disgruntled Head of C-3PO:
I was talking about 10.3

I use 10.3 on a 800Mhz now, it runs great, I only get a slow down when I have WAY WAY WAY to much open.

Side note about the mini a good point was made about it. If you buy Tiger for 129, ilife for 79 and 79 for Apple Works, put in 220 more and you have a mac mini.

[Athens]

Im collecting more Tiger pictures, any one that has any to send to me by all means send it to peacefulnature@hotmail.com

[Mafia]

no lag here, with 10.3 atleast. i can't wait for tiger.

[Disgruntled Head of C-3PO]

Originally posted by Mafia:
no lag here, with 10.3 atleast. i can't wait for tiger.

Safari sometimes takes up 70% of 2 G5 CPU's for no reason.

[ManOfSteal]

Umm, I see a QuickTime 6 Pro serial available for the taking...

[goMac]

I certainly hope you're not a developer. Apple sent a nice little note in the mail with the last build regarding a few things, including screenshots.

[Athens]

Originally posted by ManOfSteal:
Umm, I see a QuickTime 6 Pro serial available for the taking...

I didnt even notice that. Well I hope ppl are honest LOL

[Athens]

Originally posted by goMac:
I certainly hope you're not a developer. Apple sent a nice little note in the mail with the last build regarding a few things, including screenshots.

Nope, these where posted by someone else as A directory listing, I just created a thumbnail veiw. You guys are sucking up all my bandwidth LOL 500 000MB since I posted it. You know I couldnt even imagine how many GBs this forum sucks up.

[Cadaver]

Looks like someone broke his/her NDA.
Cool screenshots, none the less.

[Mafia]

Originally posted by Disgruntled Head of C-3PO:
Safari sometimes takes up 70% of 2 G5 CPU's for no reason.

oh i don't use safari, firefox for life.

[Disgruntled Head of C-3PO]

Remember the days when everyone couldn't wait for the debug code to be taken out so OSX wouldn't be so slow?

Seems they never took the code out, people just bought faster computers.

[TailsToo]

Originally posted by Mafia:
oh i don't use safari, firefox for life.

I even bought the mug.

[demograph68]

Originally posted by Disgruntled Head of C-3PO:
Safari sometimes takes up 70% of 2 G5 CPU's for no reason.

Sometimes? I rarely see it take up more than 30% of my 800 Mhz. (I tested 1.3 DP 5)

[Disgruntled Head of C-3PO]

Originally posted by demograph68:
Sometimes? I rarely see it take up more than 30% of my 800 Mhz. (I tested 1.3 DP 5)

Even that is damn scary for a web browser.

[demograph68]

Most of the time I just get this:



(Safari is loading a page and downloading at the same time.)

[alphasubzero949]

Lag in Panther? How much RAM do you people have?

Yeah, Apple even sent the testers a nice little note too.

[Athens]

Originally posted by Cadaver:
Looks like someone broke his/her NDA.
Cool screenshots, none the less.

I think im going to go find some more and devote a entire section to it, thats if my bandwidth holds out, in the last 5 hours the site has sent out a GB of data.

[willed]

Originally posted by Disgruntled Head of C-3PO:
Safari sometimes takes up 70% of 2 G5 CPU's for no reason.

Sounds like you've got system issues

[Athens]

could be a plugin as well, my Safari runs fine. I do use firefox more often latly though.

[Superchicken]

Safari never takes up that much on me unless it hangs or something. Right now it might be taking up maybe 10-20% of a 1Ghz G4. I think you need to uhh... do something SWG.

[JHromadka]

Originally posted by Disgruntled Head of C-3PO:
Remember the days when everyone couldn't wait for the debug code to be taken out so OSX wouldn't be so slow?

Seems they never took the code out, people just bought faster computers.

Anyone still have that Mac OS X architecture graphic with the Debug Code listed?

[goMac]

The debug code is just going to get worse. You realize each buffer overflow patch is more "debug code".

[Angus_D]

Originally posted by goMac:
The debug code is just going to get worse. You realize each buffer overflow patch is more "debug code".

[roam]

Originally posted by goMac:
The debug code is just going to get worse. You realize each buffer overflow patch is more "debug code".

They might as well leave it in, OS X can't get any slower, and I doubt we'd notice. Hell, enlarging a metal window is like pulling out my teeth with a claw hammer.

[Disgruntled Head of C-3PO]

Originally posted by roam:
They might as well leave it in, OS X can't get any slower, and I doubt we'd notice. Hell, enlarging a metal window is like pulling out my teeth with a claw hammer.

On a Dual G5 with a 64 meg video card resizing a safari window is still comical as the updated window is nowhere near the cursor.

[roam]

LOL, that Quicktime serial works too. Fantastico

[Mastrap]

Originally posted by Disgruntled Head of C-3PO:
On a Dual G5 with a 64 meg video card resizing a safari window is still comical as the updated window is nowhere near the cursor.

Weird. On my 1.8 G5 there are none of the issues you're talking about. I am with willed, I think you've got system issues.

[Superchicken]

SWG has issues.

[Disgruntled Head of C-3PO]

Originally posted by Mastrap:
Weird. On my 1.8 G5 there are none of the issues you're talking about. I am with willed, I think you've got system issues.

Pfff, sure, it's my system, not every damn computer I've tested it on.

[Athens]

Originally posted by roam:
LOL, that Quicktime serial works too. Fantastico

SIgh i guess im removing that image when i get home tonight. its only 29.00 buy it like me and most others

[ReggieX]

Originally posted by Disgruntled Head of C-3PO:
Safari sometimes takes up 70% of 2 G5 CPU's for no reason.

Animated GIFs kill Safari, mainly because too many of them on the net have the frame delay set to 0 seconds, which IE magically adds a delay to. Funny that.

[mitchell_pgh]

Originally posted by ReggieX:
Animated GIFs kill Safari, mainly because too many of them on the net have the frame delay set to 0 seconds, which IE magically adds a delay to. Funny that.

then so should safari...

[UnixMac]

Originally posted by Disgruntled Head of C-3PO:
Remember the days when everyone couldn't wait for the debug code to be taken out so OSX wouldn't be so slow?

Seems they never took the code out, people just bought faster computers.

I like that! Good one.. I admit, the Dual G5 isn't quite as snappy as it should be (GUI wise).. however, with tiger offloading Screendraws to the GPU, I expect it to be... Or I'll take it back!

[goMac]

Originally posted by Angus_D:

You know what a buffer overflow is, right?

Essentially most operations regarding data input and output have to have debug code attached to them. In a language like C, if you have an array 99 elements long, you can still access array 100 and you won't get an error. Instead, C will return you the next spot in memory past your array, which is probably some other part of the running program. If you can figure out reliably, using a buffer overflow, a part of the program which contains some critical code, instead of reading from that part of memory, you can write to it. This means you just inserted code into a running program, altering its functionality, perhaps making it do something bad. The only way to solve this is debug code making sure no array accesses are made past the length of the array. This is one strength of open source. You have lots of people checking code for problems like these. In a private corporation, like Microsoft, programmers get lazy and don't bother checking for these sort of exploits, and no one notices the proper debug code isn't in place. IMO Windows is faster than OS X (in places) because of the lack of things being coded properly.

[Disgruntled Head of C-3PO]

Originally posted by UnixMac:
I like that! Good one.. I admit, the Dual G5 isn't quite as snappy as it should be (GUI wise).. however, with tiger offloading Screendraws to the GPU, I expect it to be... Or I'll take it back!

Doesn't 10.3 already do that? All 10.4 will do is throw a ripple effect and the GPU as far as I know.

[Athens]

Originally posted by goMac:
You know what a buffer overflow is, right?

Essentially most operations regarding data input and output have to have debug code attached to them. In a language like C, if you have an array 99 elements long, you can still access array 100 and you won't get an error. Instead, C will return you the next spot in memory past your array, which is probably some other part of the running program. If you can figure out reliably, using a buffer overflow, a part of the program which contains some critical code, instead of reading from that part of memory, you can write to it. This means you just inserted code into a running program, altering its functionality, perhaps making it do something bad. The only way to solve this is debug code making sure no array accesses are made past the length of the array. This is one strength of open source. You have lots of people checking code for problems like these. In a private corporation, like Microsoft, programmers get lazy and don't bother checking for these sort of exploits, and no one notices the proper debug code isn't in place. IMO Windows is faster than OS X (in places) because of the lack of things being coded properly.

Its not just that its the little things we take for granted that isnt in Windows that makes it faster. Example one, every thing in a Mac is in real time. You save something in a folder you don't have to hit the refresh button to show it, on Macs it shows it right away. Countless times I am looking for something that I just saved and because the window was already open I have to hit refresh on Windows. Another one is the way MacOS keeps track of files. This is also automatic and in real time. On windows if you move a Shortcut from one folder to another you killed it, you have to relink it because it stupid. On macs if you move a Alias from one folder to another it still works. Again real time updating and tracking of things. Other things such as Windows GUI being simple helps it to be faster.One thing I find better on OS X is if the computer is really busy I can still usally access the dock, and when one program is being a goof and not working well other programs are just fine. Many times on Windows if a program is hanging bad I cant even access the Start Menu and other programs slow down really bad too. Guess we have to decide if we want ease of use or speed. I personal have always loved how Mac OS all the way back to system 7 handled Alias and the instant updating.

[roam]

Originally posted by Athens:
SIgh i guess im removing that image when i get home tonight. its only 29.00 buy it like me and most others

Yeah, I'm not partial to being known as, "new user". lol

[Super Mario]

Quicktime is very good now!

[demograph68]

Any idiot can find a serial. It's not that hard.

[Super Mario]

Originally posted by demograph68:
Any idiot can find a serial. It's not that hard.

I know, friend! This idiot just now found a serial and it was so easy!

[insha]

Originally posted by roam:
LOL, that Quicktime serial works too. Fantastico

I hope you're joking!? 'cause it's only 29 USD and not to mention doing this is sooo like the habit of a winblows victim.

Why would anyone want to bootleg Mac software?

[Wiskedjak]

Originally posted by Superchicken:
Safari never takes up that much on me unless it hangs or something. Right now it might be taking up maybe 10-20% of a 1Ghz G4. I think you need to uhh... do something SWG.

I haven't noticed Safari taken up too much CPU on my machine, but it does seem to take up alot of RAM, and doesn't always give it back even after being closed.

[Angus_D]

Originally posted by goMac:
The only way to solve this is debug code making sure no array accesses are made past the length of the array.

Uh, no. Debug code is code that is inserted for debugging purposes. If you only insert bounds checking to help you find bugs in your programs, then you have even more issues than I previously thought.

[MilkmanDan]

safari all the way man.