Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
well i can't say that i'm surprised that Flash is going away from mobile devices. Adobe never seemed to put much effort into making it work once they realized that Apple would never support it. its an anachronistic piece of technology that will hopefully be replaced completely in the near future.
 
With Video Streaming, you're saying:

Bob (Netflix) wants to send Alice a movie, but only wants her to do a few things with it.

It's a completely different type of scenario. With TLS, the untrusted party is some stranger in the middle up to no good. With Video, the customer is the untrusted party.

This is ultimately the downfall of most DRM schemes -

DRM is based on encryption most of the time. To decrypt the video, you'll need the proper keys. To get the proper keys... yep you guessed it, you're either going to have to hack them (DeCSS, AACS keys that got cracked) or conform to the standard and implement properly with a proper license.

You can't just hop one day and decide to write a client that "ignores" DRM protection on media and hopes it works because you comment off the DecryptStreamUsingKey(); function call. ;)
 
In what way is Flash video "protected?" There's really no such thing. The video content is there regardless of the delivery method. Flash, just like anything else, obfuscates the location of that content, but then, you can do that with any delivery method, including HTML5.

He's talking about the DRM capabilities built into Flash Media Server :

http://www.adobe.com/devnet/flashmediaserver/articles/digital_media_protection.html

HTML5 offers no alternative for this. Forget the fact that it was cracked ages ago, no legit implementation of Flash exists that can read these streams outside of Adobe's own runtime.

Gnash have not implemented it for good reasons : Adobe doesn't document it in the Flash specification, and all the reverse engineering is less than legit.
 
DRM is based on encryption most of the time. To decrypt the video, you'll need the proper keys. To get the proper keys... yep you guessed it, you're either going to have to hack them (DeCSS, AACS keys that got cracked) or conform to the standard and implement properly with a proper license.

That's the point though, you can't have an open DRM system if it has to have a licence!

At the moment, anyone can write a web browser. You don't need anyone's permission, you don't need to conform to any rules imposed by a company etc.

DRM is simply incompatible with open standards.

If it's not an open standard, it's not really any different from Flash - it's just made by someone else. What you suggest is essentially how Flash works now.
 
andriod is doom. their only selling point is now gone

I won't say it is doomed. Android is not without its own strengths; problem is, how do you even start marketing the idea of widgets or rootkits to the masses?

Adobe Flash Player for mobile was completely useless from the very beginning since no Flash content was optimized for mobile. Yes, you could load Flash content in the browser but it was far from usable...

Isn't that the whole point? Flash sucked then (for whatever reason). If Apple had just included an option to toggle off flash, we would never see any progress, because people would just continue to create crappy flash content, with the logic that if you wanted to view it, simply enable flash.

By banning flash altogether (and coupled with the fact that the ipad was popular enough that people evidently didn't mind this limitation), developers were forced to seek other alternatives (either dropping flash or releasing custom apps). And I reiterate my belief that in the end, we are better off for it.

Yeah, so sites like BBC suffer. But they cannot say they didn't see this coming a mile away. Even the blindest of fools would have seen the ipad's popularity coming a mile away, and optimise to take advantage of it. Anyways, I am using rss feeds to get my news, as I find their sites take too long on my ipad and have a tendency to freeze the browser. :confused:
 
I've never heard of a job title called "web guy" but the job title "front-end developer" is very frequent.
Using Perl, the read-only language, for rendering web pages sounds like a nightmare. Who did that to you?

Hum, you do understand that the LAMP stack once stood for Linux Apache MySQL Perl right ?

Perl was very big before PHP (and frankly, is much better at doing web stuff still today). CGI.pm, HTML::Template, Catalyst, you can go as low-leve or high level as you want.

I wrote a ton of Perl web stuff in the late 90s/early 00s.
 
I won't say it is doomed. Android is not without its own strengths; problem is, how do you even start marketing the idea of widgets or rootkits to the masses?

in a way, the marketer have to think of new ways to market it.
as an OS, andriod is still usable.
 
That's the point though, you can't have an open DRM system if it has to have a licence!

Sure you can. There's a difference between documenting a protocol and documentation the keys. The keys don't have to be documented, only the protocol (exchange of information) and the key format. Once you have that, you license the actual keys. That's how every encrypted protocol works in the open standards world.

At the moment, anyone can write a web browser. You don't need anyone's permission, you don't need to conform to any rules imposed by a company etc.

The W3C disagrees. You need to conform to HTTP standards, HTML, DOM, CSS standards, you need to implement a number of ratified standards or else you're not a Web browser.

If it's not an open standard, it's not really any different from Flash - it's just made by someone else. What you suggest is essentially how Flash works now.

I'm not suggesting anything. Simply saying that DRM can be an open standard.
 
Sure you can. There's a difference between documenting a protocol and documentation the keys. The keys don't have to be documented, only the protocol (exchange of information) and the key format. Once you have that, you license the actual keys. That's how every encrypted protocol works in the open standards world.

You're not looking at it correctly. Key exchange is not the problem.

Key exchange is a way for TWO parties to exchange keys with each other over a potentially insecure network so that they can communicate securely with each other.

It is not a way for one party to restrict how the other can use content.

I'll repeat. If we have an open DRM standard that anyone can implement, what stops me doing this:

Browser: I want video B please
Server: Video B is encrypted with this key and is only to be viewed once
Browser: Ok, I'll only let them play it once
Browser: Hehe, I'll just save this in an unencrypted form.

If there's anything that prevents you doing that, then it's not open.

All of the current proposals (including the major one from Netflix, Google and Microsoft) effectively block support for open-source browsers for this reason.

Others use a form of closed-source plugin.

The W3C disagrees. You need to conform to HTTP standards, HTML, DOM, CSS standards, you need to implement a number of ratified standards or else you're not a Web browser

All of these standards are openly available and do not require the developer of a browser to sign up to anything or restrict how their browser works.

I think you'll find that the W3C agrees with me entirely on this matter. They do not see how DRM can ever become part of HTML5 video.
 
People will have the .apk downloaded and readily available. Fortunately.

Adobe is making a critical error. I see no viable reason to yank it. If they want to stop updates that's one thing. But the reality for now and the future is, Flash gives the added security for content providers that HTML5 cannot. Until there is a contender in that arena, it'll continue to be an issue.

All Adobe is really doing is creating a market for Microsoft Surface (which would then be the only tablet capable of full Flash).
 
64-bit Linux users will attest to the fact that the software was always bloated. That's why it took them so long to port it - apparently lots of it only really worked on Windows, Intel 32-bit systems.

Anyway, good to hear it's dead. Now I want to see companies serving their HTML5-enabled sites to desktop users, too.

As an ex-linux user, I always found it absolutely hilarious that linux could support 128 CPU's, but couldn't deliver full screen lag-free flash. :D

Those of you who never really got how bad flash was, or thought you had it bad on the Mac OS side... Well... enjoy the fresh baked perspective pie. ;)
 
http://www.apple.com/hotnews/thoughts-on-flash/

Symantec recently highlighted Flash for having one of the worst security records in 2009. We also know first hand that Flash is the number one reason Macs crash. We have been working with Adobe to fix these problems, but they have persisted for several years now. We don’t want to reduce the reliability and security of our iPhones, iPods and iPads by adding Flash.

Although Flash has recently added support for H.264, the video on almost all Flash websites currently requires an older generation decoder that is not implemented in mobile chips and must be run in software. The difference is striking: on an iPhone, for example, H.264 videos play for up to 10 hours, while videos decoded in software play for less than 5 hours before the battery is fully drained.

Flash was designed for PCs using mice, not for touch screens using fingers. For example, many Flash websites rely on “rollovers”, which pop up menus or other elements when the mouse arrow hovers over a specific spot. Apple’s revolutionary multi-touch interface doesn’t use a mouse, and there is no concept of a rollover. Most Flash websites will need to be rewritten to support touch-based devices. If developers need to rewrite their Flash websites, why not use modern technologies like HTML5, CSS and JavaScript?

Flash was created during the PC era – for PCs and mice. Flash is a successful business for Adobe, and we can understand why they want to push it beyond PCs. But the mobile era is about low power devices, touch interfaces and open web standards – all areas where Flash falls short.
 
Except 90% of Android users are still on 2.x, including many devices on sale now. :)

Generally the only devices on sale pre-3.0 now are:

- Unlicensed phones (e.g ones without the 'GAPPS' package)
- Discounted/Refurb phones (some silly manufacturers produced their Android handsets in huge numbers thinking it would be 'the one' that everyone wanted so now they have huge stockpiles of crappy old handsets.
- Own-brand handsets (for example in the UK T-Mobile and Orange have their own Android handset lines. They are cheap and under powered, and cant run flash in the first place.

Put it this way. If someone is using a phone on 2.x that's reasonably new, its highly unlikely that flash ever worked on it in the first place, so its still a mute point.

Given the huge leaps in hardware over the last 12 months, give it another 12 months and you'll see decent specced hardware in the budget droid phones.
 
Hum, you do understand that the LAMP stack once stood for Linux Apache MySQL Perl right ?

Perl was very big before PHP (and frankly, is much better at doing web stuff still today). CGI.pm, HTML::Template, Catalyst, you can go as low-leve or high level as you want.

I wrote a ton of Perl web stuff in the late 90s/early 00s.

Granted, that was before my time but it still sounds like a nightmare to work with, just as PHP IS a nightmare to work with today.
 
As a Flash Developer I can say this is good news. I have always disliked the flood of poor programming by sudo developers in Flash, this is one of the major reasons for issues with the Flash player, and welcome the hope that as Flash becomes an even smaller "niche" platform we begin to see fewer things developed in Flash, but much better quality for those things that are.

I for one will not miss it on mobile and have always thought it to be a bad idea in the first place.

Not to be a pedant but come on, 'pseudo'...

Flash (mobile) development however will migrate into Air based apps. Certainly it keeps it relevant on iOS, and regardless of what you might think of Flash (actionscript) developers, the fact that there are bloody THOUSANDS of them out there means that Flash isn't going to go softly into that dark night.

It will just reposition itself for the time being.

Oh yeah, and banners...
 
Not to be a pedant but come on, 'pseudo'...

Flash (mobile) development however will migrate into Air based apps. Certainly it keeps it relevant on iOS, and regardless of what you might think of Flash (actionscript) developers, the fact that there are bloody THOUSANDS of them out there means that Flash isn't going to go softly into that dark night.

It will just reposition itself for the time being.

Oh yeah, and banners...

Just shows you how biased and uneducated Apple fan boys are towards Flash.
 
I disagree with most here and find Flash to be very stable.

screen-shot-2012-06-19-at-121422.png
 
Ohh, I just love Flash. I mean here I was watching a video and the next thing I know Chrome gives a message saying that flash has become unresponsive and crashed.

Only flash can bring a top of the line computer to its knees while watching a simple video. They day that web developers stop saying "I'll make it in Flash" will be a great day for the web.
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.