[seaghost]

At the current job I don't need virtualization but might need it in future at which point most apps will be optimized and fixed I guess.

[reader_mode]

Check if your dev environment is supported - but if it is Apple looks really really good.

Why go for Air tho ? Pro looks like a better device (better screen, better battery, same dimensions) and it's marginally more expensive.

[pornel]

I see no point choosing M1 Pro over M1 Air as a dev machine. $300 extra buys you mostly the TouchBar.

Air has a better form factor (no sharp edge under wrists). Better keyboard (real top row). Both have essentially the same specs. Battery life on both is an overkill. Active cooling makes relatively small difference and kicks in only in long workloads (longer than a reasonable build should take).

[reader_mode]

I use laptop keyboard 5% of the time, but I use the laptop screen as a secondary monitor constantly.

I can't judge the battery - but it's for sure going to stay useful for longer as capacity degrades.

[thekyle]

As far as I can tell the Air and Pro get basically the same performance for the first 10 minutes. After that the Air will throttle. There is no task I would do that will max out the CPU for 10+ minutes so I don't see any reason to spend the extra for a slightly brighter (but otherwise the same) screen and two more hours of battery life (18 vs 20).

[reader_mode]

Well as I can tell from fan noise levels on my current MBP - running a device simulator or a VM along with a IDE is sustained load for sure.

[thekyle]

You may want to check the Activity Monitor to make sure the CPU is actually at 100% when you're doing that. Apparently it's quite easy to get the fans going on the Intel Macs even on lighter loads compared to the new M1 ones.

[seaghost]

I use my computer mostly in the desktop mode with external screen, so I don't really care about screen quality, but I need certain mobility and I don't want mini.