5 ms·
As someone that helped a little bit in bringing Flash to WebOS, it was a battery stuck because there was no HW acceleration. Additionally, the software was very
by vlovich123 4y ago
As someone that helped a little bit in bringing Flash to WebOS, it was a battery stuck because there was no HW acceleration. Additionally, the software was very very bad. Used a crapton of memory, was really slow, and horribly insecure. Adobe was caught really off guard by mobile and never prioritized flash. If little else, the modern web is infinitely more secure than the flash player and Adobe would never have prioritized it. We also have ~3 major open source browser engines that independently implement the web compared with one closed source vendor. So structurally things are also infinitely healthier. That the web is a cesspool in turns of content is an orthogonal problem that would have always been the case (but also a flash laden website are up way more RAM and CPU than the equivalent html)
- lmm 4y ago> it was a battery stuck because there was no HW acceleration. Additionally, the software was very very bad. Used a crapton of memory, was really slow, and horribly insecure. Surely lack of hardware acceleration and poor implementation are incidental, not fundamental issues. Just as browsers eventually got their own PDF implementations because Adobe's sucked, I expect the same would have happened for Flash eventually. > We also have ~3 major open source browser engines that independently implement the web compared with one closed source vendor. We have WebKit and Gecko, and the latter barely exists on mobile. I'm not convinced we're a lot better off in practice.
- eyelidlessness 4y agoBlink (Chrome/Chromium-derived browsers) is a fork of WebKit but has diverged for many years. To treat them as the same, you should call them KHTML as that’s their common lineage. But that would be obviously absurd. WebKit and Blink are not the same browser engine.
- dontlaugh 4y agoSure, although Blink and WebKit are still much closer than WebKit and KHTML.
- geocar 4y ago> Surely lack of hardware acceleration and poor implementation are incidental, not fundamental issues. Of course not. These are just some of the many many needles of crap that broke Flash. > I expect the same would have happened for Flash eventually. Perhaps you underestimate just how complicated "Flash" is: It's 2023 and despite everything you can do in a modern Web browser with HTML5, SVG, JavaScript, Video and so on, we still don't have a second full reimplementation of Flash. No emulator or converter that preserves all of the authors intentions, not even with a server-side-helper to cover the differences in networking policies between the web and Flash. I still think it would take serious cash/time to do this. And for a large company to do it would risk being sued by Adobe. They promised. I think if Adobe couldn't fix the crap-needles for whatever reason, nobody else could either. Adobe made sure of that. And nobody wants to pay the Adobe tax when Flash hurts users so bad. PDF on the other hand, is easy enough to implement on screens in a month or less, spec-in-hand. Users who use Adobe's PDF reader deserve what they get. > We have WebKit and Gecko, and the latter barely exists on mobile. I'm not convinced we're a lot better off in practice. I do feel a little better off. I remember a time when every flash bug was an opportunity to airdrop malware, just buy an ad and get on every desktop PC in the world for chump change. I had to browse the Web in a VM, back when VM's on workstation PC's were still painfully slow, because I needed the ability to rewind state so often. I really don't miss that. A small number of players working (largely) openly (i.e. we have webkit and gecko's source code!) allowed features to the Web be deployed relatively quickly, and problems fixed fast and usually with the smallest-possible harm. And I think people are sufficiently suspicious of closed-source infrastructure that people (mainly purchasing VPs at big enterprises) will be able to resist any attempts to change that.
- gpvos 4y agoHow far have Blink and Webkit diverged? Do they still take patches from each other?
- carefish 4y agoLovely points you bring to the table, agreed on all fronts. Just wanted to add that there is definitely a decent attempt at creating that implementation though: https://ruffle.rs/ https://ruffle.rs/
- hnlmorg 4y agoWe also have iOS, Android, ChromeBooks, Tizen, macOS, GNU/Linux, games consoles, TVs, tablets, home assistants like Echo Show, and a dozen other platforms I’ve not thought of. Whereas back in the flash days there was basically just x86 desktop Windows and the few other web enabled devices were niche and didn’t properly support Flash. The Dreamcast had a browser (based on IE) but suffered from an ancient version of flash. PDAs were uncommon, also had a browser based on IE, and also suffered from a crippled version of Flash. Smartphones were a few years off and when they did arrive also had a crippled version of Flash (or no support at all). Flash was a format for a different era. An era when Microsoft had suffocated the tech industry. The fact that we can now view basically any website on any hardware is a massive step forward. I agree that the modern era of the web has its problems too (I’m looking at you Google, Facebook, etc) but having been a developer and early adopter of the web, I’d still take modern web technologies over Flash any day of the week.
- lmm 4y ago> Whereas back in the flash days there was basically just x86 desktop Windows and the few other web enabled devices were niche and didn’t properly support Flash. It wasn't quite that bad. I was running FreeBSD at the time and Flash was fine there. In fact I remember for a few years it was easier to have working Flash than working "web video".
- hnlmorg 4y agoI ran FreeBSD too but FreeBSD didn’t have the official Flash plug-in. In fact for a long time Flash didn’t support anything aside IE. Not even Firefox nor Opera (remember that?). And even when Flash did eventually get ported to more platforms, half the time it still required a bunch of jacks to get working (like Firefox using Chome’s Flash plugin) And as good as the 3rd party hacks were, they didn’t work all of the time. I remember a few sites I needed for work which required me jumping onto a Windows VM just to use. There also wasn’t really such thing as “web video”. Flash was the closest we had. There were some other clients supported like Real Player but it was the same problem about having to install their software too.
- egberts1 4y agoWe have four major technologies within web browsers. JavaScript is one. That too in turn also covers six types of JavaScript engine. * Mozilla * Microsoft * WebKit * Adobe * Opera https://egbert.net/blog/articles/javascript-jit-engines-timeline.html https://egbert.net/blog/articles/javascript-jit-engines-time...
- conradev 4y agoIt did happen eventually: https://github.com/ruffle-rs/ruffle https://github.com/ruffle-rs/ruffle
- Evidlo 4y ago> it was a battery stuck Is this an idiom? What does it mean?
- jjtheblunt 4y agoI think it's a typo, the person meant "battery suck" as in drains the battery.
- cyberax 4y agoApparently, the x86 version of Flash was extremely well-optimized and as a result very spaghettified. So even porting to 64 bits took Adobe years of effort. Additionally, the SWF format itself was way ahead of SVG. It still is to some extent: https://open-flash.github.io/mirrors/swf-spec-19.pdf https://open-flash.github.io/mirrors/swf-spec-19.pdf - look at the part that describes shapes, and compare it to SVG. One thing that helped was ability to have shapes with fill on each side of the edge, allowing smoothly joined scenes that can be animated at real-time. All without the use of high-precision math, Flash used integers only with some fixed-point data!
- scrame 4y ago> it was a battery stuck because there was no HW acceleration. Additionally, the software was very very bad. Used a crapton of memory, was really slow, and horribly insecure. You're describing javascript in that era.
- grishka 4y agoThat's the problem with the particular proprietary implementation of flash player. There's nothing inherently bad about the swf format itself.
- acdha 4y agoThat’s like saying there’s nothing wrong with Word because you could just build your own version. Adobe controlled the format and since they didn’t care about quality, performance, security, or tool quality that doomed it. The other big thing which hit Flash was mobile. Rearchitecting it to support the equivalent of the web’s responsiveness was a huge problem which got lost in the “Steve Jobs killed Flash” narrative. Battery life wasn’t the only thing which made it unpopular on mobile – that could have been improved even though some aspects of the platform made that hard – but also the fact that Flash was based around mice and fixed-size displays. Very little of the existing content worked well (often at all) on the mobile devices which did have Flash.
- butlerm 4y agoVector graphics designed for a desktop display or a printed page generally do not work well on small displays unless scaling to fit or scrolling is acceptable. I can hardly imagine what one would do to make something like SVG reflow in a sensible way. Line of business (web) applications often have the same problem, i.e. there is often a display size below which they simply are not usable, and that should be no surprise to anyone.
- numpad0 4y agoWeren’t there tons of devices that use Flash Lite for UI up to that era, in mp3 players and flip phone markets?
- giantrobot 4y agoFlash Lite was not really "Flash". It didn't support older ActionScript, it had extremely limited codec support (relying on a device's hardware support), and was missing a lot of the network features the desktop plugin had. Generally it wouldn't be able to load arbitrary SWFs off the web. Even to run a SWF the developer needed to write to the Flash Lite profile, like targeting a MIDP profile in J2ME. Flash Lite was usually used on the devices you mention as the "app" environment instead of J2ME, BREW, or whatever.