Flash Is Responsible for the Internet's Most Creative Era

Adobe has been trying to maintain backwards compatibility with flash (because most studios were still using the last version macromedia put out over 10 years ago) So adobe animate was always doomed to try and please everyone and end up pissing everyone off.

- you had types, performance was important so you had generic types like Vector , the code was compiled and it was really fast

- there were built-in efficient GUI widgets, you could have a list or table connected to a data provider with tousends of items but the components were smart and only created enough UI widgets as needed to render, where in HTML you either have to create a LI element for all your 10000 elements, create pagination(is not built in), create infinite scrolling(not built-in)

- it was super easy to customize or extend the provided things if you needed , as an example in HTML look at the it is not customizable, everyone has to implement it's own using divs, css and js , but everyone gets it wrong in the corner case(you have issues where the dropdown pops outside the screen, missing events, hell even youtube search box sometimes breaks and the dropdown popup remains stuck open, so even Google engineerscan't create a working dropdown component

- performance, remember when a blinking cursor was causing an electron editor to use a lot of resources , the issue with web is that was designed in rush for showing documents.

- layouting components was super easy , theming was easy - with css in large old projects there are so many issues( I know people use less but this is not standard )

I have some solutions too, browsers need to provide more powerful components, if we want to do RIAs or desktop apps then we need the same components that desktop toolkits offer with the same customization. Other issue I seen was in a project where the devs ahd to import a third party library because the scrollbars can't be themed in all browsers , I am not refering to the right side of the browser ones(I know sme people hate if you change those) but scrollbars on a list or dropdown component. So you have projects where you import 1 lib for scrollbars, 1 lib for modals, 1 for fancy buttons and inputs, 1 for drag and drop, 1 for calendar widgets, 1 for dropdown that allows you to have icon + text, and of course a framework like angular or react . Browsers should check what developers need the most and add that as standard( ex better dropdowns) you would still have the ability to make your own shit and use your preferred framework

The iPhone killed flash but not just in the obvious way. These days everything needs to be reactive and run on well on mobile hardware. Even if iOS supported flash it would need to be a different beast. Different screen sizes, an explosion of aspect rations, heavier security requirements, accessibility, touch controls and more led to the downfall.

The first beginner tutorial is about displaying a bitmap and starts with a terminal [1]. This is not as discoverable as Flash’s tools, which felt more like MS Paint when first opened.

[1] https://www.openfl.org/learn/haxelib/tutorials/displaying-a-...