News for hackers. Stuff that matters.
Re:Current state of AV1 codec playback support – Oct '22 by throwup on Thursday October 20, 2022 @07:43PM (#33282348)
The only solution I see is the FTC stepping in. I don't understand why they're sitting on their hands. What Microsoft did in the 90s was pale by comparison—they just bundled some extra software. By contrast Apple today is locking down their platform and explicitly decreeing that nobody is permitted to compete with them. It's amazing how brazen it is.
Re:Current state of AV1 codec playback support – Oct '22 by MBCook on Thursday October 20, 2022 @08:25PM (#33282661)
Apple supports standards they don’t own like h264 and h265. Why should they be forced to support this particular standard?

Do we want the government dictating which video encoding standards we have to use?

It’s not Apple is only allowing QuickTime, their fully owned protocol that others must license from them, and nothing else.

What is Apple doing on this issue that would be an anti-trust issue?

Re:Current state of AV1 codec playback support – Oct '22 by ZeroGravitas on Thursday October 20, 2022 @08:39PM (#33282752)
Apple do literally own necessary parts of those standards, and recieve royalties for them.
Re:Current state of AV1 codec playback support – Oct '22 by bagels on Thursday October 20, 2022 @08:31PM (#33282696)
Av1 helps google and other competitors. It doesn't help apple much.
Re:Current state of AV1 codec playback support – Oct '22 by MBCook on Thursday October 20, 2022 @08:43PM (#33282768)
I mean it may save them bandwidth on Apple TV+ or iTunes TV/movie purchases. But it seems they’ve chosen not to bother.

Maybe all the re-encoding would negate the benefits for them?

Maybe they didn’t think it was enough of an improvement over h264. Maybe they bet on h265 and it worked out well enough (for them) or it didn’t but they figure by the time they got everything set for VP1 something better will be ready.

Who knows.

Re:Current state of AV1 codec playback support – Oct '22 by FireGrey on Thursday October 20, 2022 @09:37PM (#33283234)
I believe their main reasoning for not supporting AV1 would be the lack of hardware decoding on their chips.

A minor improvement in network bandwidth and storage costs wouldn't be as high a priority as "up to 16 hours video playback (streamed)" on the iPhone 14.

Sure they could optionally support it in Safari without hardware decoding, but a service like YouTube will want to negotiate the lower bandwidth protocol over one that will make the device's battery last longer.

Maybe the licensing cost of h265 works out better for them than rushing out AV1 decode support on their chips or lowering the average battery life of their devices.

Re:Current state of AV1 codec playback support – Oct '22 by MBCook on Thursday October 20, 2022 @11:12PM (#33284043)
That would certainly have been the argument at first. Battery life is EVERYTHING.

But Netflix announced they would be using it in 2016. YouTube started using in 2018, the year the standard hit 1.0.

Apple had plenty of warning and time to get the necessary hardware acceleration blocks available by now. Chips have multi-year timelines but it’s been 4+ years.

Now on the other side, Netflix actually started using it in early 2020/late 2021, depending on device. YouTube rolled it out wide in 2020. Twitch is working on it.

So Apple is at most 2 years behind the content. It’s not like it’s been 5+. And if they decided to wait to see how those early rollouts went due to hardware timelines it might make sense support only appears to be coming now (based on someone pointing out AV1 shows up now in the AVPlayer framework documentation).

Re:Current state of AV1 codec playback support – Oct '22 by alwillis on Thursday October 20, 2022 @11:54PM (#33284330)
I believe their main reasoning for not supporting AV1 would be the lack of hardware decoding on their chips.

I doubt it.

Apple Silicon is more than fast enough to decode AV1 in software. Sure, the battery life won’t be as good but there are other trade-offs that can be made.

Their latest chips were developed before AV1 had gained enough traction to be concerned about. I suspect that future M2 and M3 and A-series SoCs will have hardware decoding for AV1 built-in.

In the meanwhile, a future version of macOS Ventura and iOS 16 will have AV1 support; it’s just going to take a little longer. They probably want to roll it out simultaneously on iOS, macOS, tvOS, and iPadOS.

Re:Current state of AV1 codec playback support – Oct '22 by vetinari on Friday October 21, 2022 @04:46AM (#33285971)
When AMD/Nvidia/Intel and Samsung/Mediatek/Rockchip/etc were able to put AV1 blocks into their chips, I'm sure Apple would be capable of doing the same -- if they wanted. Now it looks that they do not want.
Re:Current state of AV1 codec playback support – Oct '22 by fyzix on Thursday October 20, 2022 @08:45PM (#33282777)
Your argument is a straw man, he's saying that apple should be force to allow competing browser engines on iOS so other vendors can support what they don't want to...
Re:Current state of AV1 codec playback support – Oct '22 by tambourine_man on Thursday October 20, 2022 @08:53PM (#33282832)
So you are saying there are no advantages to a closed platform, no place in the world for it and it shouldn't be allowed by the government to exist.

Because it's not like there are no alternatives.

If there was no Android, I'd say yeah, regulate away.

Re:Current state of AV1 codec playback support – Oct '22 by Gigachad on Thursday October 20, 2022 @10:29PM (#33283749)
Any time a statement starts with “so you are saying …” the answer is no. It’s a phrase entirely used for building strawmen.
Re:Current state of AV1 codec playback support – Oct '22 by tambourine_man on Thursday October 20, 2022 @10:34PM (#33283777)
Which is what the grandparent is being accused of. I guess it’s strawmen all the way down.
Re:Current state of AV1 codec playback support – Oct '22 by girvo on Thursday October 20, 2022 @11:30PM (#33284172)
If we all accuse each other of building strawmen, we don’t have to interact with each others actual arguments. Kind of neat, in a sad way.
Re:Current state of AV1 codec playback support – Oct '22 by throwup on Thursday October 20, 2022 @08:49PM (#33282806)
The issue raised is not about video codecs, but about browsers. Apple is using their market position to artificially prevent Safari from being competed against by other vendors—that is classic antitrust behavior.

For comparison, imagine Microsoft banned all browser engines other than EdgeHTML from running on Windows. Would you find that acceptable?

Re:Current state of AV1 codec playback support – Oct '22 by MBCook on Thursday October 20, 2022 @08:53PM (#33282829)
This is an article about video codecs. I interpreted the above comments as complaining Safari was a problem for not supporting this video codec.

So my comment was about their video codec policy.

Re:Current state of AV1 codec playback support – Oct '22 by MobiusHorizons on Thursday October 20, 2022 @09:26PM (#33283112)
You may not be aware, but chrome does exist on iOS, but even so, it is actually running the safari rendering engine because apple prevents other browser engines from running. This effectively prevents chrome or Firefox from offering a browser with av1 support (as far as I am aware) so the browser engine is relevant to the codec policy discussion.
Re:Current state of AV1 codec playback support – Oct '22 by threeseed on Friday October 21, 2022 @12:08AM (#33284395)
I don't believe Apple has banned alternative engines.

It's just that they don't allow JIT code execution for security reasons which is needed for a comparatively performant engine.

Re:Current state of AV1 codec playback support – Oct '22 by Jasper_ on Friday October 21, 2022 @12:45AM (#33284607)
Yes, they have banned alternative engines.

https://developer.apple.com/app-store/review/guidelines/#2.5...

> Apps that browse the web must use the appropriate WebKit framework and WebKit Javascript.

Re:Current state of AV1 codec playback support – Oct '22 by enkrs on Friday October 21, 2022 @03:06AM (#33285336)
Which is the reason why I choose iOS: I trust Apple to implement the integrations in the WebView for best battery life. To get new OS features in the browser right away. Would Google Chrome implement picture-in-picture on the iPhone if they were running their own engine?

I use Firefox on iOS for the password and tab sync integration, and am supper happy that it’s using the WebKit framework. I care about the iOS experience more than some video codec support.

Re:Current state of AV1 codec playback support – Oct '22 by vetinari on Friday October 21, 2022 @04:04AM (#33285680)
If the other browsers could implement their engines, you would still have the option not to install them.

Since they can not do it, you don't have that option.

Re:Current state of AV1 codec playback support – Oct '22 by alwillis on Friday October 21, 2022 @04:29PM (#33292690)
If the other browsers could implement their engines, you would still have the option not to install them.

So it’s okay for user who (in theory) installed a 3rd party browser on iOS to have a worse experience and potentially make themselves vulnerable to malware? That’s exactly what Apple doesn’t want.

Re:Current state of AV1 codec playback support – Oct '22 by paulryanrogers on Friday October 21, 2022 @09:11PM (#33294696)
Or potentially offer a more secure browser than Safari
Re:Current state of AV1 codec playback support – Oct '22 by dmitriid on Friday October 21, 2022 @03:32AM (#33285491)
Given that Chrome abuses its market position to ram through and continuously release hundreds of Chrome-only non-standards I view this as a net positive.
Re:Current state of AV1 codec playback support – Oct '22 by kersplody on Thursday October 20, 2022 @08:57PM (#33282858)
Apple might have made a deal with one or more major h.265 patent holders that discourages them from fully supporting av-1, similar to how Google pays apple nine digits a year to keep Google search default in the Apple ecosystem.

Court action could compel any deal like this to be made public.

Re:Current state of AV1 codec playback support – Oct '22 by MBCook on Thursday October 20, 2022 @09:24PM (#33283082)
Honestly, being Apple, it could 100% be a “screw Google, it doesn’t hurt us” move without any direct financial incentive.

They’ve done it many times before (though usually in the Steve Jobs era).

Re:Current state of AV1 codec playback support – Oct '22 by hatware on Friday October 21, 2022 @02:16AM (#33285083)
> similar to how Google pays apple nine digits a year

I couldn't believe this and looked it up. It's $9 billion. Which is ten digits.

Good god.

Re:Current state of AV1 codec playback support – Oct '22 by majormajor on Thursday October 20, 2022 @08:45PM (#33282782)
> What Microsoft did in the 90s was pale by comparison—they just bundled some extra software

nah........ that's not true

Re:Current state of AV1 codec playback support – Oct '22 by derefr on Thursday October 20, 2022 @09:07PM (#33282941)
> By contrast Apple today is locking down their platform and explicitly decreeing that nobody is permitted to compete with them.

Microsoft got in trouble for anti-competitive practices with IE, because they were tightly integrating their OS with their browser in ways that meant that their browser was uniquely enabled by the OS to do things that third-party browsers couldn't do (not having access to the same APIs), thus using their position in the OS market to steal browser market-share away from third-party browser companies like Netscape, in ways those browser companies could do nothing to respond to.

In contrast, on iOS, there's nothing Safari can do that third-party browsers can't. Third-party browsers do exactly the same things Safari does, rendering-engine-wise — no more, no less. And meanwhile, they all do more than Safari does UI-wise. There's nothing Apple is doing to bias users of iOS in favor of Mobile Safari, such that it steals market-share away from competing browsers. Instead, their OS is just ruining the browser experience for everybody, equally. That's not anti-competitive — it's just dumb. :)

Re:Current state of AV1 codec playback support – Oct '22 by MobiusHorizons on Thursday October 20, 2022 @09:20PM (#33283045)
Apple blocks allocating executable memory which is necessary in order to create jit compilers, which are necessary for JavaScript engines to run at acceptable speeds. This restriction does not apply to safari’s js engine though.
Re:Current state of AV1 codec playback support – Oct '22 by derefr on Thursday October 20, 2022 @09:49PM (#33283356)
But nor does the restriction apply to WKWebViews. Which any browser that only cares about the UI part can just use and be done with it.
Re:Current state of AV1 codec playback support – Oct '22 by eyelidlessness on Thursday October 20, 2022 @10:09PM (#33283548)
I’ve implemented a WKWebView for a purely personal app with very specific but very minimal requirements and… “just” is doing a lot of heavy lifting here. You can “just” use the API and you get a fully functional web browser without any UI, but you certainly aren’t going to attach any meaningful custom UI to it that way without digging deep not just into internals at the binding level but at the WebKit level. I’m not saying it’s a bad design either, but it’s definitely not a trivial investment.
Re:Current state of AV1 codec playback support – Oct '22 by derefr on Friday October 21, 2022 @01:37PM (#33290781)
Don't want to be snide, but you're talking about the high barrier-to-entry for implementing a nice, customized WKWebView in a project that isn't a web browser. In such a case, the WKWebView brings with it a bunch of complexity that wasn't already there otherwise.

If your project is itself a web browser, then all that complexity is already inherent to the project, whatever you choose to build it with. It's just that the "digging deep" would be in the docs for how to glue Apple's low-level DOM/JS/etc library frameworks together in mostly-undocumented ways; rather than in the docs for how to feed WKWebView the right delegate logic in just the right place to get it to do something that'd be easy if you were directly doing it yourself.

Re:Current state of AV1 codec playback support – Oct '22 by eyelidlessness on Friday October 21, 2022 @11:54PM (#33295548)
Didn’t take it as snide but even just the delegated logic isn’t so simple. Most of my personal project was just a specialized browser, and really basic functionality was much more complex than I’d hoped. I got it good enough to use and haven’t maintained it since because it was just for my own use, so maybe the APIs have become less complex since.
Re:Current state of AV1 codec playback support – Oct '22 by tambourine_man on Thursday October 20, 2022 @09:22PM (#33283068)
Microsoft had 95% of the PC market share with Windows. Regulating a monopoly is the government's job.

That is not the case at all for iOS. Android is a very healthy market and a viable alternative.

Re:Current state of AV1 codec playback support – Oct '22 by isthatright4 on Thursday October 20, 2022 @09:52PM (#33283389)
Depends how you see the relevant market. You could define the market as browsers for iPhones, instead of browsers for all phones. After all, it’s not like users switch readily between different phones for different apps. There’s a whole body of case law on what the relevant market is. The gist is that it turns on substitutability, but it’s more complex and flexible. Easy knob to turn to account for tech platform dynamics.
Re:Current state of AV1 codec playback support – Oct '22 by tambourine_man on Thursday October 20, 2022 @10:09PM (#33283550)
Switching friction is not the same as a monopoly. The distinction is not that hard to draw and I think we should regulate the latter, not the former.
Re:Current state of AV1 codec playback support – Oct '22 by isthatright4 on Thursday October 20, 2022 @11:06PM (#33284000)
If the friction is high enough, antitrust law has always seen that as bearing on the definition of the relevant market. You can’t lock people in and then start charging monopoly prices with impunity. One issue is what happens when the stickiness is mostly psychological friction instead of something that an economist analyzing rational action would see as a barrier. These are laws for people, after all, not for hypothetical rational beings.
Re:Current state of AV1 codec playback support – Oct '22 by scarface74 on Thursday October 20, 2022 @09:18PM (#33283030)
Again absolutely nothing changed with respect to IE in the US as a result of the FTC case.
Re:Current state of AV1 codec playback support – Oct '22 by derefr on Thursday October 20, 2022 @09:29PM (#33283141)
Who said it did? The precedent people are always citing is that the FTC cared to sue Microsoft for doing it; not that anything came of it.
Re:Current state of AV1 codec playback support – Oct '22 by scarface74 on Thursday October 20, 2022 @09:34PM (#33283194)
And that’s about as useless as the EU caring to protect users privacy and writing a 99 section 11 chapter law and the only thing users got were cookie pop ups.
Re:Current state of AV1 codec playback support – Oct '22 by alwillis on Thursday October 20, 2022 @11:35PM (#33284200)
not that anything came of it.

You’re joking, right?

The free and open web, to the extent we have it, only exists today because Microsoft wasn’t allowed to force IE, Active X, Silverlight and the rest of their technologies down everyone’s throat. Oh, and JScript [1], their proprietary version of JavaScript would have been the industry standard.

We wouldn’t have the W3C or WHATWG creating open standards for the web had Microsoft been allowed to essentially turn the web into another Microsoft runtime environment.

[1]: https://en.wikipedia.org/wiki/JScript

Re:Current state of AV1 codec playback support – Oct '22 by scarface74 on Friday October 21, 2022 @12:14AM (#33284431)
> The free and open web, to the extent we have it, only exists today because Microsoft wasn’t allowed to force IE, Active X, Silverlight and the rest of their technologies down everyone’s throat. Oh, and JScript [1], their proprietary version of JavaScript would have been the industry standard

The justice department at no point stopped Microsoft from bundling IE with Windows.

Besides that, up until 2008-2010, the “free and open web” was littered with proprietary Flash apps. It wasn’t until Apple refused to support Flash on iPhones that anyone started worrying about standards.

> Microsoft been allowed to essentially turn the web into another Microsoft runtime environment.

Nothing that the FTC did prevented that. No part of the consent decree caused MS to behave any differently with respect to IE.

And if you don’t remember, the “modern web” as it exists today with Ajax was actually a Microsoft addition that everyone else added.

JScript was no more or less proprietary than Netscape’s “LiveScript” before Netscape jumped on the Java bandwagon and called it Javascript. It’s not like JS came from a standards body.

Re:Current state of AV1 codec playback support – Oct '22 by alwillis on Friday October 21, 2022 @02:06AM (#33285006)
The justice department at no point stopped Microsoft from bundling IE with Windows.

Nobody suggested otherwise; but that actually wasn’t the point. Microsoft made a deal with the government to stop most of its anticompetitive behavior. It was less about the bundling of IE with Windows than giving OEMs the choice to ship other browsers in addition to IE.

Besides that, up until 2008-2010, the “free and open web” was littered with proprietary Flash apps.

But that was a choice made by the market to adopt Flash instead of having of having all of the Microsoft stuff forced on them. Nobody forced developers to adopt Flash and there were other choices for audio/video, even if they weren’t as popular as Flash.

And if you don’t remember, the “modern web” as it exists today with Ajax was actually a Microsoft addition that everyone else added.

Well, to be accurate, Microsoft shipped XMLHttpRequest in IE 5.0 in 1999, as a proprietary Active X component for their products; it was never intended to be a web standard. But it was a cool idea so the other browser makers implemented it.

The term AJAX was coined by a Google employee in 2005 and was standardized by the W3C in 2006 [1].

It’s no different than Apple developing the canvas [2] element, which became a web standard, except they were more intentional than Microsoft was about XMLHttpRequest which would be renamed as AJAX.

Things would have been very different if the FTC and European regulators (who did make Microsoft ship a version of Windows without IE [3] hadn’t gotten involved.

[1]: https://en.wikipedia.org/wiki/Ajax_(programming)

[2]: https://en.wikipedia.org/wiki/Canvas_element

[3]: No IE onboard Windows 7 in Europe http://news.bbc.co.uk/2/hi/technology/8096701.stm

Re:Current state of AV1 codec playback support – Oct '22 by scarface74 on Friday October 21, 2022 @05:16AM (#33286132)
> But that was a choice made by the market to adopt Flash instead of having of having all of the Microsoft stuff forced on them. Nobody forced developers to adopt Flash and there were other choices for audio/video, even if they weren’t as popular as Flash.

The comment I replied to gave credit to the FTC. Which is not true.

> Microsoft made a deal with the government to stop most of its anticompetitive behavior. It was less about the bundling of IE with Windows than giving OEMs the choice to ship other browsers in addition to IE

Microsoft didn’t just promise “we will be good little boys”. The parent poster gave the credit to the FTC. Firefox didn’t become popular for awhile because it was bundled by OEMs. MS basically just stopped development on IE. Then Chrome took off because it was heavily advertised on the Google home page and bundled with third party downloads.

As far as IE not being bundled with windows 7 because of the EU. This is an example of government ineffectiveness. Windows 7 came out in 2009. Web browsing on the desktop was starting Gibbs yesterdays news by then. The iPhone had been out for two years and Chrome was already ascendant.

Re:Current state of AV1 codec playback support – Oct '22 by alwillis on Friday October 21, 2022 @02:37AM (#33285187)
JScript was no more or less proprietary than Netscape’s “LiveScript” before Netscape jumped on the Java bandwagon and called it Javascript. It’s not like JS came from a standards body.

Popular programming/markup languages don’t originate from standards bodies; it’s usually one person or a small group to start. Ruby, Python, Lisp, Pascal, Perl, PHP were created by a single person or a small group and (sometimes) would be submitted to a standards body.

Javascript was created for the Netscape Navigator browser in September 1995 and was submitted to Ecma International November 1996 [1] to start the standardization process. That was probably in response to Microsoft reverse engineering Javascript to create JScript in… 1996. Funny that.

So… yes, turns out JScript was significantly more proprietary than JavaScript and was only created to further Microsoft’s dominance of the web--“Best viewed in Internet Explorer”. JScript, like most of Microsoft’s tech at that time, probably relied on features that only existed on Windows and no where else.

[1]: https://en.wikipedia.org/wiki/JavaScript

Re:Current state of AV1 codec playback support – Oct '22 by scarface74 on Friday October 21, 2022 @08:05AM (#33287130)
> Javascript was created for the Netscape Navigator browser in September 1995 and was submitted to Ecma International November 1996 [1] to start the standardization process. That was probably in response to Microsoft reverse engineering Javascript to create JScript in… 1996. Funny that.

So it wasn’t “proprietary” when Netscape created it. But it became “proprietary” when Microsoft copied it?

> So… yes, turns out JScript was significantly more proprietary than JavaScript and was only created to further Microsoft’s dominance of the web--“Best viewed in Internet Explorer”

Were you around then when before IE, there were plenty of sites that had “Best viewed in Netscape Navigator”?

And don’t pretend that Navigator was a great product. In its heyday in the mid 90s, it was a point of nerd pride how well your operating system handled a Netscape crash.

IE3 was much better than Navigator on the Mac and Windows. In fact, the Max version of IE was one of the most standards compliant at the time.

Re:Current state of AV1 codec playback support – Oct '22 by alwillis on Thursday October 20, 2022 @11:29PM (#33284168)
Microsoft got in trouble for anti-competitive practices with IE, because they were tightly integrating their OS with their browser in ways that meant that their browser was uniquely enabled by the OS to do things that third-party

It was actually worse than this--when Microsoft was ordered to separate IE from Windows, they lied and said IE was integral to Windows and that it could not operate without it.

Turned out Windows worked just fine without IE and Microsoft ended up settling with the government.

Re:Current state of AV1 codec playback support – Oct '22 by comex on Friday October 21, 2022 @02:51AM (#33285262)
But Safari is the default. And if all the options are equal, then there’s no reason to switch from the default. It’s hard enough to convince people to switch browsers in the best of cases, let alone when the list of potential advantages or differentiators you can offer is severely cut down.
Re:Current state of AV1 codec playback support – Oct '22 by alwillis on Friday October 21, 2022 @04:25PM (#33292649)
But Safari is the default.

iOS supports changing the default browser to something that’s not Safari.

It’s not only about the rendering engines; Brave on iOS has other features and a UI/UX that I like that’s not present in Safari.

3rd party browsers on iOS have other ways of differentiating themselves, especially if you use those browsers on other platforms, like bookmark syncing, etc.

90% of end-users couldn’t care less what’s being used to render their websites on iOS.

Re:Current state of AV1 codec playback support – Oct '22 by paulryanrogers on Friday October 21, 2022 @07:00PM (#33293871)
Locking the rendering engine blocks a host of capabilities, both for the browser itself and its ability to support 3P extensions
Re:Current state of AV1 codec playback support – Oct '22 by alwillis on Friday October 21, 2022 @08:28PM (#33294408)
I doubt it. Safari has 3rd party extensions on iOS and WebKit has all of the important web platform features… in fact, it has pulled ahead of Chrome.

What Apple is avoiding is all of the security issues attempting to support multiple web engines.

Re:Current state of AV1 codec playback support – Oct '22 by brokenmachine on Monday October 24, 2022 @12:33AM (#33312954)
Not an Apple guy, but I thought adblocking was not as good on Safari.
Re:Current state of AV1 codec playback support – Oct '22 by gernb on Friday October 21, 2022 @04:43AM (#33285942)
it is anti-competative by denying 3rd parties from provinding more.

Imagine a truck maker who could somehow prevent other truck makers from making a truck that caries more or runs faster or is more fuel efficient. Of course that would be anti-competative.

Re:Current state of AV1 codec playback support – Oct '22 by xorcist on Friday October 21, 2022 @07:24AM (#33286846)
> on iOS, there's nothing Safari can do that third-party browsers can't

Apart from, you know, run?

(Strictly speaking not technically true of course, but enough to get the point across.)

Re:Current state of AV1 codec playback support – Oct '22 by scarface74 on Thursday October 20, 2022 @09:17PM (#33283015)
Why do people act like the results of the FTC case is lost to the annals of history? Absolutely nothing happen with the case with respect to bundling. There was never a browser choice initiative nor was there ever a time since IR was bundled with Windows was it not bundled.
Re:Current state of AV1 codec playback support – Oct '22 by yjftsjthsd-h on Thursday October 20, 2022 @10:39PM (#33283809)
> I don't understand why they're sitting on their hands. What Microsoft did in the 90s was pale by comparison

Windows had, IIRC, something like 97% of the market. It appears[0] that iPhones have a bit over half the phone market today, but they have nothing like the monopoly that Microsoft held.

[0] https://9to5mac.com/2022/09/02/iphone-us-market-share/

Re:Current state of AV1 codec playback support – Oct '22 by tristan957 on Friday October 21, 2022 @12:26AM (#33284499)
You don't have to have an actual monopoly for the government to act on anti-trust practices.
Re:Current state of AV1 codec playback support – Oct '22 by alwillis on Thursday October 20, 2022 @11:25PM (#33284136)
What Microsoft did in the 90s was pale by comparison—they just bundled some extra software.

Microsoft threatened to cancel the Windows license of several PC manufacturers including HP for making Netscape Navigator their default web browser instead of Internet Explorer. This would essentially put those companies out of business, so they had to comply.

Not to mention, for corporate and home users, Netscape Navigator was commercial product that customers had to purchase while Microsoft bundled IE with Windows for free. This was back in the day when most people didn’t have broadband and stores sold shrink-wrapped boxes of software containing floppy disks or CDs.

I’ve written this many times here on HN: a monopoly isn’t illegal; what is illegal is using your monopoly in one market (PC operating systems) to disadvantage competitors in another market—web browsers.

Apple doesn’t have a monopoly in either PCs or smartphones; there are plenty of alternatives to iOS and macOS. There are lots of examples of platforms where the platform owner decides what can run on that platform, starting with game consoles.

Re:Current state of AV1 codec playback support – Oct '22 by bobkazamakis on Thursday October 20, 2022 @11:44PM (#33284274)
>I’ve written this many times here on HN: a monopoly isn’t illegal; what is illegal is using your monopoly in one market (PC operating systems) to disadvantage competitors in another market—web browsers.

Ah yes, the free market will come up with a solution to this.

Re:Current state of AV1 codec playback support – Oct '22 by TimeBearingDown on Friday October 21, 2022 @07:21AM (#33286827)
This feels like simply a facetious non-sequitur

Do you have anything constructive to add?

Re:Current state of AV1 codec playback support – Oct '22 by tristan957 on Friday October 21, 2022 @12:22AM (#33284475)
You don't have to have a monopoly for the FTC to come after you. You just have to have a sizeable portion of a market.
Re:Current state of AV1 codec playback support – Oct '22 by pencilguin on Friday October 21, 2022 @03:13AM (#33285370)
There are other requirements on effective monopolies. But the US executive branch has decided not to bother enforcing most of them. Used to be, using monopoly power to drive other companies out of business or out of a market was an abuse of that power. Now all the USDoJ will enforce is charging excessive prices.

Reiterating, being a monopoly in the US is not illegal, but it having chosen to have a monopoly makes you subject to extra fairness laws. These laws should be enforced as written, but no recent administration has been willing to step up, and Americans are the poorer for it.

Re:Current state of AV1 codec playback support – Oct '22 by dahfizz on Friday October 21, 2022 @08:10AM (#33287161)
If Google forced alternative browser engines off the play store, the EU would jump all over them.

Apple gets to break all the rules Microsoft and Google get dinged for, because they are vertically integrated. It feels like a bug in the law that corporations are incentivized to take everything in house. Somehow being a bigger, more powerful company makes you less vulnerable to anti-trust laws.

Re:Current state of AV1 codec playback support – Oct '22 by alwillis on Friday October 21, 2022 @04:19PM (#33292593)
Apple gets to break all the rules

No, everyone who’s a registered developer knew they couldn’t use a different browser engine. That’s been the policy from day 1.

It would be different if Apple allowed 3rd party rendering engines and then forced them off, but that’s not the case.

Among other things, 3rd party engines would be incompatible with Apple’s Lockdown feature. Because browsers are required to use WebKit on iOS, they automatically work with lockdown mode; it would be much more difficult if every browser on iOS had it’s own rendering and JavaScript engine:

    On a more technical level, a number of web technologies are turned off,
    including just-in-time (JIT) JavaScript compilation (where code is run
    and compiled at the same time.) In addition, configuration profiles
    (for work or school for example) can't be installed.
From https://www.wired.com/story/how-to-use-lockdown-mode-ios-16/.
Re:Current state of AV1 codec playback support – Oct '22 by makeitdouble on Friday October 21, 2022 @09:18AM (#33287693)
You are right about Microsoft, and what you're describing is also exactly what Google is doing (threatening to cancel Play Store licensing, while Play Store is the dominant licensable app store).

Google is already sued for that, but the sailant point to me is that it took so much time, and it's far from a clear cut case.

We are way past the point where Apple, Google and Amazon abused their position in provable ways, but they got left alone for so long by the regulators it's disgusting.

PS: the definition of a monopoly comes down to the definition of the market. If we were playing games, Microsoft wasn't a monopoy when looking a computing platforms in general, for instance, it was "only" on the PC home market. Apple has a monopoly under many framings, now it comes down to wether a judge agrees or just kicks away Apple opponents.

Re:Current state of AV1 codec playback support – Oct '22 by alwillis on Friday October 21, 2022 @04:09PM (#33292508)
Apple has a monopoly under many framings, now it comes down to wether a judge agrees or just kicks away Apple opponents.

How so? Google has 80-90% of the search engine market and Microsoft had 95% of the desktop operating system market and used that disadvantage competitors in the nascent browser market.

The bottom line with Microsoft was: should Microsoft be allowed to use its monopoly position in operating systems to essentially force customers to take your web browser, whether they wanted it or not? It certainly wasn’t okay for Microsoft to use the threat of canceling HP’s ability to be a Windows’s OEM (and therefore destroying their PC business) if they made Netscape Navigator their default browser.

People forget how dominant Word Perfect and Lotus 1-2-3 were back in the MS-DOS days; Microsoft used Windows to make Word and Excel the dominant word processor and spreadsheet.

Apple’s worldwide market share is barely 30%; it’s closer to 50% in the U.S. It’s also not illegal to disallow 3rd party developers to “break” your platform, especially when they entered into a legal agreement with you to not break your platform.

There’s nothing illegal about controlling a successful platform and deciding who and what can be present on that platform. Game consoles have long operated the same way but that seems to be okay.

Apple doesn’t have a monopoly position in either phones or computers; if a potential customer doesn’t like how Apple operates, they are free to buy something else. That wasn’t the case with Microsoft back in the day and it’s pretty much not the case today with web search, since it’s realistically not an option for a business to not be available on Google search or to ignore its advertising platform that reaches billions of users.

Re:Current state of AV1 codec playback support – Oct '22 by makeitdouble on Friday October 21, 2022 @11:59PM (#33295568)
A lot of percentage are thrown around in your reply, but all of these are relative to a specific market you define. Wether it’s the relevant market definition is up for grabs.

You should have a look at the Apple vs Epic fillings, where Epic came with a pretty different perspective on which definition should be taken into account. They of course lost as the US judge sided with Apple’s definition (while Korea came with a different verdict…), but that’s at least an indication of how important that definition is. “30% of device share” or “80% of in-app purchases” are completely different perspectives.

> if a potential customer doesn’t like how Apple operates, they are free to buy something else

Customers are mostly irrelevant. To get back to your Microsoft example, no developper was stopped from developping for linux, nor were customers stopped from buying barebone machines, or Apple, or beOS, or mainframes. The issue was Microsoft making backroom deals with the vendors to make Windows alternatives pricier and non competitive. This makes it worst for customers as a result, but that’s the result, not the core issue (I’m referring here to the EU rulings). Definition of a anti-trust issue should be about how a player distorts the market by pressuring other business, not wether the customer has theoretical choices or not.

Re:Current state of AV1 codec playback support – Oct '22 by Telemakhos on Friday October 21, 2022 @12:57AM (#33284676)
I may be misremembering things, and I'd appreciate the correction if someone can show me my error here.

When the iPhone was first released, telcos were extremely paranoid, because there were legit scams by which an abuse of the telco network could result in monetary transfers. If you called the wrong number, whether a US (and Apple was a US company first and foremost) 900 number or an international number, you might owe a great deal on your next telco bill. The original iPhone had no native code applications, only web apps, because of the paranoia resulting from scams that had been perpetrated in the 90's. The telcos required a level of security that, in the early 00's and its embrace of Adobe Flash and other high-vulnerability-surface technologies, seemed prudent.

A short while later, Apple proved its security model enough to allow native code applications. This happened because, despite the initial fears of a "smart phone" being a lure for scammers, Apple's security model, which included mandating WebKit so that its security model would be imposed on anything touching the web, kept those web things separate from telco charges.

Fast-forward to 2022: now we wonder why Apple keeps locking things down so that no app can use a security model that Apple has not vetted. In this era, rogue calls to Nigeria don't drain thousands of dollars from your account. Now, we wonder why Apple seems so paranoid.

For me, whose memory reminds me that there was a time that telephony involved the risk of connecting to the wrong number and losing money, there seems to have been a time that "smart phones" ran the risk of presenting an attack surface that could incur dire financial consequences for individuals. I also suspect that those times have passed, but I'm not sure. I have to wonder what the intersectional implications of a more open environment for a device capable of both web browsing (with its security issues) and telephony (with its billing issues) might be. When I wonder about things like that, I'm happier with walled gardens that I would not accept on my laptop, which is not connected to a phone number and billing account.

A computer running Windows and using IE is one thing, namely a computer on an IP network; a phone running iOS is two things, a computer and a telephone, and there are (or were) mechanisms by which a telephone could charge money that a computer cannot (or could not).

Re:Current state of AV1 codec playback support – Oct '22 by est31 on Friday October 21, 2022 @03:12AM (#33285367)
The difference is a) the FTC was way more lax in enforcing anti-monopoly laws than back in the day, b) Microsoft was a monopolist, c) downloading software from the internet hasn't been as much of a thing back then, so obtaining internet explorer replacements was more complicated, so preinstalling something was going to influence pepole's descisions way more than now where installing an app is just one visit to the app store app away. Only years later with improved internet speeds for everyone we got the ability to install chrome with a simple download. Lastly, d), you also have to consider that Chrome and Chromium based engines basically have a monopoly right now. So I'm not sure what the government stepping in will bring to users: Right now it's more that Safari is the only non-Chrome browser that most web devs care about.

Re b: Apple has never been a monopolist so they never got into that situation. This allowed them to have such opinionated choices that would have never worked for Microsoft. However, this might be changing. Recent statistics show that they have extreme market shares in the teenager demographic. If those kids grow up and keep buying iPhones, Apple will become one, in the US market at least, and this means they will have to change.

Re:Current state of AV1 codec playback support – Oct '22 by shellac on Friday October 21, 2022 @04:45AM (#33285964)
> What Microsoft did in the 90s was pale by comparison

You really don't know what you are talking about. The issue with Microsoft was not bundling a piece of software and not fixing the box model.

Microsoft (of the 90s) deliberately worked to undermine the web using their dominant market position, adding their own extensions to ensure lock in. Their behaviour in the web standards process was appalling, and directed from above (sometimes by phone outside meeting).

"Embrace, extend, and extinguish" was not hyperbole.

Re:Current state of AV1 codec playback support – Oct '22 by rkangel on Friday October 21, 2022 @06:57AM (#33286693)
It's possible the EU has sorted this out for us already. The Digital Markets Act comes into effect 1st November and really begins to apply in May next year.

One of the thing that it specifies is that Gatekeepers (Apple in this case) can't prefer their own services and apps over other people's - they must allow third party interoperability. If I understand it correctly:

* You must be able to uninstall preloaded first party apps * You must be able to install your preferred third party equivalents (e.g. Firefox) * I believe also - you can install alternative app stores

We shall see what actually happens once Apple's lawyers dig out loopholes, and we'll see if the Gatekeepers of this world have an alternate 'EU vs rest of world strategy'. Also, if that does happen, which side the UK falls in...