I mean, I understand that swap does not have to be avoided at all costs. But if you're starting with 16GB RAM and a couple GB of swap now, think of how it might be in 5 or 8 years that these machines should easily last. At least they should if you give them 32GB right from the beginning. For light users the same reasoning could apply to 8GB vs 16GB, depends on what you are doing of course.
I don't think you and I are disagreeing that much, just degree of emphasis (now that you're no longer fetishizing ram ?).
I'd distinguish with a bit more nuance between cases:
-When one starts up and has one's basic set of "these are the apps and windows I need" and you have some swap already, that's not great and yes, doesn't leave much headroom for future changes in usage or app bloat.
...vs...
-You get to something close to your 'max' usage profile (apps, windows open, etc) - but notably still a plausible workflow/workload, not some hypothetical stress case - and you see some yellow and are in mid-range memory pressure, you're probably okay for some time to come. (I'm thinking about this because I think with 16gb I'd be somewhere in between these two, at 32gb I'd be way more than I need - and I have a desktop with 32gb so maybe not justifiable to max out)
BTW for those interested - requires a bit more work - I think this "there is some swap in the activity monitor therefore I need more memory" or "I see some yellow" is just wrong and overly simplistic (memory pressure just being an attempt to simplify it).
What matters is not that there IS some swap on disk but whether it is being actively used (actively swapping). The easiest way I know to check this is terminal > top and watch the numbers swapin, swapout - if they're changing actively and frequently, in normal workloads, that's not great - if they're changing all the time (most of the time), that's actively bad.
To explain a bit - it's fine and normal and good if the system swaps out stuff you aren't actively using - say, you have some large app you leave open but only refer to once an hour, or if you have system programs or other low priority stuff that run periodically (or many other examples). Eg, the system swaps that stuff back into active memory once an hour, does its thing, and in due course gets swapped out - you may never notice. (Actually time machine, or part of time machine's routines, may be a good example - it might actually use a lot of memory but only for several minutes and then reverts to waiting).
Right now for example I have 20-odd programs 'open' and about 20gb memory used, but that's a stupid number of programs and I'm only actively using two or three (this is not normal for me, just leftover from a small thing). On a 16gb system that'd probably show some swap but the swap wouldn't be active and would be irrelevant basically, would have basically zero impact on performance.