Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
Love it! You got me laughing!

Flash has been gut-shot by Apple, and is slowly dying. Adobe is the hysterical mother, cradling poor Flash in her lap, screaming, "No! You can't die! You're going to live forever!!!"

Alternate scene: "It's just a flesh wound!"
I'll take whatever you're having.
 
???
I kinda think of crashing as a pretty serious performance issue.

Actually, it tends to crash at the end of long YouTube videos, and since I just need to click to launch the next one, there's no pain on my part.

For my use case, I'm OK with the tradeoff. It's not like it's randomly crashing, which would be unacceptable.
 
I'd stick with the Gala preview instead of the release version. The HW acceleration really helps with the CPU usage and temperature as well as the performance.
 
That's not accurate to say. Third parties already had access to hardware H.264 decoding long before March, and the use of the H.264 dedicated API created in March is predicated on Cocoa. Flash Player did not become a Cocoa app until 10.1 (i.e., this very version), more than eight years after Apple warned of the deprecation of Carbon.

To imply that the feature was missing until Apple allowed Adobe to add it is both false and misleading. Adobe could have taken advantage of it at any point had they updated Flash player sooner or had they used a native-code approach to playback by building on top of Quicktime (the API, not the player).

You really need to post this more places, because this is one of the arguments apple-haters (or just pro flashers) use quite often; blaming Apple for the lack of H.264 support until recently. That's not to say one side is right or wrong though, they both have obvious flaws in their logic.
 
Something that I dont get is this.

All you Mac owners moaning that Adobe sucks, and that flash is crap.

Why not uninstall Flash altogether?

Forget the pop-up blockers you so love to use, if you dont install it you wont have system issues and crashes on sites that use flash.

Surely thats the solution?

Then you can view pages like the iPad and iPhone does.

That's the way to stick it to Adobe, isnt it?
 
Something that I dont get is this.

All you Mac owners moaning that Adobe sucks, and that flash is crap.

Why not uninstall Flash altogether?

Forget the pop-up blockers you so love to use, if you dont install it you wont have system issues and crashes on sites that use flash.

Surely thats the solution?

Then you can view pages like the iPad and iPhone does.

That's the way to stick it to Adobe, isnt it?

A lot of people do, including me. Flashblock.
 
I like how download times are often given for 56k modem speeds. Is there anyone who still uses dial-up?
 
Adobe: "I'll bite your legs off!"

You guys have inspired me... :D

appleflash.jpg
 
Something that I dont get is this.

All you Mac owners moaning that Adobe sucks, and that flash is crap.

Why not uninstall Flash altogether?

Forget the pop-up blockers you so love to use, if you dont install it you wont have system issues and crashes on sites that use flash.

Surely thats the solution?

Then you can view pages like the iPad and iPhone does.

That's the way to stick it to Adobe, isnt it?

I know. If you think about it, it's really weird to be so passionate about disliking flash. It's really like one of those who cares things. But in reality it's the typical patter of certain people here. No one thinks about Nintendo here, but if Apple goes against Nintendo, then Nintendo is such a horrible lazy company. Fact of the matter, in 3 years flash video cpu usage will probably be too low to even matter. If a 720p flash video uses 12% CPU power on certain computers, then imagine in 3 years with smaller and faster computers.
 
I know. If you think about it, it's really weird to be so passionate about disliking flash. It's really like one of those who cares things. But in reality it's the typical patter of certain people here. No one thinks about Nintendo here, but if Apple goes against Nintendo, then Nintendo is such a horrible lazy company. Fact of the matter, in 3 years flash video cpu usage will probably be too low to even matter. If a 720p flash video uses 12% CPU power on certain computers, then imagine in 3 years with smaller and faster computers.

No, because Nintendo makes an excellent product... and doesn't blame the competition when they fail.

The passionate dislike for Flash (for me at least) pre-dates the iPhone and iPad. I've long hated it for two reasons: it needlessly hogs resources and it's become the favorite crutch for mediocre Web developers.
 
No, because Nintendo makes an excellent product... and doesn't blame the competition when they fail.

The passionate dislike for Flash (for me at least) pre-dates the iPhone and iPad. I've long hated it for two reasons: it needlessly hogs resources and it's become the favorite crutch for mediocre Web developers.

The reason I brought Nintendo up was because a month or so ago there was an article here on MacRumors saying that Nintendo now sees the Iphone as it's biggest competitor and not the PSP. As expected certain Mac users who have no idea about video games or Nintendo started bashing them.
 
That's not accurate to say. Third parties already had access to hardware H.264 decoding long before March, and the use of the H.264 dedicated API created in March is predicated on Cocoa. .... used a native-code approach to playback by building on top of Quicktime (the API, not the player).

Then how come this only works on 10.6.3 (after Apple shipped an update ) and only on the latest GPUs ?

http://developer.apple.com/mac/library/technotes/tn2010/tn2267.html

If it existed long ago in the general Cocoa API why does Apple only support this on the latest bleeding edge OS drop and a limited subset of GPUs ?

There is a huge difference between dragging in Quicktime and sticking an additional layer of abstraction (moving your software and the decoder farther apart ) and simply being able to pump data through and getting a simple decoded buffer ( which can do overlays , etc. on).

The OS is suppose to give apps access to shared resources. Apple did that by hiding it behind a think layer of Quicktime. Very similar to providing an "fopen" as a low level interface to a file and the more complicated Cocoa interface to a file. There is little reason should block/cripple the standard 'C' library access to a file. Some apps need something that is low level, lightweight, and direct.
 
Yet another joy of my peaceful and quiet digital world of flashblockers... I don't have to bother downloading this PoC.

If you don't have Flash, you don't really need a Flash blocker, do you?

(If you do have Flash anyway for the rare site like YouTube [sorry, I like Firefox :D -- which doesn't support YouTube's HTML5 codec], then you should upgrade anyway for security reasons.)
 
I can't believe they released it without hardware acceleration. I'll just keep using the Gala version.
 
That's not accurate to say. Third parties already had access to hardware H.264 decoding long before March, and the use of the H.264 dedicated API created in March is predicated on Cocoa. Flash Player did not become a Cocoa app until 10.1 (i.e., this very version), more than eight years after Apple warned of the deprecation of Carbon.

To imply that the feature was missing until Apple allowed Adobe to add it is both false and misleading. Adobe could have taken advantage of it at any point had they updated Flash player sooner or had they used a native-code approach to playback by building on top of Quicktime (the API, not the player).

Not true. In order for Flash to support anything, the browser first has to support it in the plugin framework. This support varies by browser and by browser version. There is a chart on some Adobe employee blog somewhere.

darkplanets said:
You really need to post this more places, because this is one of the arguments apple-haters (or just pro flashers) use quite often; blaming Apple for the lack of H.264 support until recently. That's not to say one side is right or wrong though, they both have obvious flaws in their logic.
Unless he works for Apple PR, it isn't his job to spread FUD.

Max(IT) said:
without Gaia, it is just another crapware from Adobe ...
Actually, there are a lot of overdue performance optimizations in 10.1. Hardware acceleration was not the only thing wrong with it, as any number of Jobs boys' will be happy to tell you.
 
why even bother installing it until it supports hardware acceleration?

Only if want to keep your head buried in the sand. There is an active Flash security advisory out. Installing 10.1 is one of the most important steps to fix that. (defect doesn't exist in 10.1 but does in older versions. )

If Apple just released the API a couple of months ago little change any update has gone though the normal stable release cycle. It is better for Adobe to do it right rather than rush some hasty hack out and then have to repair it later.

If anything the steady drumbeat of holes in Flash indicate the are not following good testing methodologies. Shipping fast is not particularly a good indicator of quality.
 
No hardware acceleration? Oh yah, smooth move adobe, this is sure going to make apple think twice about letting you guys on the iDevices, NOT.
 
LOL! Apple Fanboys make me giggle... hehe

As a long time Mac user I don't get this whole cult of personality edict that many mac users have but too each their own.

Now to the Facts about Flash Player 10.1 for OS X.

1. Hardware Acceleration.
Is available, but for H.264. The whole player is not hardware accelerated but certain key parts are thanks in part to the use of the core animation API. Having said that, these performance improvements to the drawing core are only available to browsers that use cocoa ( Firefox users are out of luck )

2. H.264
Is not avaialble in this release but will be available later as the post suggest. This is INDEED due to the newly made API's that Apple released for H.264 decoding in 10.6.3. "matticus008" is wrong! While having the ability to decode H.264 was a available as a high level API it was NOT available as a low level API which is what Adobe needed to integrate Apple's hardware available into their own display stack ( this is not rocket science but just how software works )

3. Performance
Lot's of under the hood enhancement make 10.1 play content faster.

4. Security
Addresses the last security issue and is the most secure version of Flash up to date. Both virtual machines ( AVM1 for AS1 and AS2 and AVM3 for AS3) have been tightened up for security (specially AVM1)

5. Peer-2-Peer
This release has built in support for fast peer to peer computing opening new avenues for things like video chat and broadcasting.

6. Multi-touch support.
This has been known for sometime that 10.1 supports multitouch on portable devices but it also supports it on the desktop. Windows 7 only for now, I'm sure when Apple adds touch support to OS X Adobe will make it available for the Flash Player. 10.1 for Android, Palm Os will support touch when 10.1 is release for those platforms.

7. Memory Management
10.1 has better memory management than any of it's predecessors, specially when dealing with a lot of bitmap data.

8. Video Playback ( software engine )
Improvements here where most notable on the Mac platform which has seen a double digit reduction in the amount of CPU used for decoding H.264 content. In full-screen mode Flash Player 10.1 is now using OpenGL to blit the video pixels on the screen adding a significant amount of video performance while watching fullscreen HD content. Is it as good as a full Hardware accelerated solution, no but it is a marked improvement over the software decoder in 10.

This isn't a light weight release and is an absolute must for Mac users since this is the first Flash Player release ever with so much focus added to the Mac Platform ( mind you about 90% of the installs for Flash Player are on Windows ).

I have been working with the internal and public betas for more than a year now ( specifically on the mac platform ) and I can attest to all of the aforementioned improvements. No Bull$#!t, just real talk.

Cheers.
 
Something that I dont get is this.

All you Mac owners moaning that Adobe sucks, and that flash is crap.

Why not uninstall Flash altogether?

Forget the pop-up blockers you so love to use, if you dont install it you wont have system issues and crashes on sites that use flash.

Surely thats the solution?

Then you can view pages like the iPad and iPhone does.

That's the way to stick it to Adobe, isnt it?

Frankly, what most of us would like is if Adobe could take the time to get it to run right on Mac OSX.

The fact that blocking Flash by default means far fewer ads and annoyances while surfing the web, well, there's a reason why FlashBlock software is popular on Windows as well.

Gotta suck being a Flash (so-called) "developer" though. That's usually who gets offended by FlashBlock software. I'm guessing we hit a nerve?
 
Fact of the matter is is that Adobe makes a killing off its Mac clientele. From student copies of Adobe Suites to retail sales of the Mac line, they make a grip of money. It is truly insolent that they peddle their wares (really good wares too, I love CS4) and neglect other software for the same platform.

I would absolutely love it if they recoded Flash from the ground up to fully utilize OSX. But it seems like as always they are more interested in peddling Creative Suite CSwhatever than making the overall OSX computing experience better.

Shame on you Adobe.. seriously. Although thanks for Photoshop.
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.