![]() So here I noticed a major difference in how Homebrew seems to work compared to Arch Linux for example. The Cask doesn’t support arm64 natively yet, since the maintainer of it doesn’t have an M1 Mac and mpv doesn’t provide official binaries. Command line applications can be installed with brew install, while graphical applications that you want acccessible in the regular Applications directory need a brew install -cask.įor some applications like mpv this can be a bit confusing since there is both a command-line Formulae and a GUI Cask available for it. Homebrew seems to be the most popular third-party package manager for macOS, so I chose that, hoping that it would support most programs I want to use. MacOS’s AppStore doesn’t seem to have most of the relevant applications for me. The integrated 120 Hz screen is far better than anything I’ve had before, with clearer colors and smoother motion. I haven’t heard the fan turn on at all yet, so either my workloads, and even my compilations, are too light-weight, or the fan is pretty quiet. In DDNet I can reach 1800 FPS which is clearly more than enough and about 10 times the FPS I have with the 6700k’s iGPU. ![]() With the 10 core ARM64 CPU I get about 2-3 times the CPU performance of my desktop system with an Intel i7 6700k. I spent the last 3 weeks using it as a daily driver, tweaking it here and there. Now for work I am for the first time using a macOS-based Macbook Pro with an M1 Pro CPU. ![]() My setup used to be heavily keyboard based. About 3 years ago I wrote about my Linux Desktop Setup and having used pretty much the same software setup for 10-15 years.
0 Comments
Leave a Reply. |