If I'm not mistaken we are mostly in agreement: wifi worked better (properly) with Snow Leopard, it does not work as well with Lion, and in most cases the only "variable" is the OS upgrade. Apple needs to sort this, various hokus-pokus may help some lucky people in some specific situations, but the clear truth is Apple screwed up the wireless networking with Lion.
This is exactly the situation for me. We have a bog-standard Netgear home router. Doesn't matter if it's G, N, or Z - it's bog-standard and it worked, the Macbook Pro was fine with it, my PC laptops always were fine with it (and still are). At home, the MBP always sits on the kitchen table in the same place (it hasn't moved); the router sits on a bookshelf in the sitting room (it too hasn't moved); my PC laptops (we have 2) both worked before, both still work, anywhere in the house. And previously if we DID move the MBP to another room, it too worked.
I am no computer technician, but I am capable of basic logic. Prior to the upgrade to Lion the wireless worked flawlessly on the MBP. From the first time I ever used Lion, and ever since, the wireless has not worked properly (not to mention printer drivers which don't work, Time Machine-compatible drives which are no longer compatible, and a multitude of other things which used to work find but now don't). Like others I was sucked-in by the snazzy marketing promo video (gestures, full screen, etc) and now have a machine that is verging on unusable, not to mention a seriously p****d-off wife (it's her MBP!!).
I can only echo the comments of others. We expect this from Microsoft. We are used to MUCH better from Apple. I presume the commercial imperative to get this out to sell new MBAs is what drove a clearly poorly-tested, seriously-flawed OS to be launched by a Company from whom we do not expect such behaviour. Hopefully (a) salutory lesson learned by Apple, although may be wishful thinking on my part, and (b) more important hope they launch upgrade soon which resolves these issues.
Meanwhile I will check out of this conversation since, after 22 pages, I think it's time to acknowledge this is not something users can fix for ourselves.