> What do you find lacking in the m1 to make it your dev machine?
For me, the 16GB RAM limit on the MacBook Air is the principal reason not to get one, otherwise I would have already. As soon as you go to 32GB or more with M1, it's a big price jump to the Pro range, not sub $2000 any more.
I have been looking at the M1 MBPs, but the price makes it need justification, and the 2.5 months lead time even at Apple stores for the higher models, has kept me from committing. And when I tried the MBP keyboard in store, it felt not as good as the old Firefox in daily use is constantly swapping on my older MBP that has 16GB RAM, and when I used Safari, it wasn't any better. (It was the trigger that made me go back to Firefox, as it used less memory than Safari when I switched). It quickly rises from 10GB to using 30GB after a little browsing; I've seen it go up to 67GB. Some sites will do that with just one tab open. It took me a long time to realise that's why browsing was so janky and pausing a lot, and back when I used Safari everything else paused often too. So I'd not be eager to buy a new laptop with the same problem.
Perhaps the Linux dev VM and several Electron-based communication apps that have to be running constantly add up, but it always seems to be the browser that grows to use much more memory than there is available.
With Firefox it seems to be a fixable software problem, because when it's triggered to release memory it will drop as fast as it can swap in, with no apparent affect except a long pause. I expect it's all cache. The memory statistics fluctuate very rapidly sometimes, gaining several GB in seconds, even when just clicking around text-only sites like HN.
But it's not realistically going to be fixed, so I think it best to get at least 32GB RAM for the next machine, whether it's a Macbook or not.