The new models are a lot more expensive though. And the entry level model of the 14 inch has an 8 core variant of the m1 pro, which probably will not perform that much higher than the 8 core m1 in the 13 inch.

same for my m1 air! :D... but then I remembered that apple does trade ins! :D

M1 air and not at all feeling this way.

The original M1 pro had a touchbar, that alone make it suck. But the M1 is still thinner by a mile and has no fan!

Many people overlook this but no fan means no dirt will get into the chasis. That is HUGE.

I guess M1 Air is targeted towards execs, business crowd, marketers and such who's primary day job is not into creating, not something that'd require Pro level capabilities anyway.

The M1 Air is the best laptop for the average casual laptop user (school, emails, photos, etc). The battery life alone makes it a huge upgrade over any Windows machine. I also love that it doesn't have any fans, side that's usually the first thing to go on any laptop. I expect to get years and years of good use out of the Air.

Or programmer. We don't need that much juice really.

If our stuff makes M1 runs slow ... It's probably poorly optimized code.

Of course game dev is exempt from this.

I already have an M1 Air, and I'm looking to buy the 14 MBP just for the display (working outdoors yay), battery life, and RAM (16GB + higher bandwith). There's enough horsepower on the M1 for me, not even noticeable compared to the i7 MBP 16.

The 14” has several hours less of battery than the M1 Air. Dealbreaker if I’m honest. https://www.apple.com/mac/compare/?modelList=MacBook-Air-M1,...

That's.. interesting. Seems like the "wireless web" stat is really helped by the additional 2 efficiency cores on the Air, while the video stat is helped by the dedicated media silicon on the new Pro. Not to mention on what brightness (40% brightness on Pro is 100% brightness on air). Good to keep in mind.

Many types of programming require big resources these day. Training machine learning model is the classical example.

But also those who run multiple VMs at the same time.

> But also those who run multiple VMs at the same time.

I tried this route a few years ago but gave up out of sheer frustration. I wonder if it's improved now. At this point I'm more inclined to setup my local stack in AWS and be done with it. Like no local laptop testing at all.