I have to hit that power button multiple times a day, because the Mac mini just won't wake up from the USB keyboard/mouse... Worst of all, it always worked fine on my previous Hackintosh!
Here you go: https://pastebin.com/iemfTkzx As a dataset, I just use find to generate a list of paths from the file system: find / > large.txt I tested with Swift 5.7 and 5.9, and Python is always between 4x and 10x…
I noticed the same thing. Either Swift performances are atrocious, or I'm missing something. Just the other day I was trying to sort a large array of strings in Swift and it was painfully slow. A 3 lines Python script…
No, /dʒæk/ is not /ʒak/
AFAIK there's no "libc" on macOS. libSystem is "libc".
Yet one obvious UI change on Big Sur is they added pointless padding to windows and menus.
Looks like a Carambola2 (19€). http://8devices.com/carambola-2 Same amount of RAM and flash, but different SOC.
I have to hit that power button multiple times a day, because the Mac mini just won't wake up from the USB keyboard/mouse... Worst of all, it always worked fine on my previous Hackintosh!
Here you go: https://pastebin.com/iemfTkzx As a dataset, I just use find to generate a list of paths from the file system: find / > large.txt I tested with Swift 5.7 and 5.9, and Python is always between 4x and 10x…
I noticed the same thing. Either Swift performances are atrocious, or I'm missing something. Just the other day I was trying to sort a large array of strings in Swift and it was painfully slow. A 3 lines Python script…
No, /dʒæk/ is not /ʒak/
AFAIK there's no "libc" on macOS. libSystem is "libc".
Yet one obvious UI change on Big Sur is they added pointless padding to windows and menus.
Looks like a Carambola2 (19€). http://8devices.com/carambola-2 Same amount of RAM and flash, but different SOC.