I would, perhaps, take that thread with a big grain of salt. From the commit charges on most of those machines, they all need to be taught how to tweak their boxes.
Besides, the way in which actual RAM usage correlates to swap file usage is much more complex than the OS thinking "I'm almost outta RAM, let's swap". Even a machine with 4GB of RAM will swap (I point this out because 32-bit processors cannot address more than 4GB unless they're operating in a special mode called PAE, or Physical Address Extensions, which aren't available in any OS other than Windows Enterprise of various versions and a couple of builds of Linux kernels).
To the point, 1GB of RAM is likely advantageous to anyone who ever sees a commit charge greater 256MB which I suspect is most of us who do any complex projects.
However, as with all blanket recommendations, there are caveats.
For one, the system origin (OEM or DIY) and memory configuration play a role in how well the memory subsystem performs. For example, a major OEM box (Dell, HP, whatever) that is stuffed to the gills with DIMMS (say, 4 256MB DIMMS) will not perform the same as a system with 2 512MB DIMMS. OEM BIOSes are nearly universally tweaked for absolute system stability (and end-user stupidity) such that when the memory bus is heavily loaded (as would be with the greater number of DIMMs) the timings for memory access are slackened, thus reducing subsystem performance. Most DIY boards from quality manufacturers do not protect the end-user in such a way. If said end-user has purchased sub-par DIMMs (from which the OEMs want to distance their product's instability), these boards will gladly let that person hang themselves. Good boards will still be affected by the additional memory modules, but to a level that is easily offset by the performance gain from more memory if it is needed (say, going from 2 256MB DIMMs to four if you need 1GB of RAM).
Of course, if you're looking to add RAM, I would first suggest that you exhaust all avenues of system tweaking. It's generally free (time spent is all it costs), and it can additionallly yield rewards of greater available processor time. I mean, look at the services list on a default WinXP box. Do you really need Remote Registry or Wireless Zero Configuration on your DAW(these are just two of many examples)?