@foxlet was kind to answer some of my questions with the folowing:
"""
There's two factors involved for boot, how long it takes for EFI to find the APFS disk, and how long it takes for the kernel (once loaded) to mount it inside the macOS system.
The first part (on an unsupported Mac) is done by newCore which is slower than the native Apple method that exists on the firmware of all updated Macs (and it's slower because it essentially does all the firmware modifications on every boot, rather than baking it into firmware). The EFI extensions, however, are from Apple, (and fully compatible with unsupported Macs) so kernel loading is similar speed once the disk is found.
Since there's no technical contest between both newCore and Apple, the second part of the video only concerns the difference after the kernel has started.
The second factor is up to macOS itself, modifications aren't involved. APFS itself involves extra containers and additional metadata that the kernel has to churn through before mounting the OS partition (as well as potential bugs), so compared to HFS that adds additional seconds before any of the relevant services have time to start.
Obviously it is a Developer Beta, so there's still some work left to go through before they are on par or faster. Also note that this only involves boot, once you get into the userland macOS, things are very snappy, more so than HFS!
Luigi222 said:
Oh ok, once again thanks for the explanation
@foxlet. That explains a lot, and why you say we can only ( for now ) test APFS with dual system setup once you release your NewCore 0.2 tool.
So it's doesn't look too good that, if even you or another found a way for example to modify your paticular mac firmware model to boot APFS like a supported machine, this would not necessarily mean that it would work on other models right?
I do see a very positive thing here, like you said once the system is fully loaded on APFS, that the system usage is indeed faster
that's very good to know!
@foxlet said:You don't need a dual system to boot APFS, Sierra is only required for installation (you can boot it externally and have a whole APFS disk that way). The APFS boot system itself runs off the ESP partition (hidden by default under macOS). Baking the needed extensions to firmware means that it has to be ported to every unsupported Mac, and that assumes every firmware ROM has enough space to fit the extra software.
"""
So we know for a fact that with
@foxlet newcore 0.2 tool is released, it is in fact possible to install and boot APFS, installing it on a seperate partition using sierra for the installation... however the user in question was asking about a clean install, like we create a bootable disk with the os on it and can format the hardrive of the mac like we can do this moment with sierra patch tool of
@dosdude1 sierra patcher...
Thats what I understood and thats why I wrote what I wrote.
Are you saying you have a new method
@nandor690 ?[/QUOTE]
