Jump to content

Talk:Expenditure cascades

Page contents not supported in other languages.
From Wikipedia, the free encyclopedia

Totally disputed

[edit]

In addition to probably being a neologism, there are clear misstatements and highly questionable statements in the article, as well as the clear rejection of the (probably minority) view that Reaganomics may have produced the reverse of these "cascades", whereby expenditures of the rich reduced (relative) expenditures of the poor. — Arthur Rubin (talk) 00:27, 12 December 2008 (UTC)[reply]

This article definitely has problems in POV and in organization. I was tempted to agree with your point about it being a neologism, but did this google scholar search and there's some stuff there which isn't by Robert Frank, so it is a term which gets some use. Not sure it deserves an article, but it doesn't seem completely unreasonable. CRETOG8(t/c) 03:07, 12 December 2008 (UTC)[reply]

PROD removed

[edit]

Neither neutral or current

[edit]

This article lacks neutral POV. It way over-emphasizes the importance of tax policy. Recent history has shown that inequality and progressive taxation can be mutually reinforcing, like here in California; progressive tax bases are highly unstable, so governments start protecting the incomes and assets of the wealthy. But they can only do this by cutting taxes for everyone else, making the tax code even more progressive and unstable and necessitating even more government favoritism of wealthy tax-generating sectors, in a never-ending spiral that leads to, well, Silicon Valley.

The article should at least mention other possible causes of inequality, like skill-biased technological change, the imbalance between skilled and unskilled migration between major industrialized countries, the decline of trade unions, the closure of urban cores to non-wealthy outsiders, etc. Or just the simple fact that many European countries have less progressive tax codes than the United States but more equal income distributions. Joeedh (talk) 08:29, 24 January 2019 (UTC)[reply]