Good bye Silverlight Road
-
neither of those are adobe flash which is still exclusively 32bit.
Yes, there was a NPAPI 64bit Linux flash, but it's at version 11.something still, as Adobe put it out there and then proceeded to give it 0 love, not even the occasional security patch as far as I know.
-
Yes, there was a NPAPI 64bit Linux flash, but it's at version 11.something still, as Adobe put it out there and then proceeded to give it 0 love, not even the occasional security patch as far as I know.
They still backport security stuff:
NOTE: Adobe Flash Player 11.2 will be the last version to target Linux as a supported platform. Adobe will continue to provide security backports to Flash Player 11.2 for Linux.
-
It would be great if C++ offered a replacement for printf family of functions but it doesn't.
There's always
boost::format.
-
Security fixes, but not security features (I.e. new mitigations)
-
Still not "0 love, not even the occasional security patch" of @tarunik's post.
-
9 Make that 10 Reasons Flash Must Die
Lol @ article.Point 1:
Because Flash is an interpreted language, it's heavy -- so heavy that, in conjunction with the way Flash renders video, it's an absolute battery killer.
As if JS was any different...
Point 3:
When you're looking for weakness, though, a closed system can legitimately be considered a point that's not particularly strong.
Yeah, because bonus eyeballs totally helped with heartbleed and shellshock...
Point 4:
Flash, with its lovely .SWF (a format used by nothing else) presents you with yet another media file type to keep track of, store, and consider in the panoply of files that go into a modern website.
So?
Point 5:
And here's the thing: HTML5 is a programming language that has notable similarities to HTML4. Flash doesn't.
This is so wrong on so many levels.
Flash isn't the single most complicated programming environment to learn and use, but unless you live your entire professional life inside the Adobe Creative Cloud it's different from any of the other languages you use.
First, Flash is not a language - ActionScript is. Second, AS is very similar to Java, while JavaScript is the odd one in the world of programming languages. Also, Flash ecosystem is better thought-out and far more similar to other environments than the HTML5 ecosystem.
Point 7:
One of the ways that Flash programmers deal with the exploits is by releasing updates. And users of Flash can blithely ignore each and every one of them.
The Windows 8 casus clearly shows that it's far better approach than the other extreme. Also, you're saying that one of the reasons why Flash, including its newest release, should go extinct from the web is that some idiots didn't update?
Point 8:
Flash Makes Browsers More Complicated
And JavaScript doesn't. Nor HTML5 media tags, nor CSS particle systems and other eye-candies, nor WebGL, nor all the other W3C bullshit. Nope, those are free in terms of how much more code needs to go into a browser, as opposed to plugin system which is basically "let the 3rd party handle everything".
Point 9:
Have you ever found a great piece of Web animation and then another, and another? Then you looked up and an hour had passed? So have your employees. And we're blaming Flash.
What is this I don't even.
-
There's always boost::format.
I don't even want to open that link. Boost is too scary.
-
AS is very similar to Java
You're so wrong:
//JAVA public String helloWorld(String foo) {...} //AS function helloWorld(foo:String = ""):String {...} //JS function helloWorld(foo) {...}I see more differences than similarities there. AS feels more like VB than and C-like PL™
-
I see more differences than similarities there.
Because you chose a poor example. Look at class declaration in Java and in AS. You both have public members, private members, static methods, non-static methods, constants (though there's the final/const keyword difference), constructors. All functions are annotated with return type and types of arguments. The only real difference is the post-fix type notation, default arguments and lack of enums.Now look at class declaration in JavaScript... oh wait.
-
Point 9:
Have you ever found a great piece of Web animation and then another, and another? Then you looked up and an hour had passed? So have your employees. And we're blaming Flash.
What is this I don't even.
no, we're not blaming Flash, we're blaming the employees for doing it on work time.
-
You're looking at it the wrong way. You can blame Flash, because it allows people to do animations much more easily than JS; and with more animations made, it's harder to keep ADHD workers focussed.
Now excuse me while I go check out some Chrome Experiments.
-
I know one internet community who would use similar reasoning to blame it all on Microsoft.
-
ActionScript is ECMAScript with namespaces. (At least, AS3 is. AS2 was... just shit.)
ActionScript is JavaScript. Basically.
-
You have no idea what you're talking about.
-
You have no idea what you're talking about.
I'm a few years out of date. Maybe ActionScript has changed since I learned it.
-
I don't know what kind of AS you've learned, but AS3 is nothing like JavaScript, as I described above. The only similarity is that both have C-like syntax.
-
ActionScript is an object-oriented programming language originally developed by Macromedia Inc. (now dissolved into Adobe Systems). It is a derivation of HyperTalk, the scripting language for HyperCard.[2] It is now a dialect of ECMAScript (meaning it is a superset of the syntax and semantics of the language more widely known as JavaScript)
If ActionScript is based on ECMAScript, why does it have classes and looks almost the same as Java?
In this article, it says that ActionScript 3.0 conforms to ECMA 4th edition. But instead of looking like JavaScript and having no class or extend, ActionScript 3.0 code looks like Java and have the
Actionscript was compliant with ECMA from the very start.
You could imagine javascript & actionscript as a fork from a single standard ie ECMA, With Javascript inclined to add power to browsers while Actionscript geared towards flash development.
http://www.quora.com/Why-was-ECMAScript-4-ES4-never-implemented-outside-ActionScript-3-at-Adobe
etc. etc. etc.
ActionScript was originally developed from the (in-progress) ECMAScript 4 spec, with a few Java-like additions as well. ECMAScript was basically never adopted by anybody else, which makes it something of a fluke.
So if by "nothing like" what you mean is "derived directly from", then I guess you're correct. Good job. +1.
-
...ooookay... I admit, I was wrong. Maybe because I've only been ever exposed to idiomatic AS and never tried to write in it like in JS.
-
The real reason to kill it is simply waning need for it, resulting in waning support. With Droid devices' browsers not supporting it, for example, it can be inconvenient. Just last week I went to submit a support ticket at work to our telco, and it hung when I tapped the submit button...why? Because they use FLASH to process it!
Could not resubmit either because resource was 'in use' - spent an hour on phone with support to get the ticket opened, as even they struggled with it. Why they even use Flash for that...
-
I didn't mean Flash shouldn't die. I meant the article makes shitty arguments for that.
The real reason to kill it is simply waning need for it, resulting in waning support. With Droid devices' browsers not supporting it, for example, it can be inconvenient.
Yep, waning support is certainly a reason why Flash should die. Which is ironic, because the reason why the support is waning is that someone decided it should die. A nice circular reference that the humanity managed to garbage-collect.
-
I didn't mean Flash shouldn't die. I meant the article makes shitty arguments for that.
I know. Thant's why I liked your original post.
ActionScript - Wikipedia
