Software from the Pits of Hell: Remembering Flashstuffer
1–10 of 13 posts
Re: Software from the Pits of Hell: Remembering Flashstuffer
#2The killer line is of course the last.
Killing Flash did not kill punch the monkey ads and it didn't suddenly make web pages note efficient.
It just changed the delivery mechanism.
Re: Software from the Pits of Hell: Remembering Flashstuffer
#3Am I the only one who sees bright horizontal lines while my eyes are closed, after looking at this article for a minute or two?
Re: Software from the Pits of Hell: Remembering Flashstuffer
#4Am I the only one who sees bright horizontal lines while my eyes are closed, after looking at this article for a minute or two?
You're probably getting retinal detachment.
Re: Software from the Pits of Hell: Remembering Flashstuffer
#5The killer line is of course the last. Killing Flash did not kill punch the monkey ads and it didn't suddenly make web pages note efficient. It just changed the delivery mechanism.
Mmmmm yes we have 5MB of web assembly garbage instead of 50k of flash. All when 5k of HTML and CSS would do …
Very little genuine value added in the process.
Re: Software from the Pits of Hell: Remembering Flashstuffer
#6Am I the only one who sees bright horizontal lines while my eyes are closed, after looking at this article for a minute or two?
Is your brightness set very high? Maybe after-images of the white text.
Re: Software from the Pits of Hell: Remembering Flashstuffer
#7> Now if you were one of those unlucky people who had to code Actionscript
Unlucky? Adobe had us writing typesafe ECMAScript, JSX and SwiftUI in 2006.
The unlucky ones were folks who thought they had to use PureMVC, cairngorm or RobotLegs to build large applications.
Re: Software from the Pits of Hell: Remembering Flashstuffer
#8> Now if you were one of those unlucky people who had to code Actionscript Unlucky? Adobe had us writing typesafe ECMAScript, JSX and SwiftUI in 2006. The unlucky ones were folks who thought they had to use PureMVC, cairngorm or RobotLegs to build large applications.
> writing […] SwiftUI in 2006
Huh? How?
Re: Software from the Pits of Hell: Remembering Flashstuffer
#9> Now if you were one of those unlucky people who had to code Actionscript Unlucky? Adobe had us writing typesafe ECMAScript, JSX and SwiftUI in 2006. The unlucky ones were folks who thought they had to use PureMVC, cairngorm or RobotLegs to build large applications.
> writing […] SwiftUI in 2006 Huh? How?
I'm exaggerating; Adobe Flex's MXML was an XML schema for building application UIs declaratively. It supported custom elements, which would correspond to classes you'd write, whose constructors, fields and methods would mirror the attributes and events on the DOM, kind of like a stricter HTML5.
That's a good description of the Flash ecosystem from 2006 onwards, actually: before its time, and more stringent than what came after. That strictness was the legacy of ECMAScript 4, I suppose.
Re: Software from the Pits of Hell: Remembering Flashstuffer
#10The killer line is of course the last. Killing Flash did not kill punch the monkey ads and it didn't suddenly make web pages note efficient. It just changed the delivery mechanism.
Mmmmm yes we have 5MB of web assembly garbage instead of 50k of flash. All when 5k of HTML and CSS would do … Very little genuine value added in the process.
> Very little genuine value added in the process.
And 25 years worth of content lost because Adobe couldn't open source flash.