3 ms·
Oh, me too. So much now-obsolete knowledge accumulated! Flash was always going to die someday though, as HTML/JS caught up with it. In the end it was killed (a
by sanitycheck 3y ago
Oh, me too. So much now-obsolete knowledge accumulated!
Flash was always going to die someday though, as HTML/JS caught up with it. In the end it was killed (arguably) prematurely, but it probably wouldn't have lasted more than another 5-6 years anyway.
Silverlight, I think, was worse - only a few years between initial launch and discontinuation. Pretty much every client app based on Silverlight would have had to have been rewritten from the ground up within a couple of years of completion.
I try to learn lessons, in life. One of them is to not rely much on any Microsoft technology that's less than 10 years old.
- keyle 3y agoI remember the transition to WPF apps was awfully painful.
- throwaway_0235 3y ago> Flash was always going to die someday though, as HTML/JS caught up with it. I'm not sure that would happen. I think Flash would evolve to just "compile" to HMTL/JS. IOS/Android could be other targets as well, once they found a way that would not upset the Eye of Apple.
- acdha 3y agoNot if Adobe was developing it. Flash was terrible for performance and battery life, and it was wedded to the classic fixed-size window with a keyboard and mouse. Even Android users who had access hated it. Now, it’s possible that some of that could’ve improved (battery life would’ve been hard due to the scene timing model) but Adobe just isn’t a platform company. They didn’t even want to fix the security problems, much less all of their half-assed APIs - they were even worse than Sun for announcing ambitious frameworks duplicating built-in OS features, shipping the easiest 40%, and then letting it stagnate because there was no way fixing the hard stuff would get them a second keynote.