News for hackers. Stuff that matters.
Re:The best way for Adobe to save Flash is by killing it by poppysan on Sunday January 31, 2010 @06:35PM (#1091323)
I'd argue that they are good enough at building browser runtimes that theirs has 90%+ market saturation, and is an industry standard.

Now open is another issue...

Re:The best way for Adobe to save Flash is by killing it by radley on Sunday January 31, 2010 @07:01PM (#1091382)
Seriously? Did Adobe beat you guys up and take away your computer? Did they say "no no no mine?"

Where is the "not open" you guys claim? Flex SDK + Eclipse == free Flash development.

I swear HTML5 fanatics just make stuff up these days. You'll use Windows, Flickr, Google, and Hacker News - all privately owned systems. But god forbid Flash is bad because... why?

Re:The best way for Adobe to save Flash is by killing it by stevenwei on Sunday January 31, 2010 @07:42PM (#1091441)
Open != free.

Lack of openness: a browser plugin that is less stable and slower on Mac and Linux that noone else can fix except Adobe...and only if they choose to do so.

Lack of openness: a browser plugin that doesn't properly utilize cookies on non-IE browsers that noone else can fix except Adobe...and only if they choose to do so.

Lack of openness: a browser plugin that doesn't properly return HTTP status codes on OS X that noone else can fix except Adobe...and only if they choose to do so.

Re:The best way for Adobe to save Flash is by killing it by batterseapower on Monday February 01, 2010 @03:50AM (#1092055)
I think your comments here are off base.

The SWF standards (and associated standards like RTMP) are available for free on the Adobe website. You are permitted to construct alternative implementations based on this specification. I think it meets the definition of an open standard.

Would HTML not be an open standard if the only browser we had was IE, and it was horribly buggy? No - the quality of the available implementations is irrelevant to a standards "openness".

Re:The best way for Adobe to save Flash is by killing it by chmola on Sunday January 31, 2010 @07:58PM (#1091466)
You're assuming everyone posting replies and that the author of the post are all HTML5 fanatics. Have you considered that many of us might have worked heavily in Flash/Flex for years designing website and applications, and that possibly the uprising against Flash mentioned here involves Linux Flash plugins seg faulting with no error messages, crazy Flex binding memory usage, general CPU overload and a horrible debug log policy due to sandboxing? I'd be interested to hear why you think Flash is good. Incidentally, who's using Windows? :)
Re:The best way for Adobe to save Flash is by killing it by radley on Monday February 01, 2010 @02:57PM (#1093288)
Sounds funny, but my only supporting fact is I wouldn't be here without Flash. I basically loath programming but I'm willing to do it because of Flash.

Sure there's CPU problems and there will always be more-optimized forms of code. But Flash has a timeline, which is something few here will understand or appreciate.

Plus it really is ubiquitous, unlike anything else. I'll take a small performance hit if it means I don't have to learn/write/test multiple languages and systems.

I'm not in this for the code. I'm in it for the UX.