News for hackers. Stuff that matters.
Re:Apple announces changes to iOS, Safari, and the App Store... by derefr on Thursday January 25, 2024 @06:39PM (#39137011)
What?

Hardware-platform SDKs generally cost tons of money. Visual Studio Professional Enterprise — essentially (if you think about it) the SDK for the Windows platform — costs $250 per month per seat!

(And that's cheap, compared to the SDK costs for proprietary platforms that people don't usually consider "computers." How much do you think Blackberry charges for a QNX SDK? There's a reason that maybe five companies in the whole world ever bothered to develop car infotainment "partner apps", before Apple CarPlay and Android Auto came along to make the platform moot.)

These SDK fees pay for "the platform" — but specifically, in IP terms, they give you a license to use the source code and libraries that come with the SDK, a license to redistribute the outputs of the compilers that come with the SDK — and so forth.

PC and smartphone platform vendors stopped charging so much for SDKs (or at least their non-enterprise-level SDKs) right around when they introduced App Stores. Because they changed the model, to one where the license you got with the SDK, said that your IP license to the stuff in the SDK, is paid for through royalties, by the revenue you make from publishing your app on their App Store.

And that's a perfectly valid arrangement. If you breach the contract, by not giving Apple royalties, then you don't have IP rights to redistribute the derivative works from their SDK any more!

Re:Apple announces changes to iOS, Safari, and the App Store... by int_19h on Thursday January 25, 2024 @07:27PM (#39137403)
The vast majority of Windows software doesn't need VS Professional or Enterprise; Community edition works just fine, and still enables you to access the entirety of the platform as a developer. Not to mention numerous alternative development toolchains, use of which doesn't require paying anything to Microsoft.

And then on top of that, Apple already charges developers for tooling via their dev license program. Which at least makes some sense since it's a fixed fee. The notion that maker of the toolchain gets to claim a percentage of what the app written using it brings in is ridiculous by all industry standards.

Re:Apple announces changes to iOS, Safari, and the App Store... by nodamage on Thursday January 25, 2024 @08:45PM (#39137989)
> The notion that maker of the toolchain gets to claim a percentage of what the app written using it brings in is ridiculous by all industry standards.

Do you also believe that Epic's Unreal Engine pricing is also ridiculous under the same standard?

Re:Apple announces changes to iOS, Safari, and the App Store... by ethbr1 on Thursday January 25, 2024 @09:16PM (#39138193)
It's an interesting distinction, or if there should be one, between libraries-that-provide-value and libraries-that-must-be-used-to-access-a-platform.

If I create a platform, and an SDK that targets that platform, and require everyone to pay for the the SDK to use my platform...

... is that the same as if I create a set of libraries (nee game engine) that avoids you from having to recreate that work yourself?

I'd hazard that the two are different, because Epic isn't really gating access to an "Unreal Device" by withholding access to their engine.

A developer is free to use a competitor's engine and distribute the same places. (Afaik, Epic's store doesn't have any "must be built on Unreal" qualifier, right?)

Re:Apple announces changes to iOS, Safari, and the App Store... by MatthiasPortzel on Thursday January 25, 2024 @09:59PM (#39138438)
It's absurd to argue that Apple's libraries don't provide value.

Apple's SDK includes the compiler that target's Apple's chips, a fully-featured IDE, the platform specific APIs (sure), the UI framework, a shader API, a physics engine, etc.

Re:Apple announces changes to iOS, Safari, and the App Store... by ethbr1 on Thursday January 25, 2024 @11:23PM (#39138931)
Are there alternatives to using Apple's SDK, if you want to target Apple's hardware, which has a substantial market share?

Limiting the ability for dominant companies to crown themselves gatekeepers and toll all who pass was the intent of the EU rules.

If Apple tries to argue that the one SDK is intrinsically tied to the hardware, and also conveniently is required for apps on any store... that starts to sound a lot like 90s Microsoft and Internet Explorer, except Apple doesn't have the "But it's free" defense.

Re:Apple announces changes to iOS, Safari, and the App Store... by freedomben on Friday January 26, 2024 @04:35AM (#39140561)
> It's absurd to argue that Apple's libraries don't provide value.

Who is arguing that Apple's libraries don't provide value? Certainly the person you replied to isn't. That's an incredible strawman fallacy

Re:Apple announces changes to iOS, Safari, and the App Store... by ethbr1 on Friday January 26, 2024 @08:32AM (#39142406)
The terms I used in the initial comparison probably weren't the best.
Re:Apple announces changes to iOS, Safari, and the App Store... by burnerthrow008 on Friday January 26, 2024 @02:56PM (#39147352)
> Who is arguing that Apple's libraries don't provide value?

All the people who are whining that the core technology fee exists.

Re:Apple announces changes to iOS, Safari, and the App Store... by nodamage on Friday January 26, 2024 @02:49AM (#39139881)
I mean ultimately both companies have invested R&D into building their SDKs and it comes across as bizarre to me to suggest that one company should be legally banned from charging licensing fees for their use.
Re:Apple announces changes to iOS, Safari, and the App Store... by ethbr1 on Friday January 26, 2024 @08:36AM (#39142439)
Ceteris paribus, sure.

But if we've decided that it's unhealthy to allow dominant tech firms to tax everyone for access to their platforms...

Then an SDK might become the final area where they attempt to do so.

It'd certainly be a lot cleaner if there were 2 SDKs: a base, primitive-only freely licensed one with the bare minimum for interacting with all platform components and a higher-level, premium paid one that had better DX.

Re:Apple announces changes to iOS, Safari, and the App Store... by int_19h on Thursday January 25, 2024 @09:48PM (#39138390)
It is, actually, yeah. But game dev has a long track record as an industry where these types of abusive behavior are normalized.

This is certainly not normal for any even remotely mainstream desktop or mobile platforms, though. iOS would be a glaring exception.

Re:Apple announces changes to iOS, Safari, and the App Store... by nodamage on Friday January 26, 2024 @01:59AM (#39139635)
So Microsoft, Sony, and Nintendo too? So much for "ridiculous by all industry standards" when there is an entire software industry where this is commonplace.
Re:Apple announces changes to iOS, Safari, and the App Store... by BlueTemplar on Friday January 26, 2024 @06:44AM (#39141569)
It's (more) acceptable for consoles because they are not (Very) Personal Computers.
Re:Apple announces changes to iOS, Safari, and the App Store... by derefr on Thursday January 25, 2024 @07:33PM (#39137453)
> The notion that maker of the toolchain gets to claim a percentage of what the app written using it brings in is ridiculous by all industry standards.

Never published a game on a game console, eh?

Re:Apple announces changes to iOS, Safari, and the App Store... by coolandsmartrr on Thursday January 25, 2024 @09:58PM (#39138432)
Could you describe the terms for publishing on a game console?
Re:Apple announces changes to iOS, Safari, and the App Store... by lwkl on Thursday January 25, 2024 @11:28PM (#39138960)
Sign a NDA, buy a dev kit, get access to the APIs, let the console maker certify your game and take like 30%.
Re:Apple announces changes to iOS, Safari, and the App Store... by piskov on Friday January 26, 2024 @09:53AM (#39143259)
> Community edition works just fine

Read the terms: it’s not for commercial development

Re:Apple announces changes to iOS, Safari, and the App Store... by kllrnohj on Thursday January 25, 2024 @07:36PM (#39137473)
Apple already charges for the SDK, the $99/year developer fee. This is a second, unrelated, app install fee. There's certainly nothing similar on PC, Mac, or Android
Re:Apple announces changes to iOS, Safari, and the App Store... by ClumsyPilot on Thursday January 25, 2024 @07:03PM (#39137199)
> Visual Studio Professional Enterprise — essentially (if you think about it) the SDK for the Windows platform — costs $250 per month per seat!

Or you can use GCC and compile “Hello world” for windows, no Microsoft IP involved? What am I missing

Re:Apple announces changes to iOS, Safari, and the App Store... by derefr on Thursday January 25, 2024 @07:22PM (#39137364)
GCC — or even something like Mono — doesn't come with the headers et al for the GUI parts of Windows. And those headers are protected IP, even if you re-derive them from scratch — just ask Google about the JDK!

Certainly, you can compile Hello World with GCC — or maybe even a POSIX network server — to run under WSL. And maybe redistribute the resulting hello_world.exe to other WSL users.

But what happens when you want to compile that same program to run "on Windows" directly, to be redistributable to people who don't have WSL installed?

Well, even if you're using GCC, you'll probably end up linking your program against the Visual C Runtime. (Because otherwise you'll need to ship — or statically link — glibc.dll. Which is a bit ridiculous.) And the Visual C Runtime is... part of Visual Studio! A part that's freely redistributable, yes... for those developers with a valid Visual Studio license. Otherwise, Microsoft can sue you for packaging MSVCRT.DLL with your app.

And as your app gets more complex, that just keeps being truer. While Microsoft Store apps can just list their package deps and get the store to install them, if you're a standalone Windows UI app, you might have to redistribute, say... DirectX. Or SQL Server Embedded. Or even — and this is a very clever trap on Microsoft's part that many FOSS devs don't notice — some "sample library code" from MSDN. All of which are offered under that same redistribution licensing clause.

---

Note that there are high-level "app platforms" that attempt to work around all this — mostly by not having you compile anything to target the Windows native ABI at all — but rather, just providing a higher-level platform abstraction, that you write code against, where that code ships with the executable but not within the executable (so as to keep the executable's Microsoft-stamped code signature intact.) This is how Electron's Windows support works, for example. Also, most game engines, e.g. Unity, Love2d, RenPy, etc.

I believe that there are also a few "app platforms" that go another route, trying to avoid the Windows runtime altogether — using funky low-level static-compiled languages to directly address the NT syscall ABI, and then building up from there to doing multimedia and networking. I think Haxe is like this?

But while Haxe has some level of windows-and-menus UI toolkit (http://haxeui.org/), it's not one that supports OS accessibility APIs (e.g. screen-reader support), or DPI scalability, or high-contrast mode. (In other words, it's just not suitable for writing B2B software where your users are under a bunch of business requirements on what the software they give their employees to use, needs to be able to offer them.)

Also, you're not getting integration with OS file-picker dialogs, or multi-format drag-and-drop / copy-and-paste, or embedding of arbitrary graphical COM components within the view, or — especially — being embedded as a graphical COM component within some other app. (This last one is pretty important for boring line-of-business apps like tax-filing software; you want your app to be able to render its document filetype to the viewport when documents of that type are opened in a browser!)

In short: for making anything that you charge for... you're still gonna just pay Microsoft for Visual Studio.

Re:Apple announces changes to iOS, Safari, and the App Store... by int_19h on Thursday January 25, 2024 @07:37PM (#39137484)
WSL has nothing to do with all this - we're talking about gcc building directly for Win32. That aside, you make several claims that are outright wrong.

First of all, MinGW does come with all Win32 headers of their own included, and no, they're not protected IP (or at least Microsoft never made the claim to the contrary).

With respect to C runtime, Windows itself ships with a bunch of them, packaged as system DLLs. MinGW used msvcrt.dll historically, which is the one that originally shipped with VC++ 6.0 before getting included into Windows. Since Win10, Windows ships an ABI stable C runtime called uCRT, precisely so that different toolchains have a single shared library for better interop. Modern versions of MinGW link against uCRT. Visual Studio still ships the C++ runtime, which MinGW doesn't need because it has its own.

On top of that, unlike Unix, in Windows, CRT is not the basic OS API, but mostly a relatively thin wrapper around rich native Win32 APIs, so there are far more around than just different versions of VC++ runtime and glibc. For example, C++ Builder has its own.

If you're a standalone Windows app, you don't have to redistribute DirectX. You can just target the minimum version supported for your matrix. If you're targeting supported versions of Windows (i.e. 10+), that'd be DirectX 12. And then of course you don't have to ship SQL Server Embedded because you don't need to use it; there are plenty of alternatives such as SQLite and Firebird.

Just about the only situation I can think of where you have to pay Microsoft for the privilege of developing for Windows is when writing drivers.

Re:Apple announces changes to iOS, Safari, and the App Store... by derefr on Thursday January 25, 2024 @07:58PM (#39137643)
All of what you're saying is true of modern Windows; apologies, but I last used Windows in the 98/ME/2000/XP era, and my arguments are based in that era.

Despite things having changed, though, I think "Windows in the before-times" is still a viable precedent to cite in its own right, for Apple's current behavior. IP case-law hasn't changed too much between then and now.

For example: when developing for Windows 98, you needed to ship DirectX, because otherwise there would be no pre-installed version of DirectX — and the average user's internet connection wasn't fast enough to download it in any reasonable amount of time!

And uCRT + WinSxS preloads both exist now, but obviously, neither did before Windows Vista. Before then, you couldn't predict if any MSVCRT was gonna be available, so if you were trying to publish e.g. Apache Server But Running In a Windows Tray Icon With A Little Management Context Menu (a common thing back then, for some reason), then you needed to package the particular MSVCRT your app was compiled with. Which is why you never saw FOSS binary releases for Windows back then; instead, there was the FOSS project, with compilation instructions that involved downloading the right MSVCRT yourself; and then there were random third-party downstream "freeware" releases published on CNet or whatever.

> and no, they're not protected IP (or at least Microsoft never made the claim to the contrary)

They haven't, because there's nothing to gain from them doing so, because they aren't trying to run an ecosystem that has a per-install fee, unlike Oracle ca 2010, Unity last year, or Apple right now. (And they never will, because they're all-in on service fees (Azure) instead.) Without that incentive, Microsoft has every reason to listen to the competing incentive — that of making Windows a platform that's friendly and open to developers, that doesn't force them through this kind of bullshit.

But if, in some hypothetical world, Microsoft were to be charging developers per app install... then Microsoft would likely tell MinGW to stop redistributing "their" headers, so as to force more developers onto the SDK and through that into being install-monitored. And they would have every right (according to current IP case-law) to do so.

They wouldn't have a mandate to do so, mind you — source files, including headers, are copyrighted, not trademarked, so they don't need to enforce their IP rights to keep them. They could simply choose to enforce their copyright against only the most egregious violators: those who are clearly making millions of dollars off the use of their platform, without paying them a dime. As Apple is trying to do now!

Re:Apple announces changes to iOS, Safari, and the App Store... by int_19h on Thursday January 25, 2024 @09:41PM (#39138357)
MSVCRT.DLL has been an OS component since Win2000. But, as noted earlier, you never needed a CRT to write Win32 apps. Indeed, it was not uncommon especially in the 98/XP era for apps to be written directly against Win32 API (or with very thin wrappers like ATL and WTL; I did my share of that even as late as 00s). And even then pretty much all alternative toolchains, including C++ ones (notably, Borland C++), used their own runtimes anyway. The actual shared platform was always Win32, and there was never any sort of charge, direct or indirect, for using it.

The main reason why people shipped their own version of the CRT for VC++ was because they wanted to use a more modern version of VC++ itself (e.g. because of better support of new language features; C++ was just standardized then and all compilers were updating very rapidly to catch up), which then required a new version of the CRT that wouldn't be guaranteed by the lowest target OS version. But even VC++ did not require you to use the CRT; you could just #include <windows.h> and linker had a flag to drop stdlib.

And even when you wanted to use MSVCRT while targeting platforms where the desired version wasn't guaranteed, you still didn't have to ship it. All redistributable packages were (and are!) also published as standalone installers that users could just download and run themselves; indeed, it was not uncommon for open source Win32 software to require one to do exactly that. The bundling packages that MS also provided for integration with your own installer are a convenience, not a prerequisite.

The story with DirectX is very similar. DirectX did in fact ship as an OS component with every version of Windows starting with Win95 OSR2 and WinNT4. The reason why games pretty much always bundled it is because they wanted to use something newer, given how fast things changed back then. But, again, it was always available separately as a standalone installer, and any app that needed it could request it to be installed manually by the end user, and some apps did just that. I will also note that those standalone CRT and DirectX installers were also commonly redistributed, e.g. on large websites like Tucows.

With respect to Win32 APIs themselves being somehow protected through some form of IP, that wasn't the case, either. Again, Borland C++ / Builder used its own headers with no problem. And then of course pretty much every non-C toolchain that wanted to expose the dev to the OS API also had to provide their own equivalent of windows.h, which they all did - Delphi being probably the most prominent third party example, but there were numerous others - Ada, Eiffel etc; and even most scripting languages such as Perl. Again, back in that period, I myself wrote a bunch of Win32 header translations for then-nascent D. I don't recall anyone ever bringing up the notion that doing so was somehow legally risky; it was understood as an obvious and necessary step in development of any toolchain targeting the platform.

XP era also includes early .NET. The interesting thing about that one was that the .NET Framework redistributable (which, again, was provided as a standalone installer) also includes the C# and the VB command-line compilers, and since .NET metadata is embedded into the binaries, the result is that you effectively got a free build toolchain that let you do anything .NET could do. XP SP1 even included .NET 1.0 builtin, which I believe was the first time Windows came with dev tooling sufficient to write a full-fledged app for itself in the box.

The bit about "you never saw FOSS binary releases for Windows back then" is plainly not true. FOSS in general wasn't nearly as widespread then, and people who cared about it generally didn't care much for the DOS/Windows ecosystem, so mainline would often not even bother and just assume POSIX, and porting was a slow effort that required constant ongoing maintenance to keep up-to-date with upstream. But what did exist would normally be redistributed in binary form; examples include MinGW, Perl, and Python. Similarly, when using FOSS libraries like zlib, it was common to download and use redistributed prebuilt DLLs + import libs for your compiler.

So, to summarize: Microsoft never charged developers for access to the platform itself, and you could always write and distribute Windows apps without paying anything to MS. It charged the devs for tooling, but it also left the door wide open for alternative tooling, which did proliferate to the point where in some markets like Europe there was more Windows software written using Borland tools rather than Microsoft tools.

Re:Apple announces changes to iOS, Safari, and the App Store... by vel0city on Thursday January 25, 2024 @11:09PM (#39138858)
I did some basic C/C++ development back in the Windows 2000/XP era. I never needed to pay for a Visual Studio license, I didn't even use Visual Studio. I was hacking things together in notepad and gcc at the time.

I did years of development work against Windows machines before I got my first paid Visual Studio license, and it was still like a couple years until the first time I bothered actually installing the Windows SDK.

Re:Apple announces changes to iOS, Safari, and the App Store... by simiones on Friday January 26, 2024 @10:01AM (#39143367)
> And they would have every right (according to current IP case-law) to do so.

Actually, the result of the Google v Oracle case was ultimately that what Google was doing constitutes fair use - and what MinGW is doing is even more clearly in the fair use zone than what Google was doing. So, current IP case-law is firmly on the side of "copying APIs for interoperability is fair use".

Re:Apple announces changes to iOS, Safari, and the App Store... by postalrat on Thursday January 25, 2024 @07:43PM (#39137542)
GCC — or even something like Mono — doesn't come with the headers et al for the GUI parts of Windows. And those headers are protected IP, even if you re-derive them from scratch — just ask Google about the JDK!

You are arguing that a replacement for windows with an identical API would be protected IP. Not the toolchain for building applications.

Re:Apple announces changes to iOS, Safari, and the App Store... by EMIRELADERO on Thursday January 25, 2024 @07:33PM (#39137452)
So what happens when a FOSS SDK for iOS pops up, which only calls the APIs on the OS itself and doesn't include any Apple-copyrighted stuff in it? What would you pay Apple for, then?
Re:Apple announces changes to iOS, Safari, and the App Store... by Kwpolska on Friday January 26, 2024 @02:53AM (#39139904)
> Visual Studio Professional Enterprise

Professional and Enterprise are two distinct editions. Professional is $45/user/month, and it's a capable IDE even if Enterprise has some extra features.