Re:When SVG almost got network support for raw sockets
by gpvos on Friday March 31, 2023 @03:19AM
(#35383748)
How far have Blink and Webkit diverged? Do they still take patches from each other?
Re:When SVG almost got network support for raw sockets
by carefish on Friday March 31, 2023 @06:25AM
(#35384897)
Lovely 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/
Re:When SVG almost got network support for raw sockets
by geocar on Friday March 31, 2023 @07:31AM
(#35385451)
I'll watch out for ruffle (60% of AVM2 sounds promising!). Thanks for that.
Re:When SVG almost got network support for raw sockets
by Lex-2008 on Friday March 31, 2023 @06:48AM
(#35385069)
Thanks for a nice writeup! Regarding "for a large company to do it would risk being sued by Adobe" - what do you know about "Pepper flash plugin", which was shipped with Chrome at some time? Back then I had an impression that it was an alternative implementation of flash player, but developed by Google.
Re:When SVG almost got network support for raw sockets
by geocar on Friday March 31, 2023 @07:29AM
(#35385434)
I think Pepper was just the name of Google's extension API, and so Pepper Flash was just a (re)packaging of the flashplayer artefacts from Adobe. My memory of this was that it was pitched (to users) as a "safer" flash, since it could take advantage of Google's isolation/sandboxing features, but I don't have any special knowledge here: I just made a shittonne of flash stuff back in the day.
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.