On the initial view, only the 40th to 60th percentiles are shown. On subsequent views, only the 25th to 75th percentiles are shown. There are many above those ranges, including some outliers with 3% or more of their company (choose Scientist > Fellow for one example).
Also, according to the Source line at the bottom, executives and founders are excluded from the data set. Getting a large share of equity of a private company is rare for everyone else.
If you're working with a legacy repository, quit your job. Work somewhere where you are empowered to do what will make you and your team more efficient. I nuked trailing whitespace in our whole repo at wealthfront when I added the whitespace check to our pre-commit hook.
You've missed the point. 90% of Rails websites behave badly every time they're deployed, and the developers don't even realize it. I included our build scripts in the post to illustrate how simple it is to fix the problem. The important thing is that people reliably version their asset URIs, not what tools they use to do it.
Got a link to details? I'd be surprised, since any correct solution requires two-stage deployment and keeping old assets around. These capabilities are beyond the scope of a web server framework. The Rails team could certainly educate Rails developers and choose conventions that make correctness easier.
But any dynamic processing of stylesheets sacrifices performance. It means they have to be served by Rails. Preprocessing before deployment frees you to host them anywhere, ideally closer to your users.
Call it "Trump Linux"! :)