okay, I would try Azul open JDKs on my current MBP. Would run and validate if everything works fine. ( Maven & Jenkins Integration and java selenium test results )
Description says - check short manual at https://youtrack.jetbrains.com/issue/JBR-2526#focus=Comments-27-4527165.0-0
If you want to check on a command line too to see if it is Arm64 you can use the lipo tool.
Gruvbox Dark, which can be obtained from here for iTerm - https://iterm2colorschemes.com/What theme is that? Looks pretty tasteful
I made a copy of Terminal and set the "open in Rosetta" flag on it - that way I don't need to remember to toggle it (though, I rarely use Terminal - I prefer iTerm).
Yes. Python and Pycharm are released as native ARM binaries. You can go with either one.
Thank you so much for taking the time to come back to me.What does "learning on your iPad Pro" mean? Do you have an app (like Pyto) or web environment that allows you to write code? If so, what can't you do now? i.e. Is there a specific need to spend the money now? I don't disagree that I would prefer to do my dev on a Mac, but it's also entirely possible that's because that's how I've always done it.
It sounds like you don't currently have a Mac, and thus no specific software that you're carrying around. In that case, an M1 Mac would seem to be a better future-resistant choice than an Intel-based Mac. Eventually, most of the software will catch up and run natively on Apple Si.
re: MBA now vs MBP now vs MBP later. What do you need from the machine? I bought a MBA because I wanted to play with Apple Si and I don't like the TouchBar. The extra battery life and thermal headroom of the MBP weren't priorities for me. I'd guess that for most development, there's not a lot of performance difference between the MBA and MBP. When Docker becomes available on Apple Si, that may change (Docker causes the fans of my x86 MBP to spin up fully whenever I start a container). Whatever you choose, you aren't making a lifelong commitment. You can always trade up to a machine that better meets your needs when that time comes.
I'd recommend Homebrew and pyenv for local Python development because that allows you install multiple versions of Python concurrently. Helpful if you want to evaluate features in a different version without committing to that version for your system. I'm also partial to VS Code over PyCharm, but PyCharm is a very good tool (and helpful if you're going to use the JetBrains portfolio of IDEs).
It's being enforced on Edu users, so it'll not be long until it's enforced on everyone else.
jenv + Adopt OpenJDK for the win.
# Install jenv to enable switching between Java versions
brew install jenv
echo 'export PATH="$HOME/.jenv/bin:$PATH"' >> ~/.zshrc
echo 'eval "$(jenv init -)"' >> ~/.zshrc
mkdir -p ~/.jenv/versions
# Add AdoptOpenJDK as a source
brew tap AdoptOpenJDK/openjdk
# Install OpenJDK 8 and add to jenv - enter password when prompted
brew cask install adoptopenjdk8
jenv add /Library/Java/JavaVirtualMachines/adoptopenjdk-8.jdk/Contents/Home
# Install OpenJDK 11 and add to jenv - enter password when prompted
brew cask install adoptopenjdk11
jenv add /Library/Java/JavaVirtualMachines/adoptopenjdk-11.jdk/Contents/Home
# Set a global Java version - takes effect on new shell
jenv global 1.8