[milansm]

I’d like to see a “benchmark” about M1’s support for real world dev setup (docker, brew, libraries and so on). And when can we expect the full support

[jeffbee]

I consider myself a "real" developer and I don't use any of that stuff. So far my observations about tool and library availability:

Node: build it from source at HEAD and it works fine. Will work out of the box in release 16.

Java: Get the Azul JRE, works fine.

Go: Has to be bootstrapped from HEAD.

c++ toolchain: works out of the box

cmake: build and install from source release, no problems.

bazel: still doesn't grok darwin_arm64, release build tries to x-compile everything.

anything that needs bazel: doesn't work due to above.

python3: comes in the box, works

R: no native package yet

[rsynnott]

Caveat; if you need Java 15, Azul doesn't have that as yet.

That said, most people probably do not; 11 is still the most recent LTS version, which is what most people would be interested in.

[BryantD]

Brew status: https://github.com/Homebrew/brew/issues/7857 Docker status: https://github.com/docker/roadmap/issues/142

From a quick glance neither have committed release dates, but "soon."

[qz2]

I'm avoiding brew/docker myself on my main desktop as I've screwed it up a couple of times doing that before. Thus I fire up a t2.small in AWS to test docker images on. My local box is VSCode, Terraform, aws cli, Go, Python etc and everything just works (mostly through Rosetta)

[sroussey]

Ideally, Docker et al will be ready by the time the MacBook Pros come out. Here is hoping.