←back to thread

Ask HN: Abandoned/dead projects you think died before their time and why?

358 points ofalkaed | 7 comments | 11 Oct 25 22:16 UTC | HN request time: 1.434s | source | bottom

Just curious and who knows, maybe someone will adopt it or develop something new based on its ideas.
Show context
zaptheimpaler ◴[12 Oct 25 08:20 UTC] No.45556394[source]▶
Adobe Flash / Shockwave. After all these decades, I've yet to see a tool that makes it as easy to make games or multimedia as Flash did. One of many reminders recently (many others in politics) that humanity doesn't just inevitably or linearly move forward in any domain, or even 2 steps forward 1 step back. Some things are just lost to time - maybe rediscovered in a century, maybe never.
replies(14): >>45556456 #>>45556552 #>>45556787 #>>45556840 #>>45557111 #>>45557571 #>>45557593 #>>45558222 #>>45559471 #>>45560431 #>>45560698 #>>45561427 #>>45561684 #>>45567195 #
Y-bar ◴[12 Oct 25 08:33 UTC] No.45556456[source]▶
Those tools were awesome. But as formats go, they were awful due to bad performance and more security holes than anything else.

I still miss Macromedia Fireworks.

replies(5): >>45556521 #>>45556539 #>>45556917 #>>45557127 #>>45557469 #
1. GuB-42 ◴[12 Oct 25 10:00 UTC] No.45556917[source]▶
Performance was way better than what we have now with modern web stacks, we just have more powerful computers.

I agree on security and bugs, but bugs can be fixed. It just shows neglect by Adobe, which was, I think, the real problem. I think that if Adobe seriously wanted to, it could have been a web standard.

replies(1): >>45558509 #
2. Y-bar ◴[12 Oct 25 14:33 UTC] No.45558509[source]▶
Lots of people say performance was good, but that seems to be through the nostalgic lens of a handful of cool games.

Those did sometimes run really great, but most implementations were indeed very slow.

I remember vividly because it was part of my job back then to help with web performance and when we measured page speed and user interface responsiveness flash was almost always the worst.

replies(1): >>45558666 #
3. masfuerte ◴[12 Oct 25 14:58 UTC] No.45558666[source]▶
Right. But that doesn't mean the performance of Flash was bad for what it was doing. Or that it was worse than the performance of doing the same thing in modern HTML+CSS now.
replies(1): >>45558752 #
4. Y-bar ◴[12 Oct 25 15:11 UTC] No.45558752{3}[source]▶
The default, and by far the most common, output from Flash had significantly slower click-to-response and for network latency and for rendering than HTML+CSS is today.

You remembering a few optimised instances does not change the reality that Flash was bad.

replies(1): >>45558803 #
5. masfuerte ◴[12 Oct 25 15:18 UTC] No.45558803{4}[source]▶
You're still comparing Flash on twenty year old hardware to HTML+CSS on modern hardware.
replies(1): >>45559531 #
6. Y-bar ◴[12 Oct 25 16:37 UTC] No.45559531{5}[source]▶
I am not and have never compared them in the way you say I did. You literally wrote ”Or that it was worse than the performance of doing the same thing in modern HTML+CSS now.” so I had to somehow repsond to that strange claim.

Of course modern computers are orders of magnitude more powerful! But Flash was definitely generally worse compared on the same hardware and network stack compared to vanilla (non-plugin based) web tech.

replies(1): >>45562763 #
7. nrdvana ◴[12 Oct 25 22:48 UTC] No.45562763{6}[source]▶
Maybe at rendering menus and documents, but flash had graphic routines written in optimized assembly that simply weren't possible with JavaScript on that era of hardware.

I feel like people are talking past each other a bit here. FlashScript was never very fast, and rendering a document as a giant collection of bezier curves was not fast, but the people doing animations with it were getting the equivalent of modern day CSS3 animations + SVG, and it ran nicely on hardware two orders of magnitude slower than what we need for CSS3+SVG