Or are we still professing our hatred for everything Adobe?![]()
Oh, even without this problem, there are still plenty of good reasons to express hatred for everythign Adobe.
Or are we still professing our hatred for everything Adobe?![]()
Oh, even without this problem, there are still plenty of good reasons to express hatred for everythign Adobe.
WoW was just an example. It seems a number of 3D games (quite possibly anything that utilizes the video card) will cause the problem. Are you going to rationalize that and any other cause as devs using deprecated libraries? It doesn't take a rocket scientist or a developer to figure this one out. Also, this is suspiciously similar to the 4850 lockups earlier this year. Airport was linked to that as well. Was that just bad devs? I'm pointing a finger squarely at Apple because there are many different ways to cause the issue. Try reading something other than the anti-Adobe circle jerk in this thread. Not saying that Adobe doesn't suck, but it isn't their fault in this particular case.How can you be sure? If Blizzard is slow to update their code, we could be seeing the same thing there too. I'm not saying Apple's off the hook because they've been known to let their older libraries and APIs languish but if Blizzard and Adobe both linger and refuse to update their programs in a timely manner, that means they share some of the blame too.
And if you've ever done any development, you'd know that it's very complicated and just because resetting Airport fixes it doesn't definitively prove anything.
In any case, you should ask yourself why you're so convinced it's one party to blame over the other... even before Apple's own engineers have figured it out. Examine your own biases for a moment. Think about how complicated this stuff gets and ask yourself why you would blame either side at this stage.
Meanwhile, I'll be thanking god that you're not a judge.
Does anyone know if this issue has been resolved yet? Or are we still professing our hatred for everything Adobe?![]()
Look at my post above, looks like it's solved with a reset / reboot. Apparently, Windows fanbois saw blood in the water. It happens so seldom that they need to swim in it for a bit, before they go back to the dark side.
Apple is removing all Carbon in this transition. Any piece of Carbon that allowed Adobe to move it's tools from Classic to Carbon will soon be gone.
I went to this site, and this is what I found: Dated 9 SEP 2009
Version: Flash Player 10 - 10_0_32_18
Steps to reproduce:
1. Go to hulu.com. Stream a TV show. Pop it out into a new window and play back at 2-3 times normal size
2. On a 2009 model Mac Pro with 8 Nehalem Xeon processors and 12 GB of RAM, flash uses 50% of all CPU time available, and uses all cores. In 10.5, CPU usage was substantially lower (monitor with activity monitor.)
3. There is no 3.
Actual Results:
CPU usage is the highest I have ever seen for video playback. For comparison, the same machine uses virtually no CPU playing back a 1080p video at full screen on a 2560x1600 display.
Expected Results:
CPU usage should not be high for this operation. If this were a laptop, the battery would be drained in a hurry. Compare to quicktime playback of just about any video format, or to Silverlight, for much better video playback performance.
50% CPU Usage on an Mac Pro with 8 Nehalm Processors and 12 Gigs of RAM!
What chance do us "normal" Mac Users have? This is clearly an Adobe Screw-up!
Apple does tend to move on from their legacy stuff pretty quickly, but they do it so they don't have to support stuff that's old. The majority of their user base seems pretty OK with that.32-bit Carbon is still there, and will be until Apple needs to devalue another big chunk of the userbase to generate new sales. Probably 2 or 3 years from now.
It is simply impossible to test every single hardware/software/application combination for every possibility
Yep. That's why they don't have much of a userbase.Apple does tend to move on from their legacy stuff pretty quickly, but they do it so they don't have to support stuff that's old. The majority of their user base seems pretty OK with that.
Jeeez, and here I am expecting Apple to provide 5 years of security updates after last retail sale. And there you are, saying you don't give a darn if the things implodes on Year 5, Day 366.Personally, I'm OK with software that's 5+ years old not working well, or at all even. Apple has always pushed the envelope here, maybe too much in some cases, but it works for them.
Not that it hasn't already been said a thousand times already on this thread, but I concur that Flash on OS X is complete garbage. Spinning beach balls and the ubiquitous "Script is causing Flash player to run slowly" nonsense. And running a Flash movie (even a low-res YouTube video) on my MacBook is a guaranteed way to start the fans running at full speed. Ridiculous.
Flash OS X sucks. Fix it, Adobe, or an enterprising upstart will gladly take your place.
I hope the problem can be fixed. That would really be a huge disappointment for someone that is getting their first Mac.
[Update] Can Adobe send their programmers to training so they can write better Mac apps?
Wirelessly posted (Mozilla/5.0 (iPod; U; CPU iPhone OS 3_1_2 like Mac OS X; en-us) AppleWebKit/528.18 (KHTML, like Gecko) Version/4.0 Mobile/7D11 Safari/528.16)
I dunno, we'll see. I'll be heading over there to try stuff out and troubleshoot. One thing he didn't try that worked for me is copying the contents of the cd to the desktop, then running it from there. That worked for me for a couple apps, oddly enough.
As if we needed another reason to ditch the crap technology that is Flash!![]()
LOL. Amazing how it's Adobe's fault and not Apple's fault that their new computer doesn't behave properly; that their new operating system doesn't behave properly when everything was fine under Leopard, what the recent versions of Mac flash was designed to work with. Never mind how flash works fine on PCs and Windows7. Yes, it's Adobe's fault that Apple's new version of its operating system sucks. I haven't put it on my MBP yet and I'm glad I haven't since it's obviously bad news. And I cannot put it on my PowerMac I'm typing on now since Apple ditched 1/3 of its users with it as well. Yes I would say it's Apple's fault it's screwed up, not Adobe. I realize I'm in the minority given the huge number of completely unobjective and irrational fanatics the Apple market has worshiping everything it does no matter how poorly, but then I don't give a crap. I use what works best for me in a given situation, not what Steve (Jobs) or Steve (Ballmer) wants.
I mean for all the poo-poo about Flash, it's amazing that it works perfectly fine and smooth on my 2001 era PPC based PowerMac on either Tiger or Leopard. Yes, it MUST be Flash that's the slow crud-based problem, not those brand new 2009 dual and quad-core powered Macs that run 3-5x faster than this machine since it runs SO NOT poorly on a mere 1.8GHz G4.![]()
WoW was just an example. It seems a number of 3D games (quite possibly anything that utilizes the video card) will cause the problem. Are you going to rationalize that and any other cause as devs using deprecated libraries? It doesn't take a rocket scientist or a developer to figure this one out. Also, this is suspiciously similar to the 4850 lockups earlier this year. Airport was linked to that as well. Was that just bad devs? I'm pointing a finger squarely at Apple because there are many different ways to cause the issue. Try reading something other than the anti-Adobe circle jerk in this thread. Not saying that Adobe doesn't suck, but it isn't their fault in this particular case.
You can sit there rationalizing and trying to defend Apple all you want while whining that others are too quick to judge. I've seen way too many varying reports to put the blame anywhere else.
I started to love Silverlight-enabled websites on my Macbook3,1... And that says a lot.
32-bit Carbon is still there, and will be until Apple needs to devalue another big chunk of the userbase to generate new sales. Probably 2 or 3 years from now.
Um, this isn't Adobe's fault... IT'S APPLE'S INFERIOR OS!
I'm assuming this is an Adobe issue, but who knows -- maybe it's some weird interaction with the 64-bit Safari?
All I can say is that SL made me find, install, and fall in love with ClickToFlash!
Jeeez, and here I am expecting Apple to provide 5 years of security updates after last retail sale. And there you are, saying you don't give a darn if the things implodes on Year 5, Day 366.