Did Adobe fall in the trap, or what?

Question

I wonder WHY did Adobe let Google make their own crappy Flash player version (Pepper) in Chrome? The performance in all applications is inferior.  It sucks in displaying textfields, it sucks in displaying all other graphical display objects, it sucks in stage3D too -the motion is never as smooth and full of hiccups vs the original Adobe Flash player. I have also unresolved issues with the ExternalInterface etc. And they did all that for what, security? Google cared so much about security that they made their own version? How about all the other NPAPI plugins then? Those are OK?
Now if I tell the users to disable the embedded PPAPI plugin and install the Adobe Flash Player if they want to view my website (as it is totally incompatible), should I also warn them that this might ...compromise their security? So Google is the king of security and no one should talk against them? Who's the sucker I wonder here...

Answer 1

You know, Chrome USED to be better and pepper-plugin used to be smother, then they did something to completely destroy WebGL.   I was at shadertoy.com playing with all kinds of shaders, and they used to run at 30-60fps, then after some updates, I can no longer achieve even 1fps.  Something has gone terribly wrong with Chrome, or WebGL, or some driver, or some update to Windows 7.  Things that used to function well, no longer function at all.  Probably some underhanded attempt to cripple competition, even if it's an older version of their own operating system (it will backfire, of course). Anyway, I no longer recommend Chrome to users or schools who use our software.  The NS plugin (NetScape plugin architecture) is definitely faster and smoother than the pepper plug-in.  Who knows what's going on.  I've been back to using Firefox since version 29.  Far better rendering (no stretching/tearing/squashing of the interface when resizing the browser window), far better tab support, doesn't force tabs into the title bar, tab groups feature is incredible, less snooping/syncing to Google, so so so much better.  Just beware of having too many tabs open as it can overwhelm the session manager.
Flash still wipes the floor with HTML in every imaginable aspect as a Web Application platform; it's sad people don't know how to use it properly or don't have the proper UI framework to leverage its power (FLEX is NOT it, IMO, sorry).  The stuff I'm working with here in Flash blows away anything I've seen in web apps/desktop apps/mobile apps and even console games, and still runs at nearly 60fps.  It's layout capabilities put HTML to shame.  Anyway, it is very easy to drop the frame rate (such as by having an unbounded trace log), but it's also possible to keep memory in check and keep an app running smoothly in the browser indefinitely, even idling at 0% CPU; I've had mine running literally over the weekend (Friday to Monday) with no slowdown, all while maintaining an active websocket connection.