3 ms·
> If no browsers had support out of the box This was the original state of Flash and Java. This is when they grew. Trust me when I say: This would not be a
by MaulingMonkey 10y ago
> If no browsers had support out of the box
This was the original state of Flash and Java. This is when they grew. Trust me when I say: This would not be a problem.
> and even plugins were hard to come by (browsers could actively prevent running anything it thinks is a flash plugin..)
This is no longer Adobe 'kill'ing Flash Player, and also how you get a bunch of pissed users switching browsers or sticking to legacy versions. This shit right here is how you get IT departments sticking to IE 6.
Although, this is perhaps a golden age of open source. Maybe we'd see hostile forks instead!
And, of course, iOS Safari has already 'kill'ed Flash in this sense. On the one hand, it's added some pressure to transition to new tech stacks. On the other, since we're still asking questions about how to kill Flash Player, it clearly didn't do the job ;)
- alkonaut 10y agoI think the current pace of the death of flash is good enough. It also seems entirely fine if corporations or some individuals have to bend over backwards to keep their legacy apps running - that's how XP mode on windows still ran 16bit apps for years after ms stopped shipping a Windows version with native support for 16bit apps. The problem with flash is that the people who get in trouble through exploits had no intention to run flash at all. Browsers could start by disabling it by default and only enabling after modifying well hidden settings that would be no problem for a legacy intranet or kiosk scenario, but would serve my mother in law well.