|Subject:||回复: SwiftUI compatibility APIs in GNUstep's graphics stack (Was: Which ObjC2.0 features are missing in the latest GCC?)|
|Date:||Thu, 28 Nov 2019 02:02:29 +0800|
I wonder how Apple implemented their version though… I do have an observation: if I force VESA graphics on my Hackintosh (this requires special boot flags, so it is easier to do on Hackintosh than a real Mac,) the OS interfaces are rendered very slowly. However if I allow accelerated graphics (default behavior,) it operates smoothly but from time to time the GPU fan would spin up even though there is no GPU-intensive tasks.
I think Apple went down the exclusive OpenGL/Metal route. That is, either get accelerated graphics working at a kernel level, or tolerate slow CoreGraphics.
发件人: Ivan Vučica <address@hidden>
On Wed 27 Nov 2019 at 16:49, Max Chan <address@hidden> wrote:
I don’t know. It was in 2013. I think Fred followed up on my work and cleaned things up.
But it was much slower and it probably still is. I should rebuild with it again and compare.
But if you ask why, no, I never profiled it in great detail.
I just booted my 2009 MB the other day. I also have a Raspberry Pi. But some contributors run non-intel, non-arm hardware with far lower performance characteristics.
None of my machines has 16 cores; I am more than happy with the 4 core (x2 for hyperthreading one).
I would not easily go for a design that assumes “this doesn’t affect me, therefore it’s irrelevant”, at least for GS. Otherwise, if we go for radically divergent architectures, why not throw out AppKit and reimplement the important parts on top of GTK3 or Qt (neither of which, I think, pulls in an OpenGL dependency at this point).
Sent from Gmail Mobile
|[Prev in Thread]||Current Thread||[Next in Thread]|