Yes, hiring and training is expensive... and the loss of domain knowledge is costly too.
There are a lot of places that aren't making that much money to be able to get to "market rate".
I'd also like to put forth that the idea of a market rate for developers across all industries is one of the things making it hard to find developers. There are more than a few new grads out there that are discounting any job that pays less than $100k/y because they believe that the market rate is that and anything less is being underpaid regardless of industry, company maturity, or locale.
I was reasonably paid for the area. Sure, I could have been making more if I was to go to a different company (challenging in '09). I'm making more now for a different employer in the midwest.
The thing is that there are companies that don't make $100k/y revenue for the work that the devs do. There are also devs who are willing to work for $50k/y in the rural midwest (which is better than other jobs in the area pay).
To assume that those devs should be paid the same as one in SF would have ultimately meant a loss of jobs in the area as the business wouldn't be able to afford to do that.
There are plenty of places that are not the mid west that are paying more.
I think it's always important to keep in mind that current developer salaries are the result of a constrained market and not because we innately deserve it or something. Yes it is a high-skill job, but there are plenty of high-skill jobs out there that pay much less.
I spent the first twenty years of my career as a public school teacher, and the last four as a software engineer.
Most of the teachers I knew worked _literally_ twice as hard as the average software engineer I know now, even though they're paid one third as much.
And finding good teachers is just as difficult as finding good ICs. I think the ONLY difference is that it is possible for a lot more people to teach badly than to code badly. And of course that society has decided that teachers aren't worth paying very much.
More specifically as an employee, I think any incremental value from holding the stock is not compensation FROM the company, since the employee equally has to carry the risk of stock prices going down.
Of course, practically, one's cash flow in any given year is "base + bonus + actual value of the stock that vests in the given year" and can be vastly different from how the company does compensation planning. And this is also what determines income taxes (unless I'm bizarrely mistaken about how income taxes work in some jurisdictions).
Having been a manager at multiple public tech companies, I'll say that this has led to very many 'interesting' comp conversations and not everyone comprehends the distinctions here -- regardless of what's arguably more 'correct'.
For the same reason a manager isn't going to value a $10MM grant in company that ended up being a penny stock, he isn't going to downgrade a company that resurrected from the pits either. Money in hand last year is the best measure possible/available.
edit: and then people will come on here and say "look! Brand new Google employees make 200k!"
Looking at how they handle Google, for example they show base|annual stock|signing bonus.
So when you see 130K base + 33K stock, that was a grant of 130K vesting over 4 years. And then with signing and annual bonus of ~20K, that person is in fact making 200K starting (although the median is probably a bit lower for a completely new employee).
On the other hand, people often forget about refreshes when looking at these things. And while a refresh grant won't be as large as the initial grant, they do make the overall comp significantly larger.
In later years the situation is more complicated as the stock price will move, you'll receive annual refreshes which are performance dependent, and you might reach a new level. While the base salary changes with levels can be modest, 15% or so, refresher targets can practically double from level to level.
But yes - these won't be the public / known numbers. These folks have no incentive to make it public and affect their own future numbers.
We see this for example on a larger scale in OLED tech, where a key OLED engineer in South Korea might be worth $250k to the Korean Economy but worth $2.5M to the Chinese economy, which is why poaching was halted by classifying the job as a national security interest.
The profit/employee ratio at Apple is over a million dollars, so a valuable tech employee there should be making seven figures. That kills MBA’s brains (and the traditional power structure), which is why the cartel worked behind the scenes on wage suppression.