upvote
Love or hate Steve Jobs, his insistence of not supporting Flash on the iPhone (in favor of HTML5) accelerated Flash's demise dramatically.
reply
The best feature of flash was that it was so easy to disable. Because 99% of the use was annoying ads that pinned your cpu at 100%.

And that was Jobs argument, that it was too resource intensive. Predictably though, now that annoying crap moved to "newer" tech (javascript) and now we can't disable it as easily or without as little consequence. Just as resource intensive though...

reply
> And that was Jobs argument, that it was too resource intensive.

One of his arguments, and not the most important one. Looking at https://newslang.ch/wp-content/uploads/2022/06/Thoughts-on-F..., he says the most important reason is that Apple doesn’t want Adobe to be in control of a major API on iPhones (he buries that’s the main reason somewhat by mentioning it last because, I think, he knew that argument is more “because it’s good for Apple” than “because it’s good for our users”)

Yes, he mentions reliability, battery life, security, too, but those are things Adobe (in theory) could have fixed.

He also mentions Flash isn’t open. Again that is is something Adobe could have fixed, but I doubt they were fully willing to do that at the time

reply
I never bought the benevolent technical angle for not supporting flash. I'm pretty sure Apple strategists knew the value of the gate-kept platform, the app-store revenue stream.

The pivotal point was that flash would break this stronghold by allowing rich applications that are reasonably self-publishable. (Excuse me while I go rinse that sentence out of my mouth)

reply
First iPhone didn't have support for 3rd party apps. Steve Jobs even explicitly spoke about wanting to have all 3rd party things run in the browser.

Only when jailbreaking and custom apps got very successful, Apple introduced official app support and the appstore.

reply
I think the Appstore was planned all along, just did not fit in the first release, so they adapted the launching narrative to: "the browser is enough for all 3rd party software".
reply
No, Steve was very vocally against it until jailbreaks forced the issue. It’s well documented.
reply
Vocally public yes… but they wanted to see what the diy scene created, how the power users were using the device and letting them develop the ideas and implement… they would open up and co-opt… boss tools is your drag down for all your settings case in point. This has been openly admitted to in interviews after the fact.
reply
They 100% did not let the power users and DIY scene exist. It only existed by exploiting OS security vulnerabilities. Every new iOS release required finding a new way to crack it. That's why a lot of people chose Android.
reply
[citation needed]
reply
Apple didn't even have an AppStore in mind until people started hacking apps onto it.

Remember back in 2007 when Apple first told developers that to develop for the iPhone, they’d need to build WebApps for Safari? Well, that really was the plan. At the time, Jobs said:

    The full Safari engine is inside of iPhone. And so, you can write amazing Web 2.0 and Ajax apps that look exactly and behave exactly like apps on the iPhone. And these apps can integrate perfectly with iPhone services. They can make a call, they can send an email, they can look up a location on Google Maps.

    And guess what? There’s no SDK that you need! You’ve got everything you need if you know how to write apps using the most modern web standards to write amazing apps for the iPhone today. So developers, we think we’ve got a very sweet story for you. You can begin building your iPhone apps today.
The App Store came later and apparently as a reaction to jailbreakers and developer backlash.

https://9to5mac.com/2011/10/21/jobs-original-vision-for-the-...

Jobs hated Adobe:

According to the biography, Jobs’ longstanding animus toward Adobe helped form his vision for Apple’s tightly controlled mobile environment.

In 1999, he was flatly denied when he asked Adobe to create a version of its popular Adobe Premiere digital-graphics software for the Mac. Adobe also wouldn’t rewrite Photoshop for the Mac’s operating system, even though Macs were popular with designers.

“My primary insight when we were screwed by Adobe in 1999 was that we shouldn’t get into any business where we didn’t control both the hardware and the software, otherwise we’d get our head handed to us,” Jobs said, according to Isaacson.

The two companies go back together even further. Apple invested in Adobe in 1985 and they worked together early on. But Jobs, who in Isaacson’s book comes off sometimes as vindictive and brusque as he was innovative and inspirational, told Isaacson that Adobe went downhill after founder John Warnock retired.

“The soul of Adobe disappeared when Warnock left,” he said. “He was the inventor, the person I related to. It’s been a bunch of suits since then, and the company has turned to crap.

https://edition.cnn.com/2011/11/09/tech/mobile/flash-steve-j...

reply
> The soul of Adobe disappeared when Warnock left

Very OT, but can I say i’ve seen this happen at every company i’ve been? When the founder(s) get out of the picture they kinda bring the soul of the company with them.

Yeah there’s a fading halo still in the air for a while, but it’s just that: a fading halo.

reply
I remember seeing stories about Adobe not being able to, or not wanting to, write a good energy efficient flash renderer for the iPhone, thus being another reason not to support it for Jobs (Adobe being of the mind that "Flash is so big, they'll have to support it" and Jobs proving otherwise)
reply
They also either could not or would not write efficient Flash clients on Mac OS or Linux, while the Windows version was fine.

I bounced around a lot between the three OSes at that time, and Flash was bad enough on the other two that I would almost automatically reach for Windows when I had to use it.

reply
It took them years to realize that the App Store could be a thing.
reply
and now they make probably insane marketshare on the AppStore alone.
reply
> Apple today announced the global App Store ecosystem facilitated over $1.4 trillion in developer billings and sales in 2025

https://www.apple.com/newsroom/2026/06/app-store-ecosystem-r...

Then again, they chose to use those exact words in their webpage, so you decide how large a grain of salt to take.

reply
> I never bought the benevolent technical angle for not supporting flash.

Why not? Flash was objectively an awful experience on mobile, and the iPhone was entirely about good UX.

> I'm pretty sure Apple strategists knew the value of the gate-kept platform, the app-store revenue stream.

Initially the iPhone didn't even have an app store. They wanted everyone to make HTML5 apps.

reply
There was also the argument that "We also know first hand that Flash is the number one reason Macs crash"
reply
Flash had many issues for sure, first and foremost security. But I can’t help but feel sad of what was lost since then. The Flash era produced some really unique experiences on the web.
reply
it was about as unique as seeing corn in my poop sometimes.
reply
Lot of it was bad, sure, but there was so much games and animation done by literal kids back then, because of how easy it was to create something with the tooling. Nothing even come close today, unfortunately.
reply
The JimCarrey.com website was cool. That's about the only flash thing I came across that was though. Now gone as a site but recorded on video https://youtu.be/B1XZixLBurQ I'm not sure you can do those things in javascript to this day?
reply
Sounds like you didn't experience all the awesome flash games and animated videos etc that people made.
reply
And now were back with WebAssembly, WebGL, WebGPU, targeting 10+ year old graphic cards, without comparable easy of use tooling.

Those that think using Godot or Unity is the same, never did Flash games.

reply
Flash was better back when it was called VideoWorks. ;)

Notably, there was also a MusicWorks. Both Mac-only. But like EARLY Mac-only.

/dates me

reply
"Please buy the next version to see if we fixed your bug?" is peak Adobe.
reply
> heisenbugs

gold

reply
A well-established term of art dating to 1983:

<https://en.wikipedia.org/wiki/Heisenbug>.

reply
I also learned this term pretty recently, loved it. Another fav tech term is automagically :-)
reply
I'm guessing you are very young!
reply
Fnord gold
reply
23 skidoo.
reply
Fnord Knox
reply
deleted
reply
Flash is still unsurpassed as the easiest publishing medium.

JavaScript build system layer cake and "web standards" are a million times harder than just drawing some stuff, maybe writing a simple function, then building a static file that can be embedded anywhere and even downloaded. You have to spend so much time setting up any flash alternative, and the "standards" are worse.

I hate Steve Jobs for killing Flash and Adobe for being such awful stewards of one of the most amazing web technologies.

Kids growing up today have no idea how magical Flash was. It was like Roblox or Minecraft for web.

Websites are still inferior to Flash of the early 2000s. It's taken decades and they can only mimic a fraction of its power. And none of its ease.

reply
Magical? Those are some rose tinted glasses. Having to install a binary blob from a free-software hostile vendor that wanted a monopoly to load a website was always ridiculous ask. Flash was a constant embarassment of RCEs vulns and virtually non-existent Linux support.
reply
I remember the time of browser plug-ins (not “extensions”). Everyone happily installed Flash, and the Crescendo midi plugin, and multiple other in-retrospect-ill-advised plugins to enable fun stuff to work in their browser.

The “everyone hates Flash” stuff came later. It served a purpose for quite a while and people loved it. Newgrounds was a place of magic.

reply
FYI, just cause I discovered this recently and I was mildly mind blown: newgrounds is alive and kicking with new stuff.

I do miss kongregate tho.

reply
I mean, flash was always a pain in the ass, even when you got it working. The animations and games were great and I'm a big fan of stuff that tries to make it easy to publish programs like that, but I was still a teenager when apple announced they weren't supporting it and I was genuinely happy because I was so annoyed using it even on a windows pc.
reply
> Having to install a binary blob from a free-software hostile vendor that wanted a monopoly to load a website was always ridiculous ask.

The entire browser ecosystem started out closed source. Even JavaScript was written to interact with closed source Java Applets.

> Flash was a constant embarassment of RCEs vulns

Browsers still are the goto target for contests like Pwn2own. It is almost like inviting the entire world to run untrusted code on your computer is not a great idea, no matter how many security buzzwords browser makers like to throw arround.

reply
> The entire browser ecosystem started out closed source.

That is completely, 100%, untrue and not remotely historically accurate. WorldWideWeb (the first web browser) was public domain. Lynx came out in 1992. Mozilla was open sourced in 1998. There was never a time when the "entire" browser ecosystem was closed source. It certainly didn't start that way.

> Even JavaScript was written to interact with closed source Java Applets.

No, it wasn't. From WP (https://en.wikipedia.org/wiki/JavaScript):

> Netscape decided to add a programming language to Navigator. They pursued two routes to achieve this: collaborating with Sun Microsystems to embed the Java language, while also hiring Brendan Eich to embed the Scheme language.

> The goal was a "language for the masses", "to help nonprogrammers create dynamic, interactive Web sites". Netscape management soon decided that the best option was for Eich to devise a new language, with syntax similar to Java and less like Scheme or other extant scripting languages.

> [...]

> The choice of the JavaScript name has caused confusion, implying that it is directly related to Java. At the time, the dot-com boom had begun and Java was a popular new language, so Eich considered the JavaScript name a marketing ploy by Netscape.

Some people might have used it for the purpose you claim, but that's not why it was invinted.

reply
> Netscape decided to add a programming language to Navigator. They pursued two routes to achieve this:

And the reason for that two language approach is given in the linked source:

> We aimed to provide a “glue language” for the Web designers and part time programmers who were building Web content from components such as images, plugins, and Java applets. We saw Java as the “component language” used by higher-priced programmers, where the glue programmers—the Web page designers—would assemble components and automate their interactions using [a scripting language].

Earlier sources clearly state that Java was intended as the primary language and JavaScript merely acting as glue.

reply
Yeah but we were kids, we didn't give a shit about any of that. Kind of still don't give a shit about any of it tbh. There's security holes in everything anyway.
reply
The overwhelming majority of computer users simply DO NOT CARE about things like "install a binary blob" or "free-software hostile vendor" or "non-existent Linux support". They installed the plugin and got a way better experience.

> Flash was a constant embarassment of RCEs vulns

I wonder if anyone has done an analysis of Flash versus Javascript (or other browser technology) vulns over their respective lifespans.

reply
If Flash hadn’t sucked harder than a neutron star, that would be an argument to have. People install lots of proprietary plugins today. Flash would’ve been just one more on that list.

But it did suck, and badly. It crashed the browser all the freaking time, often hard enough to crash the whole OS. (“But the OS shouldn’t let that happen!” True, although even with that said, it was in the short list of common apps capable of crashing that badly. It was almost a talent.)

Flash was horrid. While idea was fine, the implementation was terrible. No mobile OS could have run it solidly and without sucking batteries like no tomorrow. Flash in the right hands could have been nice. We’ll never know because that never happened.

reply
> No mobile OS could have run it solidly and without sucking batteries like no tomorrow.

By the time mobile could run Flash, it was too late. Between Apple & Adobe, it had no shot of making the transition. But before that, Flash was pretty amazing.

reply
It was never amazing. It was adequate to give creative people a way to work around its many shortcomings and make something cool anyway. The tech and the implementation was awful, and all credit goes to people who still managed to shine through it.

For all the many reasons people might dislike Apple, they were 100% in the right on this topic. Flash needed to die. It got everyone to collectively push the web standard technologies ahead into something way, way better.

reply
> The tech and the implementation was awful, and all credit goes to people who still managed to shine through it.

Sorry, that's simply not true. The tech was ahead of its time. The implementation was intuitive. Only developers and Steve Jobs hated it, because Flash made it way too easy for anyone to make something fun.

reply
Also anyone who gave two shits about security hated it because it was a security nightmare. Don't leave a hater out.
reply
And yet, there was no html5 newgrounds. The magic of flash was that it gave a space where a music person, an art person, and a programmer could bang something out. The barrier to entry was comically low, which allowed an absolute explosion of content.

Sometimes good products happen despite bad technical foundations.

reply
> And yet, there was no html5 newgrounds.

Let me introduce you to itch.io[0] where, in fact, people bang out HTML5 games at a rate that will stagger your eyeballs.

(Even me, a resolute "backend-only" dinosaur managed to use a HTML5 game engine to knock something out playable in an hour or two.)

[0] https://itch.io/games/platform-web - ~689k results

reply
[flagged]
reply
I was an average-joe high school student back then.

People hated flash. Even non techies.

reply
What’s “back then” to you? Flash grew up in the time of dial up when you could still get AOL install discs with 100 free hours in your typical grocery store PC magazine. I don’t recall people hating Flash a lot until later when it wasn’t a technical necessity anymore.
reply
The first computer I remember using was a Compaq Portable with a green screen and DOS that my dad was allowed to bring home on weekends. I vividly remember going to Circuit City as a family to buy our first windows 3.1 machine.

Flash was very cool, at first, then it got used for WAY too much stuff that had no graceful degradation so you were stuck waiting a few minutes for an animation to load so you could see the content stuck behind flash.

reply
Flash certainly became broadly hated. It had a pretty long stretch of being loved, and enabling content that was loved, though. Up until about 2005 or so, flash was critical tech for the young web. By 2010 it was clearly heading toward an end.
reply
I remember strongly disliking Flash before 2005, and many tech-minded people I talked to agreed. It was an awful install, always needed an updated, was a memory hog, and was a pain in the ass to use without it crashing. Yes, it must have been great to create apps with (I never did), but it was not beloved. Flash games were beloved, not Flash.
reply
> People hated flash. Even non techies.

Billions of people enjoyed using Flash for games, video, music, and animated entertainment.

reply
Enjoying a game, video, or music is different than enjoying the underlying means of delivery.

Do people love Javascript and HTML5, or do they like streaming entertainment?

Do gamers love Unity, or do they love playing fun games, some of which are made with Unity?

I played games on every Windows from 3.1 and up (and MS-DOS before that), but I'm not pining for the days of Windows ME despite how much fun I had on that machine.

People used Internet Explorer to run all their Flash entertainment, but nobody is arguing that IE was loved even though it was part of the flash stack for a huge majority of users.

Notably, Flash is dead, and no one is arguing that we bring it back.

If I never have to sit through a flash loading bar gating an HTML website with a completely unnecessary splash page, you won't find me mourning. (yung'uns: this was a thing. If you wanted to go see a website sometimes you had to sit for a while so a dumb flash animation would show and you could click through to the actual HTML content. Jobs did you a favour)

reply
You're completely (and I think intentionally) missing that flash enabled people to easily create those things... and that creativity and ease of use still hasn't been replicated (your example of Unity - doesn't come close to the ease)

People loved flash for what flash was good for (creative toys) they disliked flash when certain sites started making it the core of the navigation etc.

When people are nostalgic for flash it's for finding random toys from other people who weren't "IT people".

reply
or they enjoyed the games despite flash.
reply
Doesn’t pass the smell test. “Billions” is >2 billion. There weren’t that many people online when iPhone came out with its famous flash ban. https://ourworldindata.org/internet
reply
Your source shows 1.36 billion people using the internet in 2007. In English, when we say "in the billions" it means more than a billion.
reply
People loved flash games.
reply
what? no? people generally loved, especially with the likes of frog in a blender...

for the younguns https://archive.org/details/joe-cartoon-frog-blender#

reply
The average person didnt really care what tech was involved, they dont romanticize software in the same way as tech inclined people do.

People hated it when apps were glitchy, when it wanted "constant" updates, or how they couldnt share a page because the entire site was some bloody flash applet.

reply
> You're in the 0.001%. Your asks are arcane and orthogonal to most users of software, who just want their PC to do something neat and useful.

Right up until enshittification kicks in and suddenly everyone cares and there are shouts of destroying the evil techbros who are poisoning the minds of our youth to buy a new yacht.

Can you imagine the situation if Jobs hadn't killed Flash? Most of the commercial websites required a Flash blob to deliver full functionality even back then in the early 2000's. Adobe never even vaguely pretended to be the good guys, they would have enshittified as soon as they possibly could, as hard as they possibly could (as they have done with the rest of their software). The entire web would be held to ransom at this point.

reply
> Most of the commercial websites required a Flash blob to deliver full functionality

Being a binary blob is not a strong argument all by itself. chrome.exe, firefox.exe, etc. are also binary blobs. I have no love for Adobe, but that specific criticism is weak.

reply
Sure, but Adobe was never going to solve them.
reply
> Websites are still inferior to Flash of the early 2000s. It's taken decades and they can only mimic a fraction of its power.

Is this a troll? What could an application do with Flash in 2005 that we can't do with a modern web application today (excluding the obvious answer of runtime vulnerabilities that allowed apps to escape the sandbox)?

reply
> What could an application do with Flash in 2005 that we can't do with a modern web application today

Show me the JavaScript framework (or tool that exports JS) that you can give it to a middle schooler and have them make a cartoon with audio and moving images that they can draw themselves, while responding to user input. Have the exported artifact be consistent across all major operating systems and browsers.

Yeah, Flash was never replaced

reply
Flash had its problems but as a user, it looked sharper and smoother than even current websites. And its editor gave non-tech users ability to create amazing animations, interfaces, and even games.
reply
wasn't some of that smoothness because it ran at a 100hz tick without any way of adapting it (and still running existing code)? That was the complaint I kept hearing from people attempting to make flash on phones viable (this led to ludicrous battery consumption)
reply
It could be smooth AF in ways that a video on a service like YouTube never could be.

I didn't get into flash games at all, but I used to watch Flash animations.

Like, for instance, Salad Fingers: https://archive.org/details/flash_salad-fingers

This was intended for a slow 2004-era computer with a 4x3 (probably 1024x768) display, where it worked very well.

But it's not 2004 anymore; things are much faster and screens have gotten a lot bigger. Here in 2026, Salad Fingers renders out fine at higher resolutions, and at different aspect ratios. It works great on my desktop at 1080p, without stretching [and with some probably-unintentional extra content on the sides]. It even works on my pocket supercomputer's 3200x1440 20:9 display.

Vectors are fun, and they scale as technology improves. The lines remain smooth and defined. And with Flash, that's a built-in: An unaltered 22-year-old digital animation still looks crisp.

For contrast, if Salad Fingers had been published on YouTube way back around that time, it would have been in chonky fixed-pixel 320x240. Maybe that would be as good as it would ever get unless it were rendered and uploaded at higher resolutions later.

reply
Image-wise, SVGA + JS probably gets you the clarity. Standard gif / image animations not so much, if that's what you're referencing.

This isn't my baliwick, so I've absolutely nothing to say about the ease with which these options can be created.

reply
Conceptually maybe you can compile flash to SVG+js but this has nothing to do with the point. Many insist (I have no direct experience) that the flash ecosystem (especially the editor) was and is unsurpassed as a publishing platform for interactive experiences.

Today with the current focus on mobile+low latency+e-commerce optimizations flash would probably have shown a lot of limitations, yet JavaScript, SVG, canvas, http webgl etc still fail to provide a "competitor" to what flash used to be.

The web simply went in a different direction, one that left many unsatisfied

reply
what’s he is referring is the editor and the easy way of drawing things, still agree we can do things today but a easy to draw editor like that is missing. I was a fan of flash and fireworks.
reply
The editor was a scripted timeline, similar to a video or animation timeline. It was fantastic for creatives, but counterintuitive for programmers, so most devs hated it.
reply
There was more unique content/UI in the Flash era.
reply
This went away not only because flash died, but also as the internet commercialized.

I mean, consider this: McDonald’s used to be fun and colorful. Now every McDonald’s is boring and gray. And, wait, every store is boring and gray! And flash had nothing to do with that.

reply
You'll get hammered for this on HN, but the web was magical and weird with Flash around, and now it feels quite vanilla and boring. I long for the days of weird experimental art and goofy animations and bonkers UIs.
reply
It was a fun and experimental time for sure. Way more stuff was weird in a good way. Standards hadn’t settled. All kinds of fun stuff was created in Flash that could not have been built with the standardized web tech of the day. I don’t really miss Flash but I do miss the early internet sometimes and Flash was part of that. (Remember when it was FutureSplash?)

I would be remiss if I didn’t post the most early-Internet-type thing I’ve encountered in a long time. Dungeon Soup.

https://m.youtube.com/@DungeonSoup

Once upon a time this would have been my favorite Flash cartoon series.

“Season one” playlist: https://youtube.com/playlist?list=PLSq76P-lbX8Ws6vgAAC2WhwSu...

reply
I would rather say, that now the web feels like being handed turds at every turn, and needing to wear a hazmat suit, if one wants to stay clean. Not what I would call boring. More like infuriating.
reply
Yeah but the execution still mattered. I'm a Flash / Shockwave fan as well but there's no point pretending that package was sufficient for the job it was pitched to do. Macromedia seemed to be on a really good track with Shockwave and Flash, but either didn't set up the technology for internet success, or really just sold out the goods with the Adobe acquisition.

In any case, take heart though. If we did it once, we can do it again.

reply
But we won't because this isn't something that can be done by consensus or by an ad company.
reply
What I never understand is why we never got a Flash-level authoring tool that exported to modern JavaScript/Canvas. Ruffle shows it can be done.

Adobe could have retuned Animate to do it, but instead let it languish as a niche animation tool for some animation studios to use before trying to kill it.

reply
Those downvoting you have no idea of what you are talking about. Flash was what truly brought multimedia to the internet. You could make complex vector animations so easily in it, and it would only take a few minutes to load on a dialup or ISDN because of its small size (10's or 100's of KB). At one point, it used to power the whole of Youtube (and many other video sites). "Web applications" in this era actually meant something built with Flash. And it did all this on ancient hardware. Flash used to run on 90+ % of internet connected PCs at one point if I remember right. And because of that, you could count on Flash player more than the browsers they ran in. Adobe 100% screwed it up.
reply
I would think:

1) macromedia ->

2) adobe ->

3) steve jobs

I think 2 was the root cause, not #1 or #3.

https://web.archive.org/web/20170615060422/https://www.apple...

That said, I wonder how easy it is to publish on apple? I think of xcode in sort of the same way sj complaining about adobe being cross-platform and slow.

reply
You know you can use Ruffle if you really want Flash right?

https://ruffle.rs

But the only standard you need is WASM. All browsers support it. Use whatever you want to make it. In fact, Ruffle is just a WASM app.

reply
The problem is that, while there's no theoretical barrier to an authoring tool with a Director-like user experience that exports to Wasm, no one has actually written one, and it's not a small amount of work.

(I agree that we're better off without Flash, but this particular problem is real and unsolved.)

reply
Or you can just use PaleMoon browser ( https://www.palemoon.org/ ) and install the original Flash player plug-in in it.
reply
Ruffle is not complete or comprehensive. In my test of a dozen swf ruffle could successfully display about half. Compare to the actual flash plugin Shockwave Flash 11.2 r202 (11.2.202.643) in my retro machine browser which displayed them all perfectly.
reply
What about lightspark?

htps://lightspark.github.io

reply
this is unfortunately, the most revisionist take I can imagine. I don’t mean this in a personal way, mind you but while it may have been magical to publish interactive websites, using flash, that magic is utterly outweighed by the mundane vulnerabilities that flash was riddled with.

It’s safe to say we all miss sites like Homestar runner, and I had a co- worker who generated many meme – worthy flash presentations of his coworkers, which were hysterical. however, flash generated security vulnerabilities on the daily, and unfortunately, these vulnerabilities were very conveniently cross platform. These vulnerabilities, which Adobe couldn’t, or wouldn’t, resolve resulted in many many lost hours fixing virus – and Trojan horse – infested PCs, Macs, and cell phones. Adobe never managed to sandbox flash at all.

I miss a lot of old flash content, and I’m sure many people miss the ease with which you could create interactive content for websites. The fault here lies squarely on Adobe, who wouldn’t fix the situation.

reply
Compared to the best that someone can vibe code? Not to show my age, but we were kids when flash came out. That copy of macro media? I don't know about you. We spent hours and hours and hours with that spend hours and hours and hours with vibecoding and tell me that you really can't accomplish similar shit. Then you just to deploy it you and I might be to smart to just paste your Vercel API key in ChatGPT, but pretend you're 16 right now.

I can tell you how much tsc sucks off the top of my head but what I can't do is tell you to hit ctrl+enter in Claude desktop to play movie.

What kids know today is how magical Claude desktop and ChatGPT are. The deploy story is trivial. just give the AI the key. We can judge someone for being dumb enough to do that, but unless you're selling consulting services, it's not nice to laugh. if you are selling consulting services then let's talk sales channels lol

reply
Yes compared to vibe coded stuff too. And it costed less money.
reply
> "Websites are still inferior to Flash of the early 2000s. It's taken decades and they can only mimic a fraction of its power. And none of its ease."

Somewhat mirrors my experience with all those rubbish non-PDF formats for digital document publishing, e. g. ePub: Often terminally ugly and utterly useless on top of it (not properly citeable, et cetera).

reply