![]() ![]() Once done, open each app one by one to tell mac OS that you are happy to run dangerous Internet software, and log in to the ones that require logging in. Here is an example Brewfile and a homebrew install script: On your existing Mac, run brew bundle dump and then copy the resulting Brewfile to your new Mac. The next step is to install Homebrew with all binaries, apps and fonts 2 to get your Mac ready for development. I like this method as it keeps your dotfiles repository organized and easy to manage, yet it makes all your configuration available in the right places. bootstrap script from Zach Holman’s dotfiles repo. Check out all of these examples, or clone a copy of my dotfiles repo cpojer/dotfiles. If you don’t have your own dotfiles repo yet, I highly recommend making one to backup your bash, fish shell, git, and other configuration. Once you are ready to use git locally, clone your dotfiles repository into ~/.home via git clone. Most likely you’ll find yourself reading the Connecting to GitHub with SSH guide for the 100th time because you just cannot remember how to set up a new SSH key otherwise. The first step is to log in to GitHub and set up a new SSH key via GitHub → Settings → SSH and GPG Keys → New SSH key. To get started setting up a new Mac, open your Terminal and run xcode-select -install and sudo xcodebuild -license in your terminal. It also forces me to make my setup portable which prevents the potential for data loss. ![]() I prefer setting up new devices from scratch as it keeps my computers clean. While there are various methods to automatically migrate data like Apple’s Migration Assistant, they are usually imperfect, require a lot of manual work, and often cannot be used on corporate Macs. ![]() Over the years I used many different personal and work Macs. It also doesn’t get very warm when using it on your knee which I also like.įinally, the performance is immense! For reference I purchased the higher standard config of the 14", so it has the 10 core CPU, 16 core GPU and 16GB of unified memory (I picked a standard config as I wanted to get it on day 1).Ĭompiling Ruby and Node happened really quickly and I’ve been very pleased with everything so far! My favourite ever laptop was the 13" MacBook Air (from 2011 I think?!), since then I’ve always had the 15" or 16" laptops, and I’m very pleased to be able to get a high performance chip in the smaller form factor again.I just received a new Starlight M2 MacBook Air and I wanted to share scripts, apps, protips, and what hasn’t worked for me in the past when setting up a new Mac, fast. I’m very pleased to say the M1 Pro doesn’t have this issue, I haven’t heard the fans ramp up once, and that includes when compiling Ruby – which is awesome! I was previously using a 16" MacBook Pro with an intel i9 CPU, the biggest problem I had with that laptop was the heat and fan noise.Įven screen recording, or taking a video call would max out the fans and cause the laptop to get extremely hot. I found a couple of smaller apps like ImageOptim don’t yet have support for arm, and rather than installing Rosetta, I’ve just not installed that yet, I’m sure I will be able to find a workaround if I need to compress images. I was surprised that I didn’t need Rosetta installed, for the most part all the major apps I used, including Hyper (for terminal) and VS Code have Apple Silicon support. The only problem here, is that with NVM, you will need to install Heroku on each node instance you plan to use, so it’s always available inside your projects. The workaround I found, which I couldn’t find documented anywhere was to install Heroku CLI using npm.Įnter fullscreen mode Exit fullscreen mode Heroku’s CLI is recommended to be installed using Homebrew, which throws a bunch of issues about x86 incompatibility. I used node version manager and installed node v14 and v17 without issues. With Homebrew and Ruby set up, the next thing I needed was Node. ![]() The only thing I noticed was that Homebrew now seems to install to /opt/homebrew instead of /usr/local/homebrew, although that might just be a later version of Homebrew, rather than an Apple Silicon specific thing. I was able to install everything natively on the arm chip, I did not need Rosetta for compatibility.įollowing the GoRails guide for Monterey using rbenv, everything installed with no problems. TLDR Everything works with only very minor issues. Prior to ordering, I had some concerns about web development on Apple Silicon and wanted to share my experience so far. I was lucky enough to get my 14" M1 Pro MacBook this week. ![]()
0 Comments
Leave a Reply. |