This doesn't make it clear how people will run the end products. Is it targeting the web? If not then it's not going to be useful for the same things as Flash was.
It says: > HTML5/Canvas export — Export to self-contained HTML5 with JavaScript Canvas 2D playback.
Building a new Flash
21–30 of 247 posts
Re: Building a new Flash
#22The vector icons in the side bar have the distinct cruft of LLM-generated SVGs, so just ideally hoping it isn't a quickly-made UI shell. The big claims about .fla import make me a bit skeptical. Though even so, we're not owed anything and I think it's a cool idea to share!
Re: Building a new Flash
#23I wonder how much this would impact the react world
Re: Building a new Flash
#24I wish Adobe had open sourced Flash - it really was a pretty amazing tool. They could have owned the proprietary developer tool market to support themselves...
Re: Building a new Flash
#25We built a dedicated cluster in a colocation center in Bucharest to handle all of this. Had issues with max floor weights and what not. Then had to upgrade the RAM on on the cluster. No remote hands. Every operation was a trip to a really cold place.
Used a lot of early stage stuff like Nutch, Hadoop, HBase etc. Everything was then processed and dumped to an SQL database with a nice UI on top. It took a few weeks to set it up, then we passed it to a team of interns that built the SQL database and UI on top. They learned a ton of stuff. Some are now in the Bay Area.
The tool uncovered a ton of security issues.
It was fun building it. I wonder if Adobe kept the data. It could be useful and/or good donation for the Computer History Museum.
Re: Building a new Flash
#26I remember trying out Macromedia Flash 6.0. My GUI apps were ugly at the time. Learning to build something like I saw in the movies could take years. Then, Flash let me throw together beautiful, animated interfaces like it was nothing. One could do quite a bit after one tutorial. (Note: Quick shoutout to Dreamweaver 6.0 which was a power, WYSIWYG editor. Today, things like Pinegrow might fill the niche.) It's death a…
Of the two, I think Adobe is most responsible for the decline of Flash. Even if smartphones had never entered the picture, laptops (where efficiency is important) were quickly becoming the most common form of PC, which would've eventually made Flash as it existed under Adobe untenable as well. The timeline was just accelerated by smartphones. Honestly I can't understand the mental calculus that went on in the heads o…
The bugs were definitely Adobe's fault: as with most tech companies, they were far more interested in expanding the feature set than they were on fixing the bugs and stabilizing the platform.
Re: Building a new Flash
#27We can't trust closed source software for content creation tools.
What happens when he gets bored?
However, I LOVE C# and would totally be down to contribute if it's open source.
Re: Building a new Flash
#28I wish Adobe had open sourced Flash - it really was a pretty amazing tool. They could have owned the proprietary developer tool market to support themselves...
They couldn't because it lives on in Adobe Animate which Disney as a customer among others.
A lot of people - including studios who use it for projects that can take years to complete - were very unhappy at the prospect of having the only tool that can read their mountains of FLA files (the file format the Flash/Animate editor uses, and used to compile into a SWF) stop working because Adobe turned off the auth servers. Adobe has pulled back to "okay we're, uh, putting it in maintenance mode, expect no new features, ever, just security patches".
Re: Building a new Flash
#29Unless this is open source I don't see the point. We can't trust closed source software for content creation tools. What happens when he gets bored? However, I LOVE C# and would totally be down to contribute if it's open source.
as to when they share the source, idk!