5 ms·

I was like you at first, seeing that my chrome speeds don't feel that fast, then I did my first XCode build. Holly.. it is so much faster than my 2017 Macboo

I was like you at first, seeing that my chrome speeds don't feel that fast, then I did my first XCode build. Holly.. it is so much faster than my 2017 Macbook Pro. Super fast builds, and A huge productivity boost. I think it shows that if software is optimized for it, M1 can be/feel crazy fast. Unfortunately, anything running with Roseta, will not feel that fast, as it's performance will be hobbled by the emulation layer.

officeplant 5y ago
Even the M1 port of Chrome is clunky, but then again chrome has always been clunky with MacOS. Firefox's M1 port actually got me to finally start transitioning out of chrome after being a fairly devoted chrome user since it released. It's the only third party browser on M1 macs that comes close to Safari in speed and handles window size changes (especially when video is playing) leagues better than Chrome.
- FireBeyond 5y ago
  Chrome completely crashes a few times a week on my M1 Max laptop. Very frustrating. Not even necessarily when I'm doing something actively, or intensively. I can have HN open as my only tab, be reading an article and I look back at the screen and Chrome has gone.
glandium 5y ago
Note that one part of this is that llvm is significantly faster to generate code for arm64 than for x86_64. I'm not saying that accounts for all the difference, but it helps.
thatswrong0 5y ago
Yet even still under Rosetta, my M1 Pro can handle more than twice as much "stuff" in my Ableton projects vs. my 2018 MBP, all while barely heating up and without _any_ fan noise (whereas my 2018 MBP starts sounding like a jet engine almost immediately after opening any sizeable project). So for me, its performance completely lives up to the hype. I don't think I'll need a new machine for a loooong time.
- herpderperator 5y ago
  Imagine how much better it will be with the native build: https://www.ableton.com/en/blog/live-111-apple-silicon-support-now-in-public-beta/ https://www.ableton.com/en/blog/live-111-apple-silicon-suppo...
  - thatswrong0 5y ago
    The main issue with that is a looot of plugins I rely on day to day still haven't been updated with native support, so they wouldn't be usable while running Live native. I really don't understand the hold up since some of my plugins were updated almost immediately after the original M1 was released.
    - spacechild1 5y ago
      > so they wouldn't be usable while running Live native Live still doesn't have built-in bit bridging? (Of course, bit bridging doesn't come free.)

officeplant 5y ago

Even the M1 port of Chrome is clunky, but then again chrome has always been clunky with MacOS. Firefox's M1 port actually got me to finally start transitioning out of chrome after being a fairly devoted chrome user since it released. It's the only third party browser on M1 macs that comes close to Safari in speed and handles window size changes (especially when video is playing) leagues better than Chrome.

FireBeyond 5y ago
Chrome completely crashes a few times a week on my M1 Max laptop. Very frustrating. Not even necessarily when I'm doing something actively, or intensively. I can have HN open as my only tab, be reading an article and I look back at the screen and Chrome has gone.

glandium 5y ago

Note that one part of this is that llvm is significantly faster to generate code for arm64 than for x86_64. I'm not saying that accounts for all the difference, but it helps.

thatswrong0 5y ago

Yet even still under Rosetta, my M1 Pro can handle more than twice as much "stuff" in my Ableton projects vs. my 2018 MBP, all while barely heating up and without _any_ fan noise (whereas my 2018 MBP starts sounding like a jet engine almost immediately after opening any sizeable project). So for me, its performance completely lives up to the hype. I don't think I'll need a new machine for a loooong time.

herpderperator 5y ago
Imagine how much better it will be with the native build: https://www.ableton.com/en/blog/live-111-apple-silicon-support-now-in-public-beta/ https://www.ableton.com/en/blog/live-111-apple-silicon-suppo...
- thatswrong0 5y ago
  The main issue with that is a looot of plugins I rely on day to day still haven't been updated with native support, so they wouldn't be usable while running Live native. I really don't understand the hold up since some of my plugins were updated almost immediately after the original M1 was released.
  - spacechild1 5y ago
    > so they wouldn't be usable while running Live native Live still doesn't have built-in bit bridging? (Of course, bit bridging doesn't come free.)