Lately, Adobe representatives and Flash fan boys alike became more vocal than usual about the alleged openness of Flash. This is probably spurred by the proposed feature set of HTML5, as well as the decisions of a certain vendor to ban Flash from some of their products, both potentially being threats to Adobe and the Flash Platform.<\/p>\n
I originally posted the following article as comment to an article by Serge Jespers, “Flash is as open as HTML5<\/a>“. Serge is an Adobe Platform Evangelist. I thought this comment deserves its own post, so here we go.<\/p>\n No, it isn\u00e2\u20ac\u2122t.<\/p>\n And it is beyond me why so many independent Flash Platform developers fail to see it. I completely understand of course why Adobe evangelists downplay it.<\/p>\n It is irrelevant for the so called \u00e2\u20ac\u0153open web\u00e2\u20ac\u009d whether the Flash Player is going to get open sourced or not. That\u00e2\u20ac\u2122s not the point. Microsoft won\u00e2\u20ac\u2122t open source their browser, Opera won\u00e2\u20ac\u2122t open source their browser, etc.<\/p>\n Relevant is who decides about the development of the data format that a runtime consumes, and the APIs a runtime provides to access that data. In the Flash world that\u00e2\u20ac\u2122s SWF and the Flash Player APIs, both controlled by a single vendor: Adobe. In the HTML world that\u00e2\u20ac\u2122s HTML and DOM, controlled by many vendors, including you and me, via standards bodies.<\/p>\n Adobe neither provides formal means for other companies and individuals to participate in the development of SWF and Flash Player APIs, nor does it provide detailed work-in-progress specs to the general public for discussion. This effectively rules out the possibility for third parties to provide alternative runtimes. The runtime and its specs are released to the public at the same time.<\/p>\n This is the exact opposite of \u00e2\u20ac\u0153open\u00e2\u20ac\u009d.<\/p>\n To make matters worse, the specs released by Adobe are incomplete and buggy (e.g. the SWF spec fails to explain how exactly shapes are supposed to be rendered and leaves out information on codecs, the ABC spec is plain wrong on some things) and generally infested with patented technologies.<\/p>\n Of course i understand why it is how it is (and likely always will be). If Adobe were to become truly open and put the development of SWF etc in the hands of standards bodies, the 1.5 year release cycle would become a 10+ years release cycle. Innovation would slow down significantly. I as a Flash Platform developer wouldn\u00e2\u20ac\u2122t want that to happen.<\/p>\n However, sorry to say that, but to tout \u00e2\u20ac\u0153Flash is as open as HTML5\u00e2\u20ac\u00b3 is pure FUD.<\/p><\/blockquote>\n","protected":false},"excerpt":{"rendered":" Lately, Adobe representatives and Flash fan boys alike became more vocal than usual about the alleged openness of Flash. This is probably spurred by the proposed feature set of HTML5, as well as the decisions of a certain vendor to … Continue reading