New Adobe Flash Player Locks Down the Cookie Jar

CommanderFrank

Cat Can't Scratch It
Joined
May 9, 2000
Messages
75,399
With the release of Adobe’s Flash player 10.3, a new level of privacy and security has been established for the end user. The new v10.3 gives better control over both cookies and flash cookies with its new cookie-clearing system.

Flash Player 10.3 also streamlines the controls of the Flash Player privacy, security and storage settings within the local control panel of desktop operating systems, Adobe said.
 
Yet still no support for 64-bit browsers. Come on Adobe, Flash is heavily used on the net. You're holding the technology world back by not developing a native 64-bit Flash player. 64-bit software isn't a fad that is going to pass...
 
Yet still no support for 64-bit browsers. Come on Adobe, Flash is heavily used on the net. You're holding the technology world back by not developing a native 64-bit Flash player. 64-bit software isn't a fad that is going to pass...

Every 64bit browser I've used has been wholly inferior to its 32bit cousin.
 
Yet still no support for 64-bit browsers. Come on Adobe, Flash is heavily used on the net. You're holding the technology world back by not developing a native 64-bit Flash player. 64-bit software isn't a fad that is going to pass...

I can't wait until Flash passes.
 
I can't wait until Flash passes.

Agreed. I have been hoping for the death of flash for years, before the whole iPad debacle kicked off. Flash needs to DIAF. The world will be a better place without it.
 
If you don't mind static, silent and inconsistent webpages, sure.

But if you want multimedia content, good presentation and complex functions, flash is here to stay.

BTW, i make flash and html5 versions of the same sites, so i really can directly compare the two.
 
Flash isn't so bad.. I think just the majority of people who develop stuff in flash are fucking retarded
 
If you don't mind static, silent and inconsistent webpages, sure.

But if you want multimedia content, good presentation and complex functions, flash is here to stay.

BTW, i make flash and html5 versions of the same sites, so i really can directly compare the two.

Actually I prefer static, silent webpages.
 
But if you want multimedia content, good presentation and complex functions, flash is here to stay.

I think people that clamor for Flash's demise are delusional. They act as though HTML 5 has been around for over a decade like Flash. The amount of content and in Flash beyond video is staggering and for the most part Flash has done its job very well, thus why its everywhere.

If you want Flash to die cool, just pony up the bazillion dollars to migrate everything beyond video to something else more suitable to your liking. In the meantime the rest of the world will continue to use Flash heavily though in time I do imagine that more and more developers will use HTML 5 where it makes sense but even HTML 5 can't completely replace Flash.
 
Websites hardly have to be static and silent, thats a ridculous statement. Its certainly easier to make multimedia websites with flash, but its hardly impossible without it. And the benefits are there. I appreciate that no manager will allow someone to spend more time to make something that runs on less machines, and thats clearly the problem, but flash isnt a neccesity.
 
But if you want multimedia content, good presentation and complex functions, flash is here to stay.
I do that with HTML5 and JavaScript (working directly with the DOM). No Flash required.
 
HTML5 will be the eventual death of Flash.

There ain't much you can't do in HTML5 that Flash can do - only talking about the features people actually use.

Also imagine how much less internet bandwidth would be wasted on ads if they were static...
 
Websites hardly have to be static and silent, thats a ridculous statement. Its certainly easier to make multimedia websites with flash, but its hardly impossible without it. And the benefits are there. I appreciate that no manager will allow someone to spend more time to make something that runs on less machines, and thats clearly the problem, but flash isnt a neccesity.

Note my statement that i use both. While individual functions in flash can be done in HTML5, using three different languages (CSS, HTML, Javascript) adds to the work and overly complicates the site. Add to the fact that each browser has their own way of interpreting the site, adds to the inconsistency between browsers, to the point that you're adding code paths for each of them.

I can replicate a basic flash site as HTML5 in one browser (Minus the effects), but it's pretty much guaranteed to be broken if i load it in another.
 
Also imagine how much less internet bandwidth would be wasted on ads if they were static...

Dude, you really think the ad companies don't take size into account? In fact, the reason they prefer flash was because of how much content they can squeeze into the same size as a JPG! They pay for their servers bandwidth too you know.

I also made flash ads, and the ceiling we were allowed was 42kb, not one byte more. No matter how complicated the ad, all the animations, all the assets, everything has to fit in 42kb (And without losing detail or color bleeding) If it's just a basic ad, we can lower that down to 10kb. There are advantages to using vectors vs bitmaps. And if you want to lower the size even further, you can do everything procedurally.

See that tigerdirect ad up top? You only need the bitmap for the peripherals, everything else can be done with vectors, gradients and shadow effects.
 
If it takes more time and money to do certain things without Flash than with it might as well be.
The issue I see with Flash, besides my general stance that the web should be architected with open platforms and not reliant on browser proprietary plug-ins to deliver content, is that when you take the Flash-only approach, you're effectively putting up a sign that says "you must have this many security vulnerabilities to ride". Telling users that they need to subscribe to Adobe's glacial pace of security patches for what are typically severe vulnerabilities in order to access your content isn't good.

Let users make the choice, even if the choice isn't directly presented to them. Depending on what you're doing, this approach is not always that complex. Is it more effort? Typically. But sometimes we opt to take the long road because it's what's better for users.

See that tigerdirect ad up top? You only need the bitmap for the peripherals, everything else can be done with vectors, gradients and shadow effects.
This is why we have the canvas element and, to some extent, SVG.
 
http://codetest.f*r*e*e*h*o*s*t*i*a.com/html/td.html

Yes, i actually redid that tigerdirect ad in flash. And it wasn't much trouble. Took me about a half hour. That's actually slow, usually something like that takes about 10-15minutes each if you average the different size variations.

And we did that eight hours a day, in several languages. Everything from static ads, to expanding ads (That 728x90 banner expands to 728x240 when you rollover), to a preview clip of that weeks soap opera on your local cable.

And before you comment, there's a limit to how much CPU and bandwidth we're allowed to use. No more than 42kb per ad and when a banner finishes displaying, especially with procedurally generated content, the CPU usage drops to Zero (or near zero if you include animated ads). Video streaming on ads are also set to only use bandwidth when you hit the play button.

If you want the finer points of flash programming, i'd recommend working for an ad company, you'll learn all the little details and tricks to fit an entire mini game in there, balancing bandwidth and CPU usage, and do everything fast.

And please, don't associate the pros with the noobs. I have this really big urge to smack him on the head whenever i see someone showing off his nice *2MEGABYTE* spinning flash logo. :mad:

Let users make the choice, even if the choice isn't directly presented to them. Depending on what you're doing, this approach is not always that complex. Is it more effort? Typically. But sometimes we opt to take the long road because it's what's better for users.

Unfortunately, in the real world, you have time and budget constraints. It will take four times as long, minimum, to make an html5 of a complex media site, and the additional delays for browser compatibility testing, cpu balancing, etc. for each browser will take a lot of your time. Every revision they request, has to be retested for every browser and there's a chance that the one they want will break your code and require you to rebuild it. Re-programming for revisions is especially difficult if you're using codepaths to maintain individual browser compatibility. In the time i've been coding for both, i spend less time rebuilding and testing flash code.

Flash = There's a button that needs to look like this, color like this, animate like this... done... oh, you want to change the color of this menu?... done... make it two pixels taller?... done... Change the font on the button?... done.

HTML = Back and forth between Photoshop and your editor, and putting it in your webpage requires three different languages (CSS, HTML, Javascript). And if you try anything too elaborate, it'll break depending on the browser.

When i make dual sites, i make the flash version first, since it's easier to revise, and hope they don't make any more revisions when i make the HTML one.

This is why we have the canvas element and, to some extent, SVG.

Canvas is not consistent across browsers unfortunately, or atleast, the last time i used it, nor will you be able to mass produce ads on that like we do on flash, nor will your fonts, text, and spacing be stable. CSS does help somewhat, but not enough to make it viable.
 
Back
Top