Why isn't it _actually_ a fork though? I don't like when projects do this and don't actually make it a fork.
From Wikipedia:
In software development, a project fork happens when developers take a copy of source code from one software package and start independent development on it, creating a distinct and separate piece of software.
This seems exactly what happened here.
Are you asking why they didn't use Github's "fork" mechanism?
Github's "fork" mechanism creates a relationship between the two repositories that the developers of this software may not want. For example if the "upstream" ever becomes unavailable, all Github "forks" are auto-deleted. This is surprising to some people and definitely not what an independent separate development would want.
Bit weird/worrying as a user or whatever looking for the repo on Github between deletion and push, but probably not a big deal in the grand scheme of things?
The GitHub UI's concept of a "fork" is unrelated to Git. GitHub doesn't detect you made a proper fork if you don't use its API or UI to do so, and requires contacting customer support to change it.
Not worth the hazzle as it provides no benefit.
It was an interesting read because Linus has repeatedly dismissed github for kernel development, and he never explains why in detail (as a consequence most news reporting his soundbites are not very informative either)
It is a true fork though, both projects have the same commit history.
Zig are also working on it: https://zig.news/monthly/zig-monthly-august-2021-ios-support...
The pioneer of software dictatorship will probably make this impossible or illegal as soon as it gains any traction though. And people will probably congratulate them for it in the name of "security".
What does Microsoft have to do with this?
Consoles were doing that shit way before, unless you redefine what counts as “software” or “dictatorship”
In the case of the poster you are replying to. Yes, Swift is open source and there are compilers for other platforms. The problem comes in with Apple's SDK and their proprietary libraries. Those are what are required to build an app that'll run on an iOS device. Those only run on macOS/OSX.
> No devices emulation: screen, touch, wifi, BT or anything else.
Is this possible as it stands? At least in bits and pieces I can put together?
Especially on an M1, perhaps running the arm builds wouldn't have too much overhead either, even though there are x86-64 images available as well.
So is the main use-case to find bugs in iOS or are there other major use-cases I'm not thinking about?
The only other use case I can think of is setting up a click-farm, or paid-review farm where you give positive reviews for apps for a small fee.
Latest blog post: https://alephsecurity.com/2020/07/19/xnu-qemu-kvm/
