Google Chrome For Macbook Air M1



I recently upgraded from Macbook Air 2017 to Macbook Pro with an M1 chip. My four year old Macbook Air was giving up. The performance to run heavy tasks like using the iOS simulator when developing and working on React Native apps was declining. I had long given up using the Android emulator and have been using a real Android device for testing. December 2020 was the time I decided its time to upgrade.

I had a long internal discussion with myself for almost a month that whether should I upgrade to M1 or stick with Intel-based chips and spend them bucks. Don't get me wrong here, M1 is not cheap either as I did go for a RAM upgrade to max limits which is currently 16GB in the base model. The kind of performance I was expecting after going through some online reviews and research, has been worth it so far (it is fast, no doubt). I received it two weeks back at the time of writing this post and since then I have installed all the necessary tools and utilities that help me work on Web development and React Native apps.

Macbook Air M1 Sale

My local environment currently includes:

Google’s Chrome team was early to that procedure, quietly pushing out a native M1 variation of the browser yesterday. Speedily noticed by Chrome buyers, it finished in an aborted rollout following reports of unanticipated crashes on M1-based mostly versions like the new MacBook Air, MacBook Pro 13, and Mac mini. Nov 17, 2020 In our reviews of the MacBook Air, MacBook Pro, and Mac mini equipped with the new M1 chip, though, we found that the version of Chrome built for Intel chips already runs well on Apple’s new Macs.

  • Rosetta 2
  • Homebrew
  • Git
  • Node.js
  • npm
  • Zsh
  • Oh My Zsh
  • iTerm
  • Xcode
  • yarn
  • VSCode Insiders Edition
  • Testing GatsbyJS builds

Other apps:

  • Google Chrome
  • Brave
  • Firefox Developer Edition
  • Android Studio
  • Insomnia as REST API client
  • And other desktop applications like Slack, Discord, Todoist, GitHub Desktop, and so on.

Rosetta 2

Rosetta 2 is the lifeline that allows you to run apps designed for Intel-based chips that use x86 architecture on ARM-based chips (in this case M1). This solution is provided by Apple in form of an emulator and doesn't come pre-installed. You have to install it manually. Fire up the Terminal application that comes pre-installed on the Big Sur and let your first command to execute be:

If you decide not to put the flag --agree-to-license, you will be prompted by Apple's interactive install and you will have to agree to their terms and license conditions in order to use it.

iTerm

My favorite terminal app that I have been using for years is iTerm. I am currently using two versions of iTerm on my setup. One with Rosetta 2 enabled and the default one. This way, I can only use the Rosetta 2 emulator when required. There are no performance issues I have found with using iTerm with Rosetta 2 for ARM-based applications.

Google Chrome

If you'd like a similar setup, go to the Applications folder in your Macbook and duplicate the iTerm application.

You can rename the duplicated iTerm app. I have renamed it to iTerm_rosetta to differentiate between the two. Right-click the duplicated app and click Get Info. In the General check the box where it says Open using Rosetta.

Now, if you open the second terminal, it will be using Rosetta 2 emulator by default.

Other iTerm profile settings that I use:

Recently I started using Jetbrains Mono font.

For the overall looks and appearance, I use Dracula Pro Color Presets created by Zen Rocha.

And my last favorite thing is to split the working directory into two more different tabs using Command + D for horizontal panes. Make sure to have the following setting configured from General > Working Directory > select Advanced Configuration > click button Edit.. > select Reuse previous session's directory under Working Directory for New Split Panes.

For terminal prompt, I use Spaceship ZSH.

Homebrew

On December 1, 2020, the Homebrew team made an official announcement on their website about the version release 2.6.0. The most significant changes among others they listed were the support for macOS Big Sur, using brew commands instead of brew cask and beginning to support macOS M1 and Apple Silicon or ARM-based chips.

This is the tricky part. At the time of writing this post, some formulae that you may like to use, might not work. It's better to track at the GitHub issue here in the Brew's official repository which is maintained by their team. I am thankful to the whole team behind the Homebrew for making it accessible and appreciate their hard work on making things work in such a short time.

Using the terminal, you can install the Homebrew by executing the default command:

Recently I found that it can be installed natively on a Macbook. You can run the above command in a native terminal environment as well without using the Rosetta terminal environment.

Git

I did install Git using brew command: brew install git.

To authenticate GitHub to be used from the terminal environment, I'd recommend you to check out the official document on creating and accessing personal tokens.

Xcode

After installing Git, for me, the next step is to install Xcode app from Apple's App Store.

After installing it, make sure to open it for the first time, from the menu bar, open Xcode > Preferences > Locations and make sure that Command Line Tools point towards the current Xcode app.

Macbook

Node.js

On Apple's silicon-based laptops, Node.js versions starting from 14 and below are not supported. You will have to install version 15.x.x. or greater (depending on when you are reading this post).

At first, I installed Node.js using nvm without using Homebrew. Execute the below curl command to install nvm first:

After installing it, add the following to the .zshrc file and make sure to put them after sourcing Oh My Zsh:

Mail for mac html signature. To verify that nvm is installed, restart the console or the zsh session (execute: source .zshrc) and execute the following command to check out its current version:

Then run the command nvm install node.

Alternatively, you can also install the Node.js using the official installer for the current version which I later moved on to.

ZSH and Oh My Zsh

ZSH is the default shell that macOS Big Sur comes with. I like to use Oh My Zsh to manage ZSH configuration and some plugins and a theme to prettify the terminal.

To install, run the command below:

Google Chrome For Macbook Air M1

After installation, make sure that the file zshrc is exporting the below path:

The first I like to do after setting up the bare minimum ZSH configuration is to install a plugin called zsh-syntax-highlighting. It provides syntax highlighting for the ZSH shell. Execute the series below commands in the terminal window:

Google Chrome For Macbook Air M1 Black Friday

In a nutshell, this is my initial ZSH configuration in the file ~/.zshrc file:

After installing the syntax highlight plugin, it starts to recognize the commands:

VSCode

VSCode does not have native M1 support yet. Side shift forklift.

VSCode and VS Code Insiders edition both support ARM chips now (as of March, 13, 2021). Download the installer for Insiders edition from here and for VSCode here.

I am still using the same VSCode configuration from my previous setup:

Themes

I usually like to switch between a dark and a light theme.

  • For the dark theme where I spent most of my time, I am currently using morgan.codes-theme.
  • For the light version, I am using the theme called Quiet Light which comes pre-installed with a new VSCode installation.
  • For file icons, I love Material-Icon-Theme.
  • For terminal prompt, I use Spaceship ZSH.
  • Font: Jetbrains Mono font.
Google

Google Chrome For Macbook Air M1 Review

Extensions

I use VSCode editor for both writing code and writing blog posts. Thus, the list of extensions below is the combination of extensions that fulfills both of my purposes.

Global NPM Packages I use

  • gatsby-cli To build and test out my personal blog built with Gatsby.
  • npm-check to check for outdated, incorrect, and unused dependencies.

For React Native Development

  • install [Watchman] to watch changes in the filesystem using the command: brew install watchman.
  • install Java Development Kit using the command: brew install --cask adoptopenjdk/openjdk/adoptopenjdk8.

  • install Android Studio

    • Then install Android SDK v29.

For more instructions on how to setup development environment for React Native, please follow the official documentation here.

For Gatsby Sites

Google Chrome For Macbook Air M1 Reviews

If you have a side project that uses GatsbyJS, chances are you are going to face the issue https://github.com/lovell/sharp/issues/2460. Gatsby uses a C based library called Sharp that needs to be compiled under the ARM architecture. It did not work for me and the only way I could solve was to install vips formulae from Homebrew as mentioned in the GitHub issue itself.

Conclusion

That’s the setup I now use for my JavaScript, Node.js, React and React Native. I think it's a good machine. Hopefully, M1 is just the beginning of a new era of powerful computers for daily use.

🤔 The only thing left for me is to find a way to transfer all laptop swag/stickers from my Macbook Air to Pro. I miss having them on this one.

isapplesiliconready.com is another useful link I found sometime back to check what is compatible to work on Apple Silicon chips natively or using Rosetta or not optimized at all.

Chrome for Apple’s M1 Macs has been released, a specially-developed version of the browser for Apple Silicon, a day after Google had to pull down its first attempt over stability issues. Attempts to download Chrome now bring up two different options: you can either have Chrome for a Mac with an Intel chip, or Chrome for a Mac with an Apple chip.

Google Chrome For Macbook Air M1 Price

The native app promises performance improvements, rather than relying on Apple’s Rosetta 2 emulation as the x86 Intel version would require. Apple has made some big claims about Rosetta’s capabilities – including suggestions that emulated apps can actually run faster on M1-based Macs than they do on Intel versions – but the company’s clear hope is for native software to become the norm.

Google’s Chrome team was early to that process, quietly pushing out a native M1 version of the browser yesterday. Quickly spotted by Chrome users, it ended in an aborted rollout after reports of unexpected crashes on M1-based models like the new MacBook Air, MacBook Pro 13, and Mac mini. The Chrome team promised a second attempt today, and that’s now been launched.

Those who have one of the newest Macs, and who use Chrome, shouldn’t really see much in the way of differences beyond speed. Both versions will benefit from Google’s latest improvements in performance and memory utilization, Chrome 87 being pushed out earlier this week with some significant promises.

Google Chrome For Macbook Air M1

Chrome’s CPU usage could be cut by a fifth, Google’s team said at the time, while battery usage could see a 1.25 hour improvement. Desktop Chrome starts faster, and loads pages faster, Google promised, while new actions had been added along with improvements to how tabs can be managed.

The challenge, of course, is Safari. Apple’s browser has the benefit of its developers being in-house with the designers of Apple Silicon itself, and the Cupertino firm hasn’t been shy in promising advantages in performance and memory use when Mac owners stick with the homegrown software.