News for hackers. Stuff that matters.
Re:When SVG almost got network support for raw sockets by nntwozz on Thursday March 30, 2023 @11:55PM (#35382356)
Flashback to Steve Jobs' famous "Thoughts on Flash" https://newslang.ch/wp-content/uploads/2022/06/Thoughts-on-F...

It was not well received at the time. Oh how things have changed.

Re:When SVG almost got network support for raw sockets by lmm on Friday March 31, 2023 @12:08AM (#35382436)
Have they? I would say the subsequent ~10 years of the web have vindicated Flash. HTML5 video hasn't made websites lighter or less annoying - quite the opposite (indeed video ads are a worse problem than Flash ads ever were). Meanwhile creativity and innovation on the web have taken a hit. 10+ years on there's still nothing that allows a lone auteur to produce a web experience as easily and effectively as you could with Flash (it seems to be possible to match Flash, a la the NYT's Snow Fall or the previous Madogatari intro, but not at a level that's accessible to an individual creator), and we're all worse off for it.
Re:When SVG almost got network support for raw sockets by vlovich123 on Friday March 31, 2023 @12:20AM (#35382510)
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)
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
Re:When SVG almost got network support for raw sockets by Evidlo on Friday March 31, 2023 @01:25AM (#35382964)
> it was a battery stuck

Is this an idiom? What does it mean?

Re:When SVG almost got network support for raw sockets by jjtheblunt on Friday March 31, 2023 @01:35AM (#35383041)
I think it's a typo, the person meant "battery suck" as in drains the battery.
Re:When SVG almost got network support for raw sockets by cyberax on Friday March 31, 2023 @01:49AM (#35383111)
Apparently, 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 - 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!

Re:When SVG almost got network support for raw sockets by nly on Friday March 31, 2023 @03:23AM (#35383772)
Ah, yes. I remember the days of using b nspluginwrapper to load the 32 bit flash plugin in a 64 bit browser on Linux...
Re:When SVG almost got network support for raw sockets by tinus_hn on Friday March 31, 2023 @04:17AM (#35384153)
There was also bug for bug compatibility with every old version ever released. Hard to support and impossible to port.
Re:When SVG almost got network support for raw sockets by scrame on Friday March 31, 2023 @01:51AM (#35383123)
> 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.

Re:When SVG almost got network support for raw sockets by grishka on Friday March 31, 2023 @02:13AM (#35383301)
That's the problem with the particular proprietary implementation of flash player. There's nothing inherently bad about the swf format itself.
Re:When SVG almost got network support for raw sockets by acdha on Friday March 31, 2023 @08:44AM (#35386252)
That’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.

Re:When SVG almost got network support for raw sockets by butlerm on Friday March 31, 2023 @01:56PM (#35390678)
Vector 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.
Re:When SVG almost got network support for raw sockets by numpad0 on Friday March 31, 2023 @02:25AM (#35383395)
Weren’t there tons of devices that use Flash Lite for UI up to that era, in mp3 players and flip phone markets?
Re:When SVG almost got network support for raw sockets by giantrobot on Friday March 31, 2023 @03:17PM (#35392015)
Flash 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.

Re:When SVG almost got network support for raw sockets by rektide on Friday March 31, 2023 @12:17AM (#35382493)
This keeps coming up, but it keeps seeming hogwash & backwards.

There are dozens & dozens of really really good html/svg animation products that give Flash like capabilities. But there's vastly less interest in this stuff today. Fun/simple/quirky Flash-like stuff isn't nearly as unique or novel, now that we have much more upscale products & experiences. It was a magical time & Flash helped, but we've changed & these rose-colored glasses views on Flash never point out all the myriad of ways it was awful, choppy, poorly integrated, quirky to work with, & otherwise difficult.

If you want higher there are hundreds of web-dev targeting game dev systems which can be put to use. Many of these actually do have popularity. In spite of their being good Flash-ish animation toolkits, it doesn't feel like there's a ton of demand or clear winners. It's hard to imagine what we'd want it for today.

Re:When SVG almost got network support for raw sockets by EamonnMR on Friday March 31, 2023 @12:37AM (#35382629)
The loss of the mouse and keyboard as primary input devices is an underrated part of why everything feels worse now compared to the flash era. Web is a very different target now than it was. Also, the flash game ecosystem was intertwined with the animation ecosystem and the advent of streaming full motion video devalued animation skills.

Anyway nowdays we have Godot and Unity which are both very nice. But there were definitely lost years where amateur gamedev was less accessable.

Re:When SVG almost got network support for raw sockets by grishka on Friday March 31, 2023 @02:19AM (#35383348)
> The loss of the mouse and keyboard as primary input devices is an underrated part of why everything feels worse now compared to the flash era.

It's okay to say "please visit this from your computer" when someone opens something that requires a keyboard from a phone.

> Anyway nowdays we have Godot and Unity which are both very nice. But there were definitely lost years where amateur gamedev was less accessable.

The barrier to entry is considerably higher with these things. They require programming from the beginning. The coolest part about Flash was that you could get started without writing a single line of code. Then you could build up your understanding of the thing iteratively. You could build a simple quest-type game with just one line of code that you copy-pasted from somewhere, `goToAndStop(frameNumber)`. And then you go from there — variables, flow control, all that. Flash got a sizable number of people interested in programming. This ease of use is extremely important and it's still unmatched by any purported modern replacements.

Re:When SVG almost got network support for raw sockets by yathaid on Friday March 31, 2023 @08:17AM (#35385927)
>> It's okay to say "please visit this from your computer" when someone opens something that requires a keyboard from a phone.

Unless you have a captive audience, like forced to use enterprise users, this is not a winning strategy for any internet based product.

Also, the assumption that everyone will have devices in two form factors is, and I am being charitable here, naive.

Re:When SVG almost got network support for raw sockets by lmm on Friday March 31, 2023 @12:29AM (#35382576)
I think the demand is there, but you underestimate how much difference the tiny inconveniences make. Like, maybe there's stuff out there that can do the same thing, but the people who are just starting out don't know where it is (hell, I'm an experienced programmer and I don't know where it is) or what to pick up. A lot of those great Flash works were made by literal schoolkids, or more often by young adults who'd got their start as schoolkids and gradually refined their craft, because you could just pick up Flash and start doing things, and kids did. From what I hear maybe Roblox is filling the same niche now, but that's only happened in the last few years, and for all that Flash was notionally proprietary and poorly-integrated with the open web, having it right there in your browser was still a win.
Re:When SVG almost got network support for raw sockets by thrashh on Friday March 31, 2023 @03:20AM (#35383757)
I wouldn’t touch any of those game systems with 10-ft pole. Their user bases are too small to be worth using. They also don’t at all compare to the Flash IDE.

Flash was great because it was popular and supported with the weight of a big company that loved its own child. Their love translated to great tooling.

Whereas the web is “community-owned” and community/committee-designed things rarely get super cool and fleshed out things like well-integrated for-everyone tooling. Instead, you mostly get self-serving projects that serve the creator’s own need primarily. Usually half-baked. And it’s not interoperable with anything else.

Re:When SVG almost got network support for raw sockets by illiarian on Friday March 31, 2023 @04:08AM (#35384097)
> There are dozens & dozens of really really good html/svg animation products that give Flash like capabilities.

And those are?

> now that we have much more upscale products & experiences.

And those are?!!

Re:When SVG almost got network support for raw sockets by JoeyJoJoJr on Friday March 31, 2023 @07:49AM (#35385613)
I was a Flash developer and have searched everywhere for a comparable tool. None exists. Recently I have worked on interfaces for touch screen kiosks, and digital signage. Flash was excellent for these kinds of projects and 10 years later nothing compares.
Re:When SVG almost got network support for raw sockets by stuaxo on Friday March 31, 2023 @09:08AM (#35386578)
The authoring tool was a big part of why so much flash stuff got made.
Re:When SVG almost got network support for raw sockets by kitsunesoba on Friday March 31, 2023 @12:44AM (#35382692)
Flash games and animations were cool, but it seemed like for every cool thing made with flash there was also a terrible SWF-as-a-website that didn't play nice with browser window resizing and was more frustrating to use than even the worst modern JS-mudball monstrosities. At least content blocker extensions and reader mode can somewhat salvage bad sites… with flash pages you got the whole thing or nothing.
Re:When SVG almost got network support for raw sockets by philsnow on Friday March 31, 2023 @01:03AM (#35382800)
Oddly enough your comment made me think of electron apps vs native apps, because they are usually impenetrable to accessibility APIs so they appear as completely opaque apps with no a11y affordances.
Re:When SVG almost got network support for raw sockets by Earw0rm on Friday March 31, 2023 @03:01AM (#35383635)
Seems like a solvable problem in the medium term - Electron apps are, in effect, a web page; build an accessible page, the Electron runtime _should_ be able to join the dots same as a full browser does.
Re:When SVG almost got network support for raw sockets by giantrobot on Friday March 31, 2023 @03:24PM (#35392117)
It seems like a lot of frameworks used with Electron are the "reinvent every HTML tag as a component with divs" variety. So unless a developer hangs a bunch of event handlers off some widget they don't have default handlers for a lot of accessibility. If they used a real tag they'd get a bunch of free accessibility/functionality but instead they use components.
Re:When SVG almost got network support for raw sockets by kitsunesoba on Friday March 31, 2023 @11:14AM (#35388334)
To me that highlights how important it is for UI frameworks of all types to have accessibility affordances not only built in, but as one of the pillars of their designs. That makes it so even apps developed without any regard to accessibility are reasonably accessible by default.

This doesn't gel well with the bring-your-own-everything nature of the web, unfortunately. Even if you look just at React there's 50 ways to build the same thing, which I'm sure makes rolling in accessibility that "just works" across all React apps without additional effort from the developer extremely difficult. It's much more practical with UI frameworks that are strongly opinionated with only a single well-supported "happy path" for most things.

Re:When SVG almost got network support for raw sockets by paultopia on Friday March 31, 2023 @01:50AM (#35383117)
This brings back memories. 20 years ago, I was managing a band in New Orleans (by an amazing coincidence I'm in New Orleans for a 2 day trip now), and I decided to make them a website. It being 2003, I did the website in flash, and with my zero coding skills at the time ... it still came out pretty awesome. Wish that still existed.
Re:When SVG almost got network support for raw sockets by wink on Friday March 31, 2023 @09:18AM (#35386709)
Technically it's not the fault of the videos that web standards now allow easy embedding, it's still the people abusing it to show you video ads. Just saying it's worse than Flash... it's like saying browsers should not show non-animated images because you can have ad banners.
Re:When SVG almost got network support for raw sockets by lmm on Friday March 31, 2023 @10:51PM (#35396574)
Sure, but that was an argument used by anti-flash people at the time. (And if anything it was a lot easier to block flash on some pages than block web video on some pages - indeed I remember some browsers started to be click-to-start-flash by default).
Re:When SVG almost got network support for raw sockets by Pulcinella on Friday March 31, 2023 @12:58PM (#35389924)
I don’t get the love for Flash on Hacker News. It’s very odd to me to see people say they prefer Adobe’s proprietary format and software to the open web.
Re:When SVG almost got network support for raw sockets by lmm on Friday March 31, 2023 @10:52PM (#35396583)
I'm all for open source but I don't let that blind me to product quality. Same thing with Discord - yes, I'd definitely prefer an open system, but if this specific proprietary thing has a better UX then we should be honest about that.
Re:When SVG almost got network support for raw sockets by gumby on Friday March 31, 2023 @12:01AM (#35382394)
Well it wasn't received well by Adobe, who had by then bought Macromedia, nor by people who had tied their wagon to Flash. But Flash was pretty horrible even on most laptops and even many desktops of the day, and was a security nightmare.

The complainers were loud, but I think the majority of people who cared (99% of humanity didn't even notice, of course) were muttering "amen brother!"

Re:When SVG almost got network support for raw sockets by exsf0859 on Friday March 31, 2023 @12:26AM (#35382547)
Besides animation and games, Flash was also used for streaming video and video conferencing.

iPhone customers were so desirable that, over time, the video streaming sites had to support Apple's video streaming format. They would have also supported Apple's video conferencing app, but I think Apple was unable to open-source the protocols for the video conferencing format, due to patent issues.

Re:When SVG almost got network support for raw sockets by duskwuff on Friday March 31, 2023 @12:50AM (#35382727)
> had to support Apple's video streaming format

It's a little weird to call an open standard (like H264) "Apple's format".

Re:When SVG almost got network support for raw sockets by Evidlo on Friday March 31, 2023 @01:31AM (#35382997)
H264 isn't open though, depending on your definition of open
Re:When SVG almost got network support for raw sockets by duskwuff on Friday March 31, 2023 @01:36AM (#35383046)
Fine, pretend I said "industry standard" then. Either way it wasn't something Apple made.
Re:When SVG almost got network support for raw sockets by lultimouomo on Friday March 31, 2023 @02:14AM (#35383309)
H264 is not a streaming format. HLS is, and it is pretty much "Apple's format". It's pretty backwards, and everyone was forced to support it because it was the one streaming format you could use in iStuff.
Re:When SVG almost got network support for raw sockets by geocar on Friday March 31, 2023 @02:35AM (#35383455)
> It's pretty backwards

I think it's pretty clever.

There are a lot of usability issues with firewalls and proxies that make implementing other streaming protocols very difficult, and the HLS design basically causes the implementer to adopt a pattern that is resilient to those problems.

Networks got a lot better after Covid had everyone work from home so IT had to sort the hot-path out for videoconferencing. Nowadays I think WebRTC would be fine, but in 2009 I think HLS was pretty smart.

Re:When SVG almost got network support for raw sockets by lultimouomo on Friday March 31, 2023 @04:54PM (#35393510)
I am comparing HLS with other HTTP-based streaming formats - DASH and SmoothStreaming. They definitely have their issues (DASH in particular is the epitome of the second system syndrome) but they fix the two most glaring issues with HLS: separate manifests and non-aligned segments.

Source: I write an HTTP streaming client library for a living.

Re:When SVG almost got network support for raw sockets by geocar on Saturday April 01, 2023 @01:21AM (#35397387)
How can HLS be a move backwards if it came out before DASH and SS?

Why do you think users care about “separate manifests and non-aligned segments” more than the video playing and not stalling and having to refresh?

Re:When SVG almost got network support for raw sockets by lultimouomo on Saturday April 01, 2023 @02:21PM (#35402617)
SS came out in 2008, HLS in 2009.

Separate manifests and non aligned segments have a real impact on the ability of the client to switch qualities in responsabilità to bandwith change, and this to avoid stalling.

BTW, when I say "HLS is pretty backwards" I mean designed unergonomically and without clear requirements in mind, not a step back from what existed before. I would guess this is because the original specification was something like "whatever Major League Baseball can easily stream from their existing setup" (see the various Pantos drafts that ultimately became RFC8216)

Re:When SVG almost got network support for raw sockets by geocar on Saturday April 01, 2023 @03:18PM (#35403188)
> SS came out in 2008, HLS in 2009.

Oh you're quite right! I was definitely mis-remembering silverlight.

> Separate manifests and non aligned segments have a real impact on the ability of the client to switch qualities in responsabilità to bandwith change, and this to avoid stalling.

I don't know if that's actually true. I sell ads, so I'm collecting delivery data on billions of devices, but only over the crappy internet that has a lot of ads on it, and at least for short videos, and the long videos after the places those short videos are, HLS stalls less than Dash and silverlight: HLS publishers make more money.

I would be interested in learning more.

> I mean designed unergonomically and without clear requirements in mind

I can easily agree with that. I misinterpreted what you meant by "backwards" as referring to the progress of the experience.

Re:When SVG almost got network support for raw sockets by mikeryan on Friday March 31, 2023 @10:18AM (#35387521)
HLS was a significant improvement over other options for live (rtmp) and adaptive bitrate solutions.

I mean it could be delivered via HTTP and was was built off of open standards for the manifest files. (HLS just breaks down mp4 files into smaller chunks and lists them in a text manifest file based on the mp3 playlist spec) *

It significantly moved the needle forward on how video was delivered and did so in a standards based way until DASH came along.

Not sure why the hate here for their “proprietary standard” it wasn't proprietary - just no one was using it and it eventually became a defacto standard because it “just works”.

* I know I’m simplifying this.

Re:When SVG almost got network support for raw sockets by duskwuff on Friday March 31, 2023 @03:07PM (#35391855)
In particular, HLS allows existing HTTP load balancers and content distribution networks to be reused for video streaming -- you don't need to build or buy application-specific infrastructure to use it, as you would have with previous streaming protocols.
Re:When SVG almost got network support for raw sockets by giantrobot on Friday March 31, 2023 @03:48PM (#35392516)
Back when streaming meant RTP/RTSP the MPEG-4 file format, and the way bitstreams were packaged, definitely supported streaming. Not only does the format have a sample mapping table but it supports streaming hint tracks to give a server packetizing hints.

Scaling RTSP was difficult because it required two way signaling with the server and for the server to maintain client state. Using HTTP instead allowed for stateless servers in a CDN to easily scale and pushed stream negotiation onto the client. Besides simplifying the server side of streaming it made it much easier for clients switching from cellular to WiFi to maintain a stream, RTSP (and protocols like it) can't really handle clients switching addresses mid-stream.

Re:When SVG almost got network support for raw sockets by Groxx on Friday March 31, 2023 @12:17AM (#35382492)
It was divisive, but I wouldn't say "not well received". The "Flash deserves death" camp was very large and very, very happy that someone with power was finally calling them out on their horrific security record.

Losing the high-quality authoring environment, without anyone producing something competitive, was a pretty big blow. But for the rest, I'm quite glad to see invasive browser plugins disappear.

Re:When SVG almost got network support for raw sockets by wlesieutre on Friday March 31, 2023 @09:27AM (#35386827)
Maybe not well received from Windows users?

It had some fun games but on the Mac side it was always an unstable dumpster fire. Having the iPhone browser start to push people away from making entire Flash-based websites so they could play music and crash my browser was a godsend.

Re:When SVG almost got network support for raw sockets by dutzi on Friday March 31, 2023 @12:59PM (#35389943)
There was also the Adobe Loves Apple campaign

https://www.fastcompany.com/1646594/adobe-launches-hearts-an...

Re:When SVG almost got network support for raw sockets by twelvedogs on Friday March 31, 2023 @09:57PM (#35396255)
It was incredibly well received by web devs