If you're coding in lots of explicit memory reference deletes, what you're writing is not C++ but C. A C++ codebase would use RRID and automatic memory management to obviate the need for any explicit memory management. My last C++ project at work contained zero (yes, zero) calls to delete/free() out of around 20000 lines of code and a year of development/testing.

You're making the same mistake you're accusing C++ developers of making - you're viewing C++ through Java lenses.

Well, you need to take GP's point to its logical conclusion - use references everywhere. The problem with C pointers is that they have overloaded semantics - they're used for pointing to heap memory (which is the only place you need NULL) as well as for call-by-reference (for performance). C++ obviates the need for pointers in both instances. No, I'm not saying I never use pointers in C++, but they're rare, as rare as say, the "static" keyword.

Allow me to elaborate.

> In theory they can't lay off a ton of people in the US without pushing the H1B's out the door first
Wrong. Only applies if the more than 15% of the company is on an H1B.

> their most cost effective workers
Wrong. Microsoft does not (and cannot) pay employees differently based on visa status. In fact, thanks to annual visa renewal fees, visa-stamping travel reimbursements, green-card processing fees, "premium processing" fees (where do you think USCIS gets its money from?), H1B employees are per capita more expensive to hire.

Yes, I used to work for Microsoft on an H1B.