Skip to content

Comment on Flash Player: CPU Hog or Hot Tamale? It Depends.

Comments

This ducks the real issue.

I'm not all that concerned about the efficiency of the codec and of the mechanism that flushes video to the screen. That said, <video> in a web browser that's codesigned to work on a platform is always going to give a complex cross-platform app like Flash a run for the money.

I'm more concerned that Flash burns up CPU for no reason at all. I mean, my Mac Mini hits 100% CPU and sounds like a helicopter taking off when I've got a little tiny flash ad open on any tab. I got no trouble w/ internet ads, but it's ridiculous that one stupid ad should be able to completely disable the power management system on my computer.

Exactly. The article says that Flash isn't inherently slow. Is anything inherently slow if you take time to optimize it? Why has Adobe/Macromedia taken so long to get decent performance out of Flash?

I'd say the ball is in Adobe's court to actually make a version of Flash that doesn't suck on the existing platforms.

Because its easier, in a cross platform sense, to code to one device: the cpu. Graphics libraries, GPUs, and drivers are more different and thus require more knowledge, experience, debugging, etc.

The performance of flash is good enough for Adobe. It's not good enough for apple and, well, some of us. Steve Jobs called them lazy, precisely because they don't make more effort in this department.

AboutSource Built by g1lg1l

Hackerly is an independent reader for Hacker News, built on the public HN API. Not affiliated with Y Combinator.