I had a long internal discussion with myself for almost a month about whether I should upgrade to M1 or stick with Intel-based chips and spend them bucks. December 2020 was the time I decided its time to upgrade. I had long given up using the Android emulator and used an actual Android device for testing.
The performance to run heavy tasks like using the iOS simulator when developing and working on React Native apps was declining. My four-year-old Macbook Air was giving up. I recently upgraded from Macbook Air 2017 to Macbook Pro with an M1 chip. While setting up the new laptop, I thought it is an excellent time to update this post. The Macbook Pro M1 I was using crashed and stopped working without any reason on August 25, 2021. Rust support and JetBrains' slow progress on many issues, I will probably switch to VS Code at some point.Note: Most of this article was updated in August 2021. But with the progress that Visual Studio Code makes with e.g. I have a ToolBox subscription (among other reasons because IntelliJ is still the best Java IDE). There are some issues about this in their bug tracker, but the JetBrains personnel either do not seem to understand how the Linux graphics stack works (and come with non-solutions) or say that it is low on their priority list. My only gripe is that they do not have native Wayland support and as a result the IDEs are blurry with GNOME fractional scaling. The JetBrains IDEs are lightning-fast, including indexing. I never had that issue on Linux with a Ryzen CPU (3700X) though. I have noticed the same issue with my Intel MacBooks, it's slow and the fans spin loudly. These must be macOS issues or problems with the limited thermal envelopes ofIntel Macs. This release makes the IDE so incredibly fast! Indexing dependencies happens magnitudes faster than Intel version. That joy has subsided in recent years with performance on Mac Intel.
0 kommentar(er)
