News for hackers. Stuff that matters.
Re:When SVG almost got network support for raw sockets by lmm on Friday March 31, 2023 @12:56AM (#35382762)
> 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.

Re:When SVG almost got network support for raw sockets by eyelidlessness on Friday March 31, 2023 @01:11AM (#35382866)
Blink (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.

Re:When SVG almost got network support for raw sockets by dontlaugh on Friday March 31, 2023 @06:21AM (#35384878)
Sure, although Blink and WebKit are still much closer than WebKit and KHTML.
Re:When SVG almost got network support for raw sockets by geocar on Friday March 31, 2023 @02:21AM (#35383362)
> 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.

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.
Re:When SVG almost got network support for raw sockets by hnlmorg on Friday March 31, 2023 @02:21AM (#35383369)
We 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.

Re:When SVG almost got network support for raw sockets by lmm on Friday March 31, 2023 @02:58AM (#35383622)
> 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".

Re:When SVG almost got network support for raw sockets by hnlmorg on Tuesday April 04, 2023 @09:19AM (#35439135)
I 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.

Re:When SVG almost got network support for raw sockets by lmm on Tuesday April 04, 2023 @06:17PM (#35446570)
> 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)

I had to put some kind of wrapper in, and I think it was actually using the Linux version of the plugin, but it all worked pretty reliably once it was there.

> 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.

I'm talking about slightly later, when people were pushing "web video" as a replacement for Flash for e.g. YouTube. Flash was more reliable and better supported on FreeBSD for some time, is my recollection. Although honestly straight-up <embed> also worked fine and I never felt that the move away from that was really justified.

Re:When SVG almost got network support for raw sockets by hnlmorg on Thursday April 06, 2023 @02:36AM (#35464966)
I seem to recall the Linux plugin used to ramp up the CPU load. Which wasn’t so much of an issue on desktops but was extremely annoying on laptops where battery life was dependent on heavy CPU throttling and most laptop fans spinning up sounded like jet engines.

As for the early days of web video, I think half the problem was that nobody could agree on what video format to support. Some wanted patented formats while others (namely Firefox) wanted open source formats.

I’m not sure what the end outcome was of all that but it does feel a resolution has at least now been found.

Re:When SVG almost got network support for raw sockets by egberts1 on Friday March 31, 2023 @10:21AM (#35387568)
We 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-time...

Re:When SVG almost got network support for raw sockets by conradev on Friday March 31, 2023 @11:29AM (#35388600)
It did happen eventually: https://github.com/ruffle-rs/ruffle