6 ms·
Adobe is seriously doing it all wrong. They have to open-source the Flash Player and everything around it now. They can keep the IDE proprietary if that floats
by cookiecaper 16y ago
Adobe is seriously doing it all wrong. They have to open-source the Flash Player and everything around it now. They can keep the IDE proprietary if that floats their boat, it's just a premium authoring tool, but the only way to save Flash is to open-source like NOW. HTML5 is still young enough that an open Flash Player and standard and protocol (RTMP) would effectively kill it.
Open-sourcing would open so many doors. Apple could modify Flash until it worked on iOS properly, Google could modify until it worked on Android. The reason this hasn't happened so far is that Adobe is a bottleneck nobody wants to deal with; they just consider basically impossible to get Flash Player on mobile because Adobe doesn't have the structure or the talent to do it correctly, and there is no other option except to let Adobe do it. An open Flash would open many doors, awesome adaptations, deployments, and uses that we can't yet think up would come out of it, and all the while Adobe would keep selling its IDE (probably selling more, actually, because Flash will then do cool stuff that everyone wants).
I don't know why they don't do this. Flash Player is already basically free, all of the money from Flash comes from the IDE Adobe sells. Keep the IDE locked up if you want, Adobe, but every second you keep the Player locked up you are killing Flash that much more, and when nobody uses Flash nobody is going to buy your IDE.
I know there are free software Flash players out there, but it's not the same. It's like saying nobody needs cooperation from nvidia because of nouveau. While a noble effort with meaningful results, vendor support still gets you much, much farther ahead.
If Adobe knows what's good for them they will be opening the Flash Player as quickly as they possibly can. They are going to be very sorry that they didn't. They probably will eventually take this route as a last-ditch effort when Flash content has dipped like 80% and been replaced by HTML5/JS, but that will be too late. This is Adobe's last chance, they must open it now if they expect any kind of future from it.
Flash is too big for Adobe alone, and if they don't want the whole thing to crash and burn totally and have that revenue dry up, they need to open ASAP. This should be the number one priority at Adobe.
- xtacy 16y agoCould an alternate approach be to take the route that Dalvik did? There's also a research paper about having a remote proxy to deal with Flash on mobile devices; it's something like a VNC viewer, but for Flash. That wouldn't violate any patents now, would it? http://www.cs.washington.edu/homes/gribble/papers/sys169-moshchuk.pdf http://www.cs.washington.edu/homes/gribble/papers/sys169-mos...
- borisk 16y agoFlash player gives Adobe a lot of power and keeps their not so good dev/design tooos safe from competition. From what I've seen the current strategy is to try to add features not available in HTML5, like P2P. That would allow youtube and company to roll out torrent-based players and save hugely on bandwidth.
- rbranson 16y agoI doubt P2P could be used reliably for video streaming. There's a quality of service component of video streaming that P2P solutions can't currently provide effectively in the context of embedded web video streaming. Besides, YouTube probably doesn't cost very much bandwidth-wise. Google has dozens of datacenters placed at or near key peering locations where they can negotiate very low or zero tariff interconnects with major IP networks. At work on a Time-Warner fiber connection, I am 2 hops from Google's network.
- wmf 16y agoOctoshape has had some successful deployments recently, although I suspect they only offload some of the bandwidth from the CDN. Also, Google isn't the only game in town; P2P offers the promise that you could cheaply deliver video to large audiences without having to pay Akamai or give up control to Google.
- illumin8 16y agoAgreed. The main reason why it wouldn't work is that existing broadband deployments are not designed for P2P. Your neighborhood might have a gigabit of downstream bandwidth on fiber from the cable company but the upstream is limited to something like 100 megabits for the entire neighborhood. It sounds nice in theory to cut bandwidth costs, but somehow I don't think the cable companies are going to be too happy with you sharing their limited upstream with your traffic. They'd much rather deliver lots of streaming content downstream, which is what their network is designed for in the first place.
- cookiecaper 16y ago
- daleharvey 16y agoits already far far too late for adobe, if they had open sourced 10 years ago, there wouldnt be a html5 video and canvas, flash would be the standard. open sourcing it now will help them stay relevant for longer but it will be a band aid, proprietary tools will be replaced by web standards on the internet thats more obvious now than it ever was. flash can innovate by raising the limit on what you can do, but there is a roof on that functionality the gap between it and where web standards are now is getting smaller and smaller.
- nanairo 16y agoI may be wrong, but I think Adobe 10 years ago was pushing for things like html5 video and canvas... because Flash was Macromedia's. It was a case of: the enemy of my enemy is my friend. (They were also one of the first big companies to push SVG from what I remember).
- daleharvey 16y agoheh not the first time I have made that mistake, when I say "they" I mean macromedia / whoever happened to be in charge of flash at the time of whatever incidence we are talking about.
- nanairo 16y agoBut I am not sure Flash was really comparable to what it is today back in the days of Macromedia. Did we have Youtube and company back then? My gut feeling is that Adobe there went from "the enemy of my enemy is my friend" to "hey, wait a minute: we could actually BUY it, and CONTROL it". Adobe bought Macromedia and suddenly Flash was great and amazing and they integrated it with the rest of the their portfolio. The question I am trying to put is: back in the days of Macromedia, do you think they would have clanged on Flash on mobile like they life depended on it? (this is not a rhetorical question, btw, I am really wondering: I didn't follow Adobe and Macromedia much in those days)
- daleharvey 16y ago
- nanairo 16y agoNot sure how much I agree. There seems to be an intermediate step in your reasoning that goes something like: "FOSS fixes everything". Sometimes it's true, sometimes it isn't. Why would Apple spend a lot of money and man-hours to port Flash for the iOS? Is not like the lack of Flash seems to be bothering anyone much (in terms of units sold). And Google actually did help Adobe to port Flash to Android, and it seems (from this article) that the job is not that good. Maybe Flash would need a massive internal change for it to reach the speed it deserves: sometimes it's better to simply start from scratch. Also it's still not obvious to me that Flash is the right technology for the mobile/touch-screen Web.
- Legion 16y agoI don't think the point is "FOSS fixes everything". I think the point in this case is, "go FOSS and you've got a shot. Stick with the status quo and your death is assured". I think the poster has a point. Maintaining a monopoly on the tools to create media in a certain format isn't going to amount to much if everyone ditches the format. Flash is already becoming a four-letter word. I don't see what Adobe can do on their own to change the direction Flash is headed. Going open would give Flash a shot at survival.
- nanairo 16y agoThat I agree.
- sethg 16y agoOpen-sourcing would open so many doors. Apple could modify Flash until it worked on iOS properly, Google could modify until it worked on Android. If Adobe has spent years growing the Flash player code on the principle “make it work well on Windows, and then hack it as necessary to make it work tolerably on other platforms”, then even after it is open-sourced, developing a Linux- or iOS-compatible Flash player may be more than just a Simple Matter Of Programming. Remember the long gap between Netscape open-sourcing its browser and Mozilla becoming a usable platform.
- commandar 16y ago>Remember the long gap between Netscape open-sourcing its browser and Mozilla becoming a usable platform. Not sure this is the best comparison. Netscape open sourced Communicator 4.0, yes, but what we know as Mozilla was a total rewrite after they decided to scrap 5.0. EDIT: Unless your point is that the Flash codebase may be similarly bloated. :)
- sethg 16y agoUnless your point is that the Flash codebase may be similarly bloated. Yeah, that was kind of what I had in mind.
- cookiecaper 16y agoIt's not necessarily that it'd be a simple matter or wouldn't require major architectural changes or whatever, it's just that it'd be much, much more _possible_. And I fully believe that there are many, many improvements that could be made that are just a simple matter of programming, even if running on mobile devices isn't among them. Not to mention a fully open-source Flash Player would make a great reference for aspiring free Flash players like Lightspark. If Adobe stays on the path it's on, HTML5 will continue to mature faster and faster as the desperation for a legit Flash replacement grows. Adobe could stay in the loop without having to reinvent the wheel and reacquire a distrusting and skeptical customer base if they would just open Flash while they're ahead; people would continue to buy the Flash IDE in droves, but when HTML5 takes over, that installed base is not likely to wait on Adobe and they'll move on to a competing IDE. I believe that HTML5 is still young enough that it could be basically deposed by a truly open Flash.
- jcl 16y agoYou are assuming that the only thing preventing Flash from working on mobile is that it hasn't been "optimized" enough -- that opening the source to Google and Apple will unlock performance otherwise unattainable by Adobe. But suppose Adobe's programmers are not completely incompetent? Perhaps Flash's execution model is genuinely unable to be optimized further. Or perhaps most Flash content in the wild runs at the limits of desktop performance, and that compositing vector graphics and text on top of video while running multiple VMs embedded in a webpage is just too much for a memory- and CPU-constrained device. In that case, open-sourcing Flash would have little effect. Even if we had an optimal mobile Flash player, we'd still need everyone to rewrite their Flash movies to run well on it. That's why HTML5 has the advantage here: HTML5 content is being freshly written and tested for mobile platforms.
- bruceboughton 16y agoRubbish! Most moderately advanced HTML5 demos run hideously, if at all, on mobile hardware. The difference will be if HTML5 can replace 80% of Flash uses in a performant manner. The video tag makes up a huge block of that 80%. The other 20% will always run like a dog on mobile hardware, no matter the technology.
- ItarPeyo 16y agoAlways?! Even on mobile hardware that will come in 5-10 years?
- illumin8 16y agoHave you watched the Apple HTML5 demos on an iPad? It's actually revolutionary to see what they can do with the limited hardware. Being able to touch and drag a 3d model around at 30 fps without stuttering? I can't even do that on a lot of PCs with Flash.
- elblanco 16y agoHere ya go. Give this a try and let us know how it runs. http://xplsv.com/prods/demos/xplsv_orsotheysay/ http://xplsv.com/prods/demos/xplsv_orsotheysay/
- Detrus 16y agoWhy would mobile OS companies devote resources to improving Flash when they're already working on Canvas, WebGL etc... They'll still have to make Canvas as fast as they make Flash. Flash was supposed to be canvas, but Macromedia/Adobe chose not to join the standards process, so browser makers just rolled their own. After all the effort on canvas, they'll just drop it all and replace it with Flash or work on both? It just seems impractical. I don't think Google is interested in Flash beyond integrating it with NativeClient. Maybe they could improve it, they may have more engineering talent, but these are ultimately strategic decisions, not technical ones. As far as other companies besides Google, MS and Apple, why would they commit themselves to Flash when Canvas is already open source, can be improved, etc..? I think Adobe is screwed with their current plugin either way. Their path of piling on features, ensuring perfect integration with authoring tools seems more reasonable. That's where their focus should be. They won't lose much if they lose the plugin, it's not a big deal if they could do the same things the plugin does through JS eventually. The plugin is just an insurance policy and if NativeClient becomes a standard they won't have to worry about penetration when they come up with a better plugin eventually.
- illumin8 16y agoThis is a great idea, but I think Adobe might not want to open source it because they have sold Flash to content companies as a way to lock their streaming content down with DRM. Opening the specs and allowing anyone to play DRM content would let the "evil pirates" get their hands on all that sweet, sweet booty. By booty I mean streaming episodes of Hulu...
- andybak 16y agoAre you saying that an it's impossible technically to have an open source DRM format? I'm not sure that follows, does it?
- cookiecaper 16y agoThe benefit from preventing the death of the Flash format is greater than the benefit from not pissing media companies off, first of all. Secondly, as stated, the DRM components should be possible to open if they're properly implemented. There are many open implementations of PGP et al that are open and PGP hasn't lost anything from that. If their DRM is hacky/not good, then yes, open-sourcing would probably be bad for that component. But DRM is a rather small part of the overall Flash ecosystem, and if they don't get the Player completely open, they are going to lose meaningful revenue from Flash completely relatively soon.
- joehn 16y agoadobe also sells access to the premium codecs in flash. youtube pays a nice chunk of change for it
- jasongullickson 16y agoI think this goes 180 degrees in the wrong direction. Based on what I've heard, the real reason anyone uses flash anymore is because of the authoring tools, not the runtime. Instead of open-sourcing the flash player, build a development/authoring tool for HTML5 of equal or higher quality than the Adobe tools and open-source that...then watch this debate become irrelevant a year from now...
- loewenskind 16y agoExactly right, you should be higher on this page. :)
- cookiecaper 16y agoI agree that an equivalent IDE for HTML5 would be huge for HTML5. I don't think HTML5 has a chance of mainstream adoption until it gets one and I hope it does get one. I don't necessarily want Flash to win out, or think HTML5 should suffer, I'm just saying that the only way Adobe will keep Flash alive is open-source.
- jasongullickson 16y agoGotcha, and I agree, if the goal is to keep Flash alive, it's going to need to find some compelling way to remain competitive, and fast.
- c1sc0 16y agoMaybe I'm wrong on this, but I always thought that Adobe can't open source flash because of intellectual property conflicts. Or is that just an excuse?