I don't think it's useful to account for time spent outside of work by the same hourly income as a way to measure how much something costs. By that logic, spending an hour listening would also "cost" $300.
FEIE is only one of the options for avoiding federal income tax. The other is the Foreign Tax Credit, which has no such limit: https://www.irs.gov/pub/irs-pdf/f1116.pdf. If the place an American lives and works has a higher income tax rate than the US one, in practice he will not face any tax liability, regardless of income level.
The reason there will never be enough lanes is not population growth. It's that we generally don't provide people with alternatives to driving, and adding more lanes just makes even more people have to drive, since things get even farther apart.
This may be a good summary of the blog post, but in my opinion it is an uninformed understanding of Elm and Elm's history. JavaScript FFI isn't and never has been a "critical language feature". Rather, people discovered an implementation detail that allowed them to create thin Elm wrappers around JS libs (think Elm interface for d3, leaflet, moment, etc...). This was (rightly IMO) seen as undesirable for multiple reasons and 0.19 closed off the loophole at the compiler level.
As for being banned from the community, I keep seeing this claim but have never seen or heard of such things happening. Sure, there may be a negative reception to folks who keep wanting to re-litigate a decision that was made over and over, but nobody has been banned from anything.
For me, the best monitors by far for programming are LG's 28in DualUp, due to the aspect ratio. I have a pair side by side, and it's effectively four 1440p screens in a 2x2 layout, giving lots of vertical space without a bezel as well as horizonal on each screen.