As someone who programs in ActionScript very often and makes heavy use out of RTMP, I'm very well aware of Flash's shortcomings and how quickly they would be fixed if it were more open. However, I really wish discussions like this weren't full of so much empty talk. If you don't like Flash, don't use it. Uninstall the Flash player and leave it all behind. Fact is, they have succeeded in getting a proprietary and comm…
Official reasons why Adobe doesn't open-source Flash
51–60 of 67 posts
Re: Official reasons why Adobe doesn't open-source Flash
#52What are peoples views here on using Flash for rich internet applications? In particular, what do you think are the benefits of using Flash/Flex? It seems to me that development for prototyping and proof of concept is cheaper and quicker in Flash/Flex and is still usable by a massive portion of internet users, even if it will not be in the future.
Re: Official reasons why Adobe doesn't open-source Flash
#53Earlier quoted context omitted.
What's with the group downvotes, folks? I stopped responding to this guy because his points are worthless. I'd rather the space on this page was used up by intelligent discussion rather than needless debate over a concept that is obvious to anyone who actually does any kind of ambiguous, difficult work (e.g. running a start-up, being a consultant, and generally being anything more than an employee who takes orders).…
It doesn't surprise me you were a management consultant. You're getting downvotes for repeating simplistic abstracts, without suggesting anything close to a reasonable course of action. "How do we fix this problem?" "Well, all problems can be fixed by fixing the problem." "Ok, so how do we do that?" "Simple, fix the problem." "Right."
Here are a few possible solutions, though, off the top of my head right now - I'm sure someone closer to the problem could find more, better potential solutions:
1) Release the player code without the codecs.
2) Obtain a special license from the people that own H.264 to be allowed to release the source code.
3) Get some kind of agreement that the owners of H.264 won't sue Adobe and release the source code.
4) Do so without getting the agreement - maybe they won't sue.
5) Transmit ownership of the code to a different legal entity and release the code via that entity.
6) Slowly migrate to a new codec that can be released (e.g. Ogg).
7) Release the code with Ogg support without the H.264 part.
8) Buy the code patent.
9) Start a public relations campaign to convince the owners to open up H.264 for everyone.
10) Start a public relations campaign to convince the courts to overturn H.264 (say, on grounds that it harms the public good).
That's just off the top of my head. Yes, they all have problems, but they're all starting points - and there's no evidence that Adobe explored any of those or any others. If you can't think of twice as many potential solutions, your brain is effectively the size of a pea when it comes to creative problem-solving.
And if "management-speak" language stops you from understanding a good point, you're a fucking retard.
Downvote away.
Re: Official reasons why Adobe doesn't open-source Flash
#54Earlier quoted context omitted.
I think Java developers everywhere were happy that Sun opened up Java, but does anyone think it was a good business decision?
Why not? The JRE was a free download for end users anyway, and open-sourcing it removed a large source of bad press. If Java was open-sourced earlier, it might have seen more adoption by hackers, and innovation. Now, it's an "enterprise" language, which basically means it has entered the "legacy" stage of its lifetime, and will go the way of COBOL in under 10 years.
Re: Official reasons why Adobe doesn't open-source Flash
#55Earlier quoted context omitted.
It doesn't surprise me you were a management consultant. You're getting downvotes for repeating simplistic abstracts, without suggesting anything close to a reasonable course of action. "How do we fix this problem?" "Well, all problems can be fixed by fixing the problem." "Ok, so how do we do that?" "Simple, fix the problem." "Right."
Ultimately, every solution I propose will have issues. This is why I did not outline a specific solution. Because they're all stupid until one of them becomes the right one because of specific circumstances, people, etc. That is the nature of difficult problem-solving. If it was easy, people like you might be able to do it. Here are a few possible solutions, though, off the top of my head right now - I'm sure someone…
Of them all, #1 (the "plug your codec here") is the easiest. h.264 is not even protected in the whole world, so, those who can will enjoy it and those who don't will, perhaps, lobby their representatives.
#6 is also nice because with sufficient funding, Ogg can become a decent option and everyone would benefit.
Re: Official reasons why Adobe doesn't open-source Flash
#56Earlier quoted context omitted.
There is only "one stuff" they can do to make the problem go away (in your words "resolving licensing issues"), which is, they can buy H.264 and give it away for free (open source it), which is impossible without making themselves bankrupt. The other stuff that I can think of is that they can use Ogg Theora, which is hardly a solution, considering (IMO) it is an inferior codec.
they can buy H.264 and give it away for free (open source it), which is impossible without making themselves bankrupt. As the discussion around H.264/Theora etc has heated up I've started wondering about this. There are now at least 3 rather large players with relatively deep pockets that all have licensed h.264 for products they essentially give away. So what if Google, Apple, and Adobe all pooled together and purch…
That's half a trillion dollars in a year, and that's not even counting revenue they get from MPEG-4 or the audio codecs.
Re: Official reasons why Adobe doesn't open-source Flash
#57Earlier quoted context omitted.
The Flash (SWF) format is open (or, so Adobe says)... But their software isn't.
Their flash specification is not complete. The blend modes are not specified there. Two of those are strange, flash specific ones that you have to reverse engineer, but the others are similar to PDF.
"Adobe seriously considers all feedback to the SWF file format specification. E-mail any unclear or potentially erroneous information within the specification to Adobe at flashformat@adobe.com."
Has already someone asked for clarification of these details? I ask because the answer would state a lot about Adobe's relation to open specifications.
Re: Official reasons why Adobe doesn't open-source Flash
#58Earlier quoted context omitted.
Why not? The JRE was a free download for end users anyway, and open-sourcing it removed a large source of bad press. If Java was open-sourced earlier, it might have seen more adoption by hackers, and innovation. Now, it's an "enterprise" language, which basically means it has entered the "legacy" stage of its lifetime, and will go the way of COBOL in under 10 years.
Well... COBOL and Fortran have been going the dinossaur way for far more than 10 years and show no sign of disappearing...
Re: Official reasons why Adobe doesn't open-source Flash
#59"Official reasons" ??? The subhead of this blog states: Please note that opinions expressed within are mine and do not necessarily reflect those of Adobe.
The person writing it is Director of Open Source and Standards (OSS) at Adobe, its an official comment.
Re: Official reasons why Adobe doesn't open-source Flash
#60From Wikipedia: On 20 January 2009 Adobe announced it will publish the RTMP specification. On 21 May 2009 Adobe filed a DMCA removal request on a Sourceforge-hosted implementation of the protocol. And now we are about to believe that: The Flash file format (SWF) specifications are open and unrestricted, so any company - even Apple - can build their own Flash Player if they want. Also freely available are related spec…
Most people that are using RTMP are using it to serve static files that they want to make harder to copy than downloading an FLV file. As I recall, the problem with rtmpdump wasn't that it implemented RTMP, but that it included ways to bypass the "security measures" that are built-in to RTMP. It was able to spoof all of the parameters that FMS uses to determine whether or not it should serve a stream, and would save…