text:
Cohen heads to Springfield with signatures
June 20, 2010 (CHICAGO)
Now he's going to file those petitions with the Illinois State Board of Elections before Monday's deadline. Those signatures are now on their way to Springfield.
Scott Lee Cohen and his running mate Baxter Swilley are en route to Springfield. Before they left, Cohen took a jab at Governor Patrick Quinn and the different requirements for incumbents to be on the ballot.
Cohen rolled out a stack of papers that represent 133,170 signatures, he said, no Sunday. Cohen hopes the signatures will put him on the ballot for governor as an independent. His day of politicking began with a life-sized cutout of the Democratic nominee and incumbent Governor Pat Quinn.
"What the petition process is is nothing short of an incumbent, career politician protection plan," said Cohen.
In February an emotional Cohen pulled out of the race for lieutenant governor. Cohen was the democratic nominee for lieutenant governor, but allegations of domestic violence, sexual abuse and steroid abuse surfaced.
At the time, he said it was for the good of the people for him to resign. But now Cohen says he's what Illinois needs.
"I believe in my heart that I have the tools that are necessary to bring businesses back to Illinois, to put people back to work," said Cohen.
Governor Quinn addressed Cohen's attempt to run for governor while at a father's day event to promote men's wellness.
"I think competition is good, whether it's in sports, business, economics or government or politics. So anybody who wants to run for governor, the water's fine. You gotta expect though when you get into the water some tough questions," said Quinn.
The Republican nominee for governor is Bill Brady, whose spokesperson issued a statement:
"No matter who is on the ballot- Bill Brady will continue to talk to voters in Chicagoland and throughout the state about the need for a strong jobs climate that puts people to work, his plan to reign in uncontrolled government spending and a clean break from the politics of the past."
Regarding Cohen's previous behavior and allegations of behavior, he would only say the past is the past.
Cohen said some of those who signed petitions are people who voted for him in the primary and he also expects the other candidates to challenge his petitions.


In Rome. Beach, Lake, Mountain, Tourist.
May and June are the best times to visit, as far as the weather goes. Spring weather can be quite changeable, especially in March and April, with sunny skies in the morning and storms in the afternoon. May and June can be very pleasant, but temperatures often climb above 85 F/30 C in July and August. High humidity (around 85%) causes most locals to flee the city toward the end of summer. Fall remains sunny, with October and November mild but sometimes rainy. September-November is a nice time to visit—the weather's good for touring around, and you'll miss the early-summer crowds. Winters are generally mild, with January lows around 40 F/5 C. Rome receives snow about once every five years, and when it does, public transport tends to stop, and getting around the city can be difficult.


What Is IESnare and How Do I Block It?
Have you ever stopped to wonder whether your online activity is as private as you'd like it to be? Or are you being spied upon every time that you do something?
What is IESnare and can it help the bookies to keep an eye on you? Even more importantly, what can you do about it? Let's see what it is all about.
Betconnect Review – Is it legit?
Are you looking for new ways to bet? Maybe you would like to find out what the experts bet on? Following tipsters has long been a popular approach. But is there a more modern way to do this now? Well, there are now far more ways of betting than ever before. So it was time that pro bettors got a new platform. This Betconnect review looks at an interesting new betting service. Basically, it takes the idea of pro tipsters and gives it a novel twist. Let's take a look at the full details in this Betconnect review.
Winning money from the bookies is all well and good. In fact, this is something that can make life so much better. Matched betting can give you a hefty second income when you stick to the right approach. Yet, might you end up being tempted to gamble money? Maybe you will end up taking unnecessary risks with your cash. This is something that could creep up on you little by little. But what would it mean for your betting and for your life?
Does the idea of betting for a living sound good to you? If you want to change your life then this is a great way of doing so. What do you need to know about becoming a professional bettor? Let's get started with the basics.
In most cases, you will place bets and collect your winnings with out any fuss. Gambling is regulated in the UK and bookies need to be licensed in order to operate. But if you have problems with a bookie then what should you do? Can you hope to see it resolved in your favour? You definitely don't want to just give up without a fight. Read my article to find out more.
I've written about the mysterious Betfair trader called Psychoff. Does he really make £50K per month? What strategies does he use to make his profits? Read my article to find out more.


text:
More info on Social Security debate (United States)
Social Security debate (United States): Map
Categories: Social Security (United States) > United States economic policy > Article Feedback Pilot
This article concerns proposals to change the Social Security system in the United States . Social Security is a social insurance program officially called "Old-Age, Survivors, and Disability Insurance" (OASDI), in reference to its three components. It is primarily funded through a dedicated payroll tax. During 2008, total benefits of $625 billion were paid out versus income (taxes and interest) of $805 billion, a $180 billion annual surplus. An estimated 162 million people paid into the program and 51 million received benefits, roughly 3.2 workers per beneficiary.
Reform proposals continue to circulate with some urgency, due to a long-term funding challenge faced by the program. Starting in 2016, program expenses begin to exceed revenues. This is due to the aging of the baby-boom generation (resulting in a lower ratio of paying workers to retirees), expected continuing low birth rate (compared to the baby-boom period), and increasing life expectancy. Further, the government has borrowed and spent the accumulated surplus funds, called the Social Security Trust Fund, while counting the funds as revenue, not debt. During 2008, the fund held $2.4 trillion in government bonds—essentially "IOUs" or claims on the government's general fund or tax revenues. This amount is part of the total national debt of $11.3 trillion as of May 12, 2009. By 2016, the government is expected to have borrowed nearly $3.7 trillion against the Social Security Trust fund. Between 2016 and 2037, Social Security has the legal authority to draw amounts from other government tax sources besides the payroll tax, to fully fund the program. However, this will liquidate the Trust Fund during that period. By 2037, the Trust Fund is expected to be officially exhausted, meaning that only the ongoing payroll tax collections thereafter will be available to fund the program. There are certain key implications to understand under current law, if no reforms are implemented:
Payroll taxes will only cover 76% of the scheduled payout amounts after 2037. This declines to 74% by 2083. Without changes to the law, Social Security would have no legal authority to draw other government funds to cover the shortfall and payments would decline without a large tax increase.
Between 2016 and 2037, redemption of the trust fund balance to pay retirees will draw $3.7 trillion in government funds from sources other than payroll taxes. This is a funding challenge for the government overall, not just Social Security.
The present value of unfunded obligations under Social Security as of January 1, 2009 was approximately $5.3 trillion. In other words, this amount would have to be set aside today such that the principal and interest would cover the shortfall over the next 75 years. The estimated annual shortfall averages 1.9% of the payroll tax base or 0.7% of gross domestic product.
Former President George W. Bush called for a transition to a combination of a government-funded program and personal accounts ("individual accounts" or "private accounts") through partial privatization of the system. President Barack Obama "strongly opposes" privatization or raising the retirement age, but supports raising the cap on the payroll tax ($106,800 in 2009) to help fund the program.
Federal Reserve Chairman Ben Bernanke said on October 4, 2006: "Reform of our unsustainable entitlement programs should be a priority." He added, "the imperative to undertake reform earlier rather than later is great." The tax increases or benefit cuts required to maintain the system as it exists under current law are significantly higher the longer such changes are delayed. For example, raising the payroll tax rate to 14.4% during 2009 (from the current 12.4%) or cutting benefits by 13.3% would address the program's budgetary concerns indefinitely; these amounts increase to around 16% and 24% if no changes are made until 2037.
Background on funding challenges
Social Security is funded through the Federal Insurance Contributions Act , which is a payroll tax paid equally by the employee and the employer. During 2009, Social Security taxes will be levied on the first $106,800 of worker income; amounts earned above that are not taxed. Covered workers are eligible for retirement benefits and for disability benefits; if a covered worker dies, his or her spouse and children may receive survivors' benefits. The program does not have individual accounts and tax receipts are not invested on behalf of the worker. Instead, current receipts are used to pay current benefits (the system known as "pay-as-you-go"), as is typical of some insurance and defined-benefit plans.
In each year since 1983, tax receipts and other income have exceeded benefit payments and other expenditures, most recently (in 2008) by more than $180 billion. However, this annual "surplus" is expected to change to a deficit around 2016, when payments begin to exceed receipts. The fiscal pressures are due to demographic trends, where the number of workers paying into the program continues declining relative to those receiving benefits. The number of workers paying into the program was 6.1 per retiree in 1960; this declined to 3.2 in 2008 and is projected to decline to 2.1 by 2040. Further, life expectancy continues to increase, meaning retirees collect benefits longer. Federal Reserve Chairman Bernanke has indicated that the aging of the population is a long-term trend, rather than a proverbial "pig moving through the python."
The accumulated surpluses are invested in Treasury securities (treasuries) issued by the U.S. government, which are deposited in the Social Security Trust Fund. At the end of 2008, the Trust Fund stood at $2.4 trillion. The $2.4 trillion amount owed by the federal government to the Social Security Trust Fund is also a component of the U.S. National Debt, which stood at $11.3 trillion as of May 12, 2009. By 2016, the government is expected to have borrowed nearly $3.7 trillion against the Social Security Trust Fund.
The value of unfunded obligations under Social Security during FY 2007 was approximately $5.3 trillion. In other words, this amount would have to be set aside today such that the principal and interest would cover the shortfall over the next 75 years. This is 1.9% of the payroll tax base or 0.7% of gross domestic product each year.
Because Social Security receipts currently exceed payments, the program also reduces the size of the annual federal budget deficit. For example, the budget deficit would have been $182 billion higher in 2007 (i.e., $344 billion rather than $162 billion published) if Social Security were accounted for separately from the overall budget.
Increasing unemployment due to the subprime mortgage crisis has significantly reduced the amount of payroll tax income that funds Social Security. The CBO projects that the "primary surplus" (i.e., cash tax collections less cash payouts) has declined to an estimated $16 billion for 2009 and a $10 billion deficit for 2010. Since the Social Security Trust Fund will accrue approximately $120 billion annually in interest during 2009 and 2010, the "surplus" (including interest) is projected to be $136 billion and $108 billion in those years, respectively. The crisis and recession of 2008-2009 also caused more to apply for both retirement and disability benefits than expected.
Current projections
Projections were made by the Board of Trustees of the Federal Old-Age and Survivors Insurance and Federal Disability Insurance Trust Funds (OASDI) in their 69th annual report dated May 12, 2009. According to these projections, based on the system's current revenue and benefit structure, expenses will exceed tax receipts beginning in 2016. The trust fund is projected to continue to grow for several years thereafter because the analyses assume interest income from loans made to the US Treasury is available to cover the difference. However, the funds from loans made have been spent along with other revenues in the general funds in satisfying annual budgets. At some point, however, absent any change in the law, the Social Security Administration will finance payment of benefits through the net redemption of the assets in the trust fund. Because those assets consist solely of U.S. government securities, their redemption will represent a call on the federal government's general fund, which for decades has been borrowing the Trust Fund's surplus and applying it to its expenses to partially satisfy budget deficits. To finance such a projected call on the general fund, some combination of increasing taxes, cutting other government spending or programs, selling government assets, or borrowing would be required.
The balances in the trust fund are projected to be depleted either by 2037 (OASDI Trustees' 2009 projection), or by 2052 (Congressional Budget Office's projection) assuming proper and continuous repayment of the outstanding treasury notes. At that point, under current law, the system's benefits would have to be paid from the FICA tax alone. Revenues from FICA are projected at that point to be continue to cover about 76% of projected Social Security benefits if no change is made to the current tax and benefit schedules.
Cumulative OASDI Income Less Cost, Based on Present Law Tax Rates and Scheduled Benefits.
Source: 2008 OASDI Trustees Report.
Framing the debate
Framing: ideological arguments
Ideology plays a major part of framing the Social Security debate. Key points of philosophical debate include, among others:
degree of ownership and choice among investment alternatives in determining one's own financial future;
the right and extent of government taxation and wealth redistribution;
trade-offs between social insurance and wealth creation;
whether the program represents (or is perceived) as a charitable safety net (entitlement) or earned benefits; and
intergenerational equity, meaning the rights of those living today to impose burdens on future generations.
Retirees and others who receive Social Security benefits have become an important bloc of voters in the United States. Indeed, Social Security has been called "the third rail of American politics" — meaning that any politician sparking fears about cuts in benefits by touching the program endangers his or her political career. The New York Times wrote in January 2009 that Social Security and Medicare "have proved almost sacrosanct in political terms, even as they threaten to grow so large as to be unsustainable in the long run."
Conservative ideological arguments
Conservatives argue that Social Security reduces individual ownership by redistributing wealth from workers to retirees and bypassing the free market. Social Security taxes paid into the system cannot be passed to future generations, as private accounts can, thereby preventing the accumulation of wealth to some degree. Conservatives tend to argue for a fundamental change in the structure of the program.
Liberal ideological arguments
Liberals argue that government has the obligation to provide social insurance, through mandatory participation and broad program coverage. During 2004, Social Security constituted more than half of the income of nearly two-thirds of retired Americans. For one in six, it is their only income. Liberals tend to defend the current program, preferring limited tax and payment modifications.
Framing: Pro-privatization arguments
The conservative position is often pro-privatization. There are countries other than the U.S. that have set up individual accounts for individual workers, which allow workers leeway in decisions about the securities in which their accounts are invested, which pay workers after retirement through annuities funded by the individual accounts, and which allow the funds to be inherited by the workers' heirs. Such systems are referred to as 'privatized.' Currently, the United Kingdom , Sweden , and Chile are the most frequently cited examples of privatized systems. The experiences of these countries are being debated as part of the current Social Security controversy.
In the United States in the late 1990s, privatization found advocates who complained that U.S. workers, paying compulsory payroll taxes into Social Security, were missing out on the high rates of return of the U.S. stock market (the Dow averaged 5.3% compounded annually for the 20th century). They likened their proposed "Private Retirement Accounts" (PRAs) to the popular Individual Retirement Accounts (IRAs) and 401 savings plans. But in the meantime, several conservative and libertarian organizations that considered it a crucial issue, such as the Heritage Foundation and Cato Institute, continued to lobby for some form of Social Security privatization.
Framing: Anti-privatization arguments
The liberal position is typically anti-privatization. Those who have taken an anti-privatization position argue several points (among others), including:
Privatization does not address Social Security's long-term funding challenges. The program is "pay as you go," meaning current payroll taxes pay for current retirees. Diverting payroll taxes (or other sources of government funds) to fund private accounts would drive enormous deficits and borrowing ("transition costs").
Privatization converts the program from a "defined benefits" plan to a "defined contribution" plan, subjecting the ultimate payouts to stock or bond market fluctuations;
Social Security payouts are indexed to wages, which historically have exceeded inflation. As such, Social Security payments are protected from inflation, while private accounts might not be;
Privatization would represent a windfall for Wall Street financial institutions, who would obtain significant fees for managing private accounts.
Privatization in the midst of the greatest economic downturn since the Great Depression would have caused households to have lost even more of their assets, had their investments been invested in the U.S. stock market.
Is there a crisis?
The Trust Fund, under current law (blue) and under privatization (red) as per "Model 2" considered in the 2001 commission report.
(Graph from "Social Security Trust Fund" by zFacts.com)
Accordingly, advocates of major change in the system generally argue that drastic action is necessary because Social Security is facing a crisis. In his 2005 State of the Union speech, President Bush indicated that Social Security was facing "bankruptcy." In his 2006 State of the Union speech, he described entitlement reform (including Social Security) as a "national challenge" that, if not addressed timely, would "present future Congresses with impossible choices -- staggering tax increases, immense deficits, or deep cuts in every category of spending."
A liberal think tank, The Center for Economic and Policy Research, says that "Social Security is more financially sound today than it has been throughout most of its 69-year history" and that Bush's statement should have no credibility.
Nobel Laureate economist Paul Krugman, deriding what he called "the hype about a Social Security crisis," wrote:
The claims of the probability of future difficulty with the current Social Security system are largely based on the annual analysis made of the system and its prospects and reported by the governors of the Social Security system. While such analysis can never be 100% accurate, it can at least be made using different probable future scenarios and be based on rational assumptions and reach rational conclusions, with the conclusions being no better (in terms of predicting the future) than the assumptions on which the predictions are based. With these predictions in hand, it is possible to make at least some prediction of what the future retirement security of Americans who will rely on Social Security might be.
Proponents of the current system argue if and when the trust fund runs out, there will still be the choice of raising taxes or cutting benefits, or both. Advocates of the current system say that the projected deficits in Social Security are identical to the "prescription drug benefit" enacted in 2002. They say that demographic and revenue projections might turn out to be too pessimistic — and that the current health of the economy exceeds the assumptions used by the Social Security Administration.
These Social Security proponents argue that the correct plan is to fix Medicare, which is the largest underfunded entitlement, repeal the 2001–2004 revenue reductions, and balance the budget. They believe a growth trendline will emerge from these steps, and the government can alter the Social Security mix of taxes, benefits, benefit adjustments and retirement age to avoid future deficits. The age at which one begins to receive Social Security benefits has been raised several times since the program's inception.
Proposals that keep an entirely government-run system
Robert L. Clark, an economist at North Carolina State University who specializes in aging issues, formerly served as a chairman of a national panel on Social Security's financial status; he has said that future options for Social Security are clear: "You either raise taxes or you cut benefits. There are lots of ways to do both."
David Koitz, a 30-year veteran of the Congressional Research Service, echoed these remarks in his 2001 book Seeking Middle Ground on Social Security Reform: "The real choices for resolving the system's problems...require current lawmakers to raise revenue or cut spending--to change the law now to explicitly raise future taxes or constrain future benefits." He discusses the 1983 Social Security amendments that followed the Greenspan Commission's recommendations. It was the Commission's recommendations that provided political cover for both political parties to act. The changes approved by President Reagan in 1983 were phased in over time and included raising the retirement age from 65 to 67, taxation of benefits, cost of living adjustment (COLA) delays, and inclusion of new federal hires in the program. There was a key point during the debate when House members were forced to choose between raising the retirement age or raising future taxes; they chose the former. Senator Daniel Patrick Moynihan indicated the compromises involved showed that lawmakers could still govern. Koitz cautions against the concept of a free lunch; retirement security cannot be provided without benefit cuts or tax increases.
The AARP has described the ramifications of different policies:
Revenue raisers
Raise the cap to 90% of taxable earnings
Approximately 39% reduction in shortfall
PRO:Affects only 6% of taxpayers or top 15% of income.
Can be phased in gradually.
Not a new tax, restores prior policy.
CON:It's a tax increase for higher earners.
Increase payroll tax rate
Each 0.5% tax rate increase addresses 23% of shortfall.
PRO:A gradual increase would maintain 75-year solvency.
CON:A regressive tax increase that adversely affect workers.
Raise taxes on benefits
10% reduction in shortfall
This amounts to a reduction in the benefit to high wage earners so the pros and cons are purely subjective.
Preserve tax on estates over $3.5 million
PRO:Improves tax progressivity, affects only 1/2 of 1% of all estates.
CON:Would alter the president's tax-cutting plans.
Extend coverage to newly hired state and local government employees
PRO:Makes Social Security universal, with all sharing obligations and benefits.
CON:State and local governments employees might get less retirement benefits.
Invest 15% of the trust funds in stock and bond index funds
PRO:In the most optimistic scenario, the trust would earn higher returns on its investment.
CON:Since the US government has a debt, this amounts to borrowing money in bonds to invest in the stock market, or margin trading.
Cost of transition between $600 billion - $3 trillion.
Less likely scenarios involve lower or negative returns.
Cost trimmers
Adjust the COLA
PRO:Saves money.
CON:This would set the standard of living afforded by Social Security to the level the individual could achieve at their date of initial benefit.
The current plan allows for an increased standard of living based on productivity increases made in the US economy.
Increase normal retirement age to 70
PRO:Links retirement more closely to life expectancy and increased worker health since program inception.
CON:Reduces benefits.
Unfair to those forced to retire early but not otherwise eligible for other Social Security benefits.
Progressive Indexing - Index benefits to prices, not wages
100% reduction in shortfall
PRO:Could eliminate shortfall.
CON:Reduces the growth in scheduled benefits over time.
Barack Obama's proposals
As of September 14, 2008, Barack Obama indicated preliminary views on Social Security reform. His website indicated that he "will work with members of Congress from both parties to strengthen Social Security and prevent privatization while protecting middle class families from tax increases or benefit cuts. As part of a bipartisan plan that would be phased in over many years, he would ask families making over $250,000 to contribute a bit more to Social Security to keep it sound." He has opposed raising the retirement age, privatization, or cutting benefits.
Understanding the COLA and progressive indexing
The current system sets the initial benefit level based on the retiree's past wages. The benefit level is based on the 35 highest years. This initial amount is then subject to a "Cost of Living Adjustment" or COLA. During 2009, the COLA will be 5.8%, following a 2.3% adjustment in 2008. Reducing the COLA would reduce the funding shortfall because wages historically grow faster than prices via a process known as economic growth. Because Social Security benefits are currently indexed to wages, benefits are scheduled to grow faster than inflation, resulting in an increase in the monthly benefit check as the economy becomes more productive. It is important to note that there is disagreement about what actually constitutes a "benefit cut". The Center for Budget and Policy Priorities considers any reduction in future promised benefits to be a "cut". However, others dispute this assertion because under any indexing strategy the purchasing power of Social Security checks would never decrease, they would just increase at varying or lesser rates.
A variant of this approach is called "progressive indexing," which maintains benefits for the lowest wage workers while phasing out the currently larger benefits for higher-wage workers. The net result is essentially one level of benefits for all workers who earn at least $20,000 per year. The Congressional Research Service reported that:
"Progressive indexing," would index initial benefits for low earners to wage growth (as under current law), index initial benefits for high earners to price growth (resulting in lower projected benefits compared to current-law promised benefits), and index benefits for middle earners to a combination of wage growth and price growth.
One mechanism that had been suggested for reducing expenses is to replace this wage indexing with price indexing. Initial benefits would be lower if the past wages were brought forward based on the changes in the consumer price index, which tends to grow more slowly than average wages. Bush endorsed a version of this approach suggested by financier Robert Pozen, called "progressive indexing", which would mix price and wage indexing in setting the initial benefit level. The "progressive" feature is that the less generous price indexing would be used in greater proportion for retirees with higher incomes. The San Francisco Chronicle gave this explanation:
Under Pozen's plan, which is likely to be significantly altered even if the concept remains in legislation, all workers who earn more than about $25,000 a year would receive some benefit cuts.
For example, those who retire in 50 years while earning about $36,500 a year would see their benefits reduced by 20 percent from the benefits promised under the current plan.
Those who earn $90,000 — the maximum income in 2005 for payroll taxes — and retire in 2055 would see their benefits cut 37 percent.
As under the current system, all retirees would have their initial benefit amount adjusted periodically for price inflation occurring after their retirement. Thus, the purchasing power of the monthly benefit level would be frozen, as it is now.
Understanding adjustments to the payroll tax limit
During 2009, payroll taxes were levied on the first $106,800 of income; earnings above that amount are not taxed. Approximately 6% of the population earns over this amount, which represents approximately 15% of total wage income. Because of this limit, people with higher incomes pay a lower percentage of tax than people with lower incomes; the payroll tax is therefore a regressive tax. President Bush's 2001 advisory board discussed ways that the system could be adjusted. Eliminating the cap would make this a more progressive tax and would reduce or eliminate the projected deficit. A 2001 Social Security advisory board report stated:
Making all earnings covered by Social Security subject to the payroll tax beginning in 2002, but retaining the current law limit for benefit computations (in effect removing the link between earnings and benefits at higher earnings levels), would eliminate the deficit. If benefits were to be paid on the additional earnings, 88 percent of the deficit would be eliminated.
Diamond-Orszag Plan
Peter A. Diamond and Peter R. Orszag proposed in their 2005 book Saving Social Security-A Balanced Approach that Social Security be stabilized by various tax and spend adjustments and gradually ending the process by which the general fund has been borrowing from payroll taxes. This requires increased revenues devoted to Social Security. Their plan, as with several other Social Security stabilization plans, relies on gradually increasing the retirement age, raising the ceiling on which people must pay FICA (payroll) taxes, and slowly increasing the FICA tax rate to a peak of 15% total from the current 12.4%.
Conceptual arguments regarding privatization
Cost of transition and long-term funding concerns
Critics argue that privatizing Social Security does nothing to address the long-term funding concerns. Diverting funds to private accounts would reduce available funds to pay current retirees, requiring significant borrowing. An analysis by the Center on Budget and Policy Priorities estimates that President Bush's 2005 privatization proposal would add $1 trillion in new federal debt in its first decade of implementation and $3.5 trillion in the decade thereafter. The 2004 Economic Report of the President found that the federal budget deficit would be more than 1 percent of gross domestic product (GDP) higher every year for roughly two decades; U.S. GDP in 2008 was $14 trillion. The debt burden for every man, woman, and child would be $32,000 higher after 32 years because of privatization.
Privatization proponents counter that the savings to the government would come through a mechanism called a "clawback", where profits from private account investment would be taxed, or a benefit reduction meaning that individuals whose accounts underperformed the market would receive less than current benefit schedules, although, even in this instance, the heirs of those who die early could receive increased benefits even if the accounts underperformed historical returns.
Opponents of privatization also point out that, even conceding for sake of argument that what they call highly optimistic numbers are true, they fail to count what the transition will cost the country as a whole. Gary Thayer, chief economist for A.G. Edwards, has been cited in the mainstream media saying that the cost of privatizing— estimated by some at $1 trillion to $2 trillion— would worsen the federal budget deficit in the short term, and "That's not something I think the credit markets would appreciate." If, as in some plans, the interest expenditure on this debt is recaptured from the private accounts before any gains are available to the workers, then the net benefit could be small or nonexistent. And this is really a key to understanding the debate, because if, on the other hand, a system which mandated investment of all assets in U.S. Treasuries resulted in a positive net recapturing, this would illustrate that the captive nature of the system results in benefits that are lower than if it merely allowed investment in U.S. Treasuries (purported to be the safest investment on Earth).
Current Social Security system advocates claim that when the risks, overhead costs and borrowing costs of any privatization plan are taken together, the result is that such a plan has a lower expected rate of return than "pay as you go" systems. They point out the high overheads of privatized plans in the United Kingdom and Chile.
Rate of return and individual initiative
Even some of those who oppose privatization agree that if current future promises to the current young generation are kept in the future, they will experience a much lower rate of return than past retirees have. Under privatization, each worker's benefit would be the combination of a minimum guaranteed benefit and the return on the private account. The proponents' argument is that projected returns (higher than those individuals currently receive from Social Security) and ownership of the private accounts would allow lower spending on the guaranteed benefit, but possibly without any net loss of income to beneficiaries.
Both wholesale and partial privatization pose questions such as: 1) How much added risk will workers bear compared to the risks they face under current system? 2) What are the potential rewards? and 3) What happens at retirement to workers whose privatized risks turn out badly? For workers, privatization would mean smaller Social Security checks, in addition to increased compensation from returns on investments, according to historical precedent. Debate has ensued over the advisability of subjecting workers' retirement money to market risks.
Generally, privatization advocates believe that individuals are the best decision makers about how much risk they should undertake with their own retirement funds but do not show in any detail how individuals would have this power under as-yet-not-described privatization plans. The reality almost surely would be that individuals would be able to make choices at defined times among a limited set of investment options chosen by a government panel. This may fall very short of individuals truly being given the power of making their own decisions about how to invest their retirement money. Proponents of the current system counter that if those risks turn out badly, a political push by the same individuals to raise state benefits will be all but inevitable, which means that the risks such individuals may be willing to take under a privatized system are not without moral hazard.
Supporters of the current system maintain that its combination of low risks and low management costs, along with its social insurance provisions, work well for what the system was designed to provide: a baseline income for citizens derived from savings. From their perspective, the major deficiency of any privatization scheme is risk. Like any private investments, PRAs could fail to produce any return or could produce a lower return than proponents of privatization assert, and could even suffer a reduction in principal.
Advocates of privatization have long criticized Social Security for lower returns than the returns available from other investments, and cite numbers based on historical performance. The Heritage Foundation, a conservative think tank, calculates that a 40-year-old male with an income just under $60,000, will contribute $284,360 in payroll taxes to the Social Security trust fund over his working life, and can expect to receive $2,208 per month in return under the current program. They claim that the same 40-year-old male, investing the same $284,360 equally weighted into treasuries and high-grade corporate bonds over his working life, would own a PRA at retirement worth $904,982 which would pay an annuity of up to $7,372 per month (assuming that the dollar volume of such investments would not dilute yields so that they are lower than averages from a period in which no such dilution occurred.) Furthermore, they argue that the "efficiency" of the system should be measured not by costs as a percent of assets, but by returns after expenses (e.g. a 6% return reduced by 2% expenses would be preferable to a 3% return reduced by 1% expenses). Other advocates state that because privatization would increase the wealth of Social Security users, it would contribute to consumer spending, which in turn would cause economic growth.
Supporters of the current system argue that the long-term trend of U.S. securities markets cannot safely be extrapolated forward, because stock prices relative to earnings are already at very high levels by historical standards. They add that an exclusive focus on long-term trends would ignore the increased risks they think privatization would cause. The general upward trend has been punctuated by severe downturns. Critics of privatization point out that workers attempting to retire during any future such downturns, even if they prove to be temporary, will be placed at a severe disadvantage.
Proponents argue that a privatized system would open up new funds for investment in the economy, and would produce real growth. They claim that the treasuries held in the current trust fund are covering consumption rather than investments, and that their value rests solely upon the continued ability of the U.S. government to impose taxes. Michael Kinsley has said that there would be no net new funds for investment, because any money diverted into private accounts would produce a dollar-for-dollar increase in the federal government's borrowing from other sources to cover its general deficit.
Meanwhile, some investment-minded observers among those who do not support privatization, point out potential pitfalls to the trust fund's undiversified portfolio, containing only treasuries. Many of these support the government itself investing the trust fund into other securities, to help boost the system's overall soundness through diversification, in a plan similar to CalPERS in the state of California . Among the proponents of this idea were some members of President Bill Clinton's 1996 Social Security commission that studied the issue; the majority of the group supported partial privatization, and other members put forth the idea that Social Security funds should themselves be invested in the private markets to gain a higher rate of return.
The other major sector of opinion is that privatization accomplishes nothing, that rational investors would neutralize any benefit of, effectively, selling Treasury Notes and buying equities (see Modigliani-Miller theorem), that it places more risk on individual workers than it gives back in rewards since they cannot effectively vote their shares, but have no more protection than any other owner of common stock. These proponents argue that while "risk for reward" applies to the individual, the macro picture means that for every winner, there will be losers, and the government will be responsible for preventing those losers from slipping into poverty. This will mean an increase in expenditures for anti-poverty programs for the elderly, as it has for both Chile and Argentina .
Role of government
There are also substantive issues that do not involve economics, but rather the role of government. Conservative Nobel Prize-winning economist Gary S. Becker, currently a graduate professor at the University of Chicago , wrote in a February 15, 2005 article that "[privatization] reduce[s] the role of government in determining retirement ages and incomes, and improve[s] government accounting of revenues and spending obligations." He compares the privatization of Social Security to the privatization of the steel industry, citing similar "excellent reasons."
Management costs of private funds
Opponents of privatization also decry the increased management costs that any privatized system will incur. In Chile and the United Kingdom , as much as 30% of savings are reportedly being absorbed by fees. Since the U.S. system is passively managed — with no specific funds being tied to specific investments within individual accounts, and with the system's surpluses being automatically invested only in treasuries — its management costs are very low.
Advocates of privatization at the Cato Institute, a libertarian think tank, counter that, "Based on existing private pension plans, it appears reasonable to assume that the costs of administering a well-run system of PRAs might be anywhere from a low of roughly 15 basis points (0.15%) to a high of roughly 50 basis points (0.5%)." They also point to the low costs of index funds (funds whose value rises or falls according to a particular financial index), including an S&P 500 index fund whose management fees run between 8 basis point (0.08%) and 10 basis points (0.10%).
Windfall for Wall Street?
Opponents also claim that privatization will bring a windfall for Wall Street brokerages and mutual fund companies, who will rake in billions of dollars in management fees.
Austan Goolsbee at the University of Chicago has written a study, "The Fees of Private Accounts and the Impact of Social Security Privatization on Financial Managers," which calculates that, "Under Plan II of the President's Commission to Strengthen Social Security (CSSS), the net present value (NPV) of such payments would be $940 billion," and, "amounts to about one-quarter (25%) of the NPV of the revenue of the entire financial sector for the next 75 years," and concludes that, "The fees would be the largest windfall gain in American financial history." The Heritage Foundation has produced their own study, written by David C. John, specifically to counter Goolsbee.
Other analysts argue that dangers of a Wall Street windfall of such magnitude are being vastly overstated. Rob Mills, vice-president of the brokerage industry trade group Securities Industry Association, calculated in a report published in December 2004 that the proposed private accounts might generate $39 billion in fees, in NPV terms, over the next 75 years. This amount would represent only 1.2% of the sector's projected NPV revenues of $3.3 trillion over that timeframe. He concludes that privatization is "hardly likely to be a bonanza for Wall Street." At the same time, the watchdogs at FactCheck estimate that the financial management sector will receive only 0.05% and 0.27% of its total revenues from fees on PRAs.
Other privatization proposals
A range of other proposals have been suggested for partial privatization, such as the 7.65% Solution. One, suggested by a number of Republican candidates during the 2000 elections, would set aside an initially small but increasing percentage of each worker's payroll tax into a 'lockbox', which the worker would be allowed to invest in securities. Another eliminated the Social Security payroll tax completely for workers born after a certain date, and allowed workers of different ages different periods of time during which they could opt to not pay the payroll tax, in exchange for a proportional delay in their receipt of payouts.
George W. Bush's privatization proposal
President George W. Bush discussed the "partial privatization" of Social Security since the beginning of his presidency in 2001. But only after winning re-election in 2004 did he begin to invest his "political capital" in pursuing changes in earnest.
In May 2001, he announced establishment of a 16-member bipartisan commission "to study and report specific recommendations to preserve Social Security for seniors while building wealth for younger Americans", with the specific directive that it consider only how to incorporate "individually controlled, voluntary personal retirement accounts". The majority of members serving on Bill Clinton's similar Social Security commission in 1996 had recommended through their own report that partial privatization be implemented. Bush's Commission to Strengthen Social Security (CSSS) issued a report in December 2001 (revised in March 2002), which proposed three alternative plans for partial privatization:
Plan I: Up to two percent of taxable wages could be diverted from FICA and voluntarily placed by workers into private accounts for investment in stocks, bonds, and/or mutual funds.
Plan II: Up to four percent of taxable wages, up to a maximum of $1000, could be diverted from FICA and voluntarily placed by workers into private accounts for investment.
Plan III: One percent of wages on top of FICA, and 2.5% diverted from FICA up to a maximum of $1000, could be voluntarily placed by workers into private accounts for investment.
On February 2, 2005, Bush made Social Security a prominent theme of his State of the Union Address. In this speech, which sparked the debate, it was Plan II of CSSS's report that Bush outlined as the starting point for changes in Social Security. He outlined, in general terms, a proposal based on partial privatization. After a phase-in period, workers currently less than 55 years old would have the option to set aside four percentage points of their payroll taxes in individual accounts that could be invested in the private sector, in "a conservative mix of bonds and stock funds". Workers making such a choice might receive larger or smaller benefits than if they had not done so, depending on the performance of the investments they selected.
Although Bush described the Social Security system as "headed for bankruptcy," his proposal would not affect the projected shortfall in Social Security tax receipts. Partial privatization would mean that some workers would pay less into the system's general fund and receive less back from it. Administration officials said that the proposal would have a "net neutral effect" on the system's financial situation, and that Bush would discuss with Congress how to fill the projected shortfall. The Congressional Budget Office had previously analyzed the commission's "Plan II" (the plan most similar to Bush's proposal) and had concluded that the individual accounts would have little or no overall effect on the system's solvency, and that virtually all the savings would come instead from changing the benefits formula.
As illustrated by the CBO analysis, one possible approach to the shortfall would be benefit cuts that would affect all retirees, not just those choosing the private accounts. Bush alluded to this option, mentioning some suggestions that he linked to various former Democratic officeholders. He did not endorse any specific benefit cuts himself, however. He said only, "All these ideas are on the table." He expressed his opposition to any increase in Social Security taxes. Later that month, his press secretary, Scott McClellan, ambiguously characterized raising or eliminating the cap on income subject to the tax as a tax increase that Bush would oppose.
In his speech, Bush did not address the issue of how the system would continue to provide benefits for current and near-future retirees if some of the incoming Social Security tax receipts were to be diverted into private accounts. A few days later, however, Vice-President Dick Cheney stated that the plan would require borrowing $758 billion over the period 2005 to 2014; that estimate has been criticized as being unrealistically low.
On April 28, 2005, Bush held a televised press conference at which he provided additional detail about the proposal he favored. For the first time, he endorsed reducing the benefits that some retirees would receive. He endorsed a plan from Robert Pozen, described below in the section regarding suggestions for Social Security that do not involve privatization.
Although Bush's State of the Union speech left many important aspects of his proposal unspecified, debate began on the basis of the broad outline he had given.
Politics of the dispute over Bush's proposal
The political heat was turned up on the issue since Bush mentioned changing Social Security during the 2004 elections, and since he made it clear in his nationally televised January 2005 speech that he intended to work to partially privatize the system during his second term.
To assist the effort, Republican donors were asked after the election to help raise $50 million or more for a campaign in support of the proposal, with contributions expected from such sources as the conservative Club for Growth and the securities industry. In 1983, a Cato Institute paper had noted that privatization would require "mobilizing the various coalitions that stand to benefit from the change, ... the business community, and financial institutions in particular ..." Soon after Bush's State of the Union speech, the Club for Growth began running television advertisements in the districts of Republican members of Congress whom it identified as undecided on the issue.
A group backed by labor unions called "Americans United to Protect Social Security" "set its sights on killing Bush's privatization plan and silencing his warnings that Social Security was 'headed toward bankruptcy.'" Americans United to Protect Social Security later changed its name to Americans United for Change and rallied behind Obama's proposed 2009 economic stimulus bill.
On January 16, 2005, the New York Times reported internal Social Security Administration documents directing employees to disseminate the message that "Social Security's long-term financing problems are serious and need to be addressed soon," and to "insert solvency messages in all Social Security publications".
Coming soon after the disclosure of government payments to commentator Armstrong Williams to promote the No Child Left Behind Act, the revelation prompted the objection from Dana C. Duggins, a vice president of the Social Security Council of the American Federation of Government Employees, that "Trust fund dollars should not be used to promote a political agenda."
In the weeks following his State of the Union speech, Bush devoted considerable time and energy to campaigning for privatization. He held "town meetings" at many locations around the country. Attendance at these meetings was controlled to ensure that the crowds would be supportive of Bush's plan. In Denver , for example, three people who had obtained tickets through Representative Bob Beauprez, a Republican, were nevertheless ejected from the meeting before Bush appeared, because they had arrived at the event in a car with a bumper sticker reading "No More Blood for Oil".
Opponents of Bush's plan have analogized his dire predictions about Social Security to similar statements that he made to muster support for the 2003 Invasion of Iraq.
A dispute between the AARP and a conservative group for older Americans, USA Next, cropped up around the time of the State of the Union speech. The AARP had supported Bush's plan for major changes in Medicare in 2003, but it opposed his Social Security privatization initiative. In January 2005, before the State of the Union Address, the AARP ran advertisements attacking the idea. In response, USA Next launched a campaign against AARP. Charlie Jarvis of USA Next stated: "They [AARP] are the boulder in the middle of the highway to personal savings accounts. We will be the dynamite that removes them."
The tone of the debate between these two interest groups is merely one example among many of the tone of many of the debates, discussions, columns, advertisements, articles, letters, and white papers that Bush's proposal, to touch the "third rail," has sparked among politicians, pundits, thinktankers, and taxpayers.
Immediately after Bush's State of the Union speech, a national poll brought some good news for each side of the controversy. Only 17% of the respondents thought the Social Security system was "in a state of crisis", but 55% thought it had "major problems". The general idea of allowing private investments was favored by 40% and opposed by 55%. Specific proposals that received more support than opposition (in each case by about a two-to-one ratio) were "Limiting benefits for wealthy retirees" and "Requiring higher income workers to pay Social Security taxes on ALL of their wages". The poll was conducted by USA Today, CNN, and the Gallup Organization.
Bush's April press conference, in which for the first time he expressly endorsed benefit reductions, sparked disagreement about where the burden would fall. Bush referred to "people who are better off". Many media summaries accepted the characterization that "wealthy" retirees would be affected, and that benefits for lower-income people would grow. Opponents countered that middle-class retirees would also experience cuts, and that those below the poverty line would receive only what they are entitled to under current law. Democrats also expressed concern that a Social Security system that primarily benefited the poor would have less widespread political support. Finally, the issue of private accounts continued to be a divisive one. Many legislators remained opposed or dubious, while Bush, in his press conference, said he felt strongly about the point.
Despite Bush's emphasis on the issue, many Republicans in Congress were not enthusiastic about his proposal. In late May 2005, House Majority Whip Roy Blunt listed the "priority legislation" to be acted on after Memorial Day; Social Security was not included. In September, some Congressional Republicans pointed to the budgetary problems caused by Hurricane Katrina as a further obstacle to acting on the Bush proposal. Congress did not enact any major changes to Social Security in 2005, or before its pre-election adjournment in 2006.
During the campaigning for the 2006 midterm election, Bush stated that reviving his proposal for privatizing Social Security would be one of his top two priorities for his last two years in office. In 2007, he continued to pursue that goal by nominating Andrew Biggs, a privatization advocate and former researcher for the Cato Institute, to be deputy commissioner of the Social Security Administration. When the Senate did not confirm Biggs, Bush made a recess appointment, enabling Biggs to hold the post without Senate confirmation until December 2008. During his last days in office, Bush said that spurring the debate on Social Security was his most effective achievement during his presidency.
Other concerns about Social Security
Some allege that George W. Bush is opposed to Social Security on ideological grounds, regarding it as a form of governmental redistribution of income from the wealthy, which other groups such as libertarians strongly oppose. Some of the critics of Bush's plan argued that its real purpose was not to save the current Social Security system, but to lay the groundwork for dismantling it. They note that, in 2000, when Bush was asked about a possible transition to a fully privatized system, he replied: "It's going to take a while to transition to a system where personal savings accounts are the predominant part of the investment vehicle. ... This is a step toward a completely different world, and an important step." His comment is consonant with the Cato Institute's reference in 1983 to a "Leninist strategy" for "guerrilla warfare" against both the current Social Security system and the coalition that supports it."
Critics of the system, such as Nobel Laureate economist Milton Friedman, have said that Social Security redistributes wealth from the poor to the wealthy.[117558] Workers must pay 12.4%, including a 6.2% employer contribution, on their wages below the Social Security Wage Base ($102,000 in 2008), but no tax on income in excess of this amount.[117559] Therefore, high earners pay a lower percentage of their total income, resulting in a regressive tax. Others would argue the tax is a flat tax. The benefit paid to each worker is also calculated using the wage base on which the tax was paid. Changing the system to tax all earnings without increasing the benefit wage base would result in the system being a progressive tax.
Furthermore, wealthier individuals generally have higher life expectancies and thus may expect to receive larger benefits for a longer period than poorer taxpayers, often minorities.[117560] A single individual who dies before age 62, who is more likely to be poor, receives no retirement benefits despite years of paying Social Security tax. On the other hand, an individual who lives to age 100, who is more likely to be wealthy, is guaranteed payments that are more than he or she paid into the system.[117561]
A factor working against wealthier individuals and in favor of the poor with little other retirement income is that Social Security benefits become subject to federal income tax based on income. The portion varies with income level, 50% at $32,000 rising to 85% at $44,000 for married couples in 2008. This does not just affect those that continue to work after retirement. Unearned income withdrawn from tax deferred retirement accounts, like IRAs and 401s, counts towards taxation of benefits.
Still other critics focus on the quality of life issues associated with Social Security, claiming that while the system has provided for retiree pensions, their quality of life is much lower than it would be if the system were required to pay a fair rate of return. The party leadership on both sides of the aisle have chosen not to frame the debate in this manner, presumably because of the unpleasantness involved in arguing that current retirees would have a much higher quality of life if Social Security legislation mandated returns that were merely similar to the interest rate the U.S. government pays on its borrowings.
The effects of the gift to the first generation
It has been argued that the first generation of social security participants have, in effect, received a large gift, because they received far more benefits than they paid into the system. Robert J. Shiller noted that "the initial designers of the Social Security System in 1935 had envisioned the building of a large trust fund", but "the 1939 amendments and subsequent changes prevented this from happening".
As such, the gift to the first generation is necessarily borne by subsequent generations. In this pay-as-you-go system, current workers are paying the benefits of the previous generation, instead of investing for their own retirement, and therefore, attempts at privatizing Social Security could result in workers having to pay twice: once to fund the benefits of current retirees, and a second time to fund their own retirement.
Criticism of Social Security as a pyramid or Ponzi scheme
Libertarians commonly criticize Social Security's pay-as-you-go funding as being closer to an illegal Ponzi scheme — where investors are paid off out of the funds collected from more investors, instead of out of profits from business activity — than it is to a trust fund. Michael Kinsley has also described Social Security in this way. William G. Shipman of the Cato Institute argues:
In common usage a trust fund is an estate of money and securities held in trust for its beneficiaries.
The Social Security Trust Fund is quite different.
It is an accounting of the difference between tax and benefit flows.
When taxes exceed benefits, the federal government lends itself the excess in return for an interest-paying bond, an IOU that it issues to itself.
The government then spends its new funds on unrelated projects such as bridge repairs, defense, or food stamps.
The funds are not invested for the benefit of present or future retirees.
This criticism is not new. In his 1936 presidential campaign, Republican Alf Landon called the trust fund "a cruel hoax". The Republican platform that year stated, "The so-called reserve fund estimated at forty-seven billion dollars for old age insurance is no reserve at all, because the fund will contain nothing but the Government's promise to pay, while the taxes collected in the guise of premiums will be wasted by the Government in reckless and extravagant political schemes." [117562] Defenders of pay-as-you-go respond that the system is a Ponzi scheme only if the United States intends to repudiate its debts. On the occasions when the Social Security Administration has needed to redeem some of those securities, they have always been honored. Although Social Security benefits to future retirees do not represent debt in the legal sense (Fleming v. Nestor, 1960), the treasuries held by the trust fund do.
The Social Security Administration responds to the criticism as follows:
Generational accounting
Pensions crisis
2008 Social Security - Trustees Report Summary Press Release
Trust Fund Report - Table VI.C6 Intermediate Assumptions
2009 Social Security OASDI Trustees Report - Overview
OASDI Trust Fund Report
Trustees Report Long Range Estimates - Section 5a
Bernanke - The Coming Demographic Transition
Social Scty Trust Fund Report - 2009 Page 3
Concord Slides
Bernanke Speech Oct 4, 2006
Social Security Trust Fund
Biddle, Scott and Johnson, Jean "Where Does the Money Go?" New York. Collins;2008
OMB Analytical Perspectives 2009 Budget Page 370 Table 23-1
Washington Post-Recession Puts Major Strain on Social Security Trust Fund
CBO Schedule via Hot Air
Bloomberg - Social Security Applications Almost Double Because of Recession - Oct 2 2009
Bernanke-The Coming Demographic Transition
NYT-Third Rail Quote Source
George Will - Opportunity, Not a Crisis
Twelve Reasons Why Privatizing Social Security is a Bad Idea
Krugman-Social Security Scares
Twelve Reasons Privatizing Social Security is a Bad Idea
President Bush - 2005 State of the Union Speech
AARP Public Policy Institute - Reform Options for Social Security
Thomas N. Bethell, What's the Big Idea?, The AARP Bulletin Online, April 2005.
Barack Obama | Change We Can Believe In | Seniors
Barack Obama on Social Security
Social Security COLA adjustment 2009
Twelve Reasons Privatizing Social Security is a Bad Idea-Reason 3
GDP Statistics
(80k external PDF file)
Milton Friedman & Rose Friedman, "Free to Choose," (New York:Harcout, Brace, Jovanovich, 1980), pg. 102-107.
Very basic
'Reforming European Pension Systems' (Arun Muralidhar and Serge Allegreza (Eds.)), Amsterdam, NL and West Lafayette, Indiana, USA: Dutch University Press, Rozenberg Publishers and Purdue University Press (essays in memory of Franco Modigliani)
Modigliani, Franco. Rethinking pension reform / Franco Modigliani, Arun Muralidhar. Cambridge, UK ; New York : Cambridge University Press, 2004.
Muralidhar, Arun S. Innovations in pension fund management / Arun S. Muralidhar. Stanford, Calif.; Great Britain: Stanford Economics + Finance, c2001.
Arno Tausch, The Three Pillars of Wisdom? A Reader on Globalization, World Bank Pension Models and Welfare Society. Nova Science Hauppauge, New York, 2003
List of Social Security legislation
Social Security for both information about the program, as it currently exists, and historical information about the creation of the program in the mid 1930's and the controversies at that time.
Be not afraid: personal accounts are no radical idea — The American Enterprise — March 2005
CommUnity of Minds: Working Together — The $44 Trillion Abyss - 2003 Fortune Magazine
"False Attacks Over 'Windfalls' to Wall Street" — from FactCheck* José Piñera, "Retiring in Chile", The New York Times, December 1, 2004 [117563]
José Piñera, "Empowering the Workers: The Privatization of Social Security in Chile", Cato Journal, Vol. 15 No. 2-3 [117564]
Getting a grip on Social Security: The flaw in the system
Social Security Suicide — AlterNet
Arno Tausch (2005) 'World Bank Pension reforms and development patterns in the world system and in the "Wider Europe". A 109 country investigation based on 33 indicators of economic growth, and human, social and ecological well-being, and a European regional case study'. A slightly re-worked version of a paper, originally presented to the Conference on "Reforming European pension systems. In memory of Professor Franco Modigliani. 24 and 25 September 2004", Castle of Schengen, Luxembourg Institute for European and International Studies
"The Fake Crisis" — Rolling Stone
US Government Accountability Office, Social Security Reform: Answers to Key Questions
"What Does Price Indexing Mean for Social Security Benefits?" — from Center for Retirement Research, January, 2005 (explanation of wage indexing versus price indexing)
Social Security Q & A by economist Doug Orr
Washington Post - Allan Sloan - The Next Great Bailout: Social Security -July 2009
President George W. Bush — State of the Union Address — February 2, 2005
"Bush's State of the Union: Social Security 'Bankruptcy?'" — FactCheck.org commentary on the speech
FRB: Testimony, Greenspan — Economic outlook and current fiscal issues — February 25, 2004

redpajama_set_name: RedPajamaCommonCrawl


Serving strategy is one of the most impactful ways that a coach can influence winning or losing with a team in a match. Can you as a coach maximize your team's point scoring percentage by making the best decisions to get the most value from each server?
2013 AVCA National Coach of the Year, discusses serving strategy.
Coach Collier believes that one of the biggest was that a coach can impact his/her team winning matches is with serving strategy and with serving emphasis with players. A lot of different things happen in a match, but serving scores points. They are the direct reason you score points. he believes that as coaches we should take control and manage serving as best as possible to help our teams win more matches.
Here are things to consider when developing your stategy.
Signaling zones or player choice – To develop a serving strategy coaches must know their players strength and weaknesses. Which players serve better to which zones? Which type of serve is most effective for each player? To know these things coaches need to track points per rotation served. Coaches need to collect data so they can make informed decisions on what type of serve they want the players to use and to what zone.
Serve the weakest player. – sometimes players serve more conservative when asked to serve the weaker player. The result is that despite serving a weaker player, the point production to does not go up.
Adjusting serving strategy match to match – are you going to change your strategy or adjust match to match. There are advantages to both, you must decide.
This clip is from Coach Collier's DVD entitled: Effective Game Management: Win More Points, Win More Games! For more information about that DVD click the link above.
The YouTube video below has audio, so please make sure that your sound is turned on and that you have access to the site. Note that some schools block access to YouTube. Click the arrow to play the video.


In fact it's going to be held in London and will be a quickie.
The AGM was always going to be held in the UK (it's part of the ACT constitution) but the trade-sponsored conference was first going to be held in Palma but this ambitious plan was later scaled back to Belgium.
"We had such little interest in the overseas conference that it was an easy decision to shelve it. All our efforts will now go into the many positive things the ACT does on a day to day basis. We always do what the members want us to do, and an overseas conference isn't something the members wanted."


From time to time, new online callbooks and QSL databases become available. In addition, the location or search parameters for existing online resources sometimes change. You can create or modify your own search files to expand Pathfinder's search capabilities -- see Modifying searches for more information. In addition, you can download search files -- either en masse or individually -- from Pathfinder's Search library as they become available. The following two sections describe these search file download procedures.
If a downloaded search file describes a country-specific callbook, no further action is required; Pathfinder checks its Searches subfolder whenever you enter a callsign, and thus will reference the new search file when needed.
If a downloaded search file describes a callbook or QSL database that you expect to search frequently, you can assign the search to one of Pathfinder's 12 search buttons by following these directions.
To update a search already assigned to one of Pathfinder's search buttons, assign the newly-downloaded search file to the existing button by following these directions.
The following process updates all search files. If you've made modifications to the search files in your Searches subfolder, be sure to make copies before proceeding.
2 When prompted, direct your browser to save this executable file to a temporary location on your hard drive; subfolder C:\Temp is often used for this purpose. Note the name of the executable file being downloaded, as well as the destination subfolder.
3 When the download has finished, initiate self-extraction by double-clicking on the executable file in a Windows Explorer window. The WinZip Self-Extractor dialog box will appear.
If you installed Pathfinder in C:\Program Files\DXLab Suite\Pathfinder, then this default destination is correct -- just click the Unzip button. Your Searches subfolder will now contain a full set of up-to-date search files.
If you installed Pathfinder elsewhere, modify the Unzip to folder field to designate Pathfinder's Searches subfolder and then click the Unzip button.
1 Display Pathfinder's Search Library by clicking here.
2 Find the entry corresponding to the search file you wish to download, and click on it. Your browser will display the search file's contents -- six lines of descriptive information.
3 Use your browser's SaveAs command (in it's File menu) to store the file into Pathfinder's Searches subfolder. If you are updating an existing search file, your browser will ask permission to replace it with the new version; click the Yes button.
If the downloaded search file describes a country-specific callbook, no further action is required; Pathfinder checks its Searches subfolder whenever you enter a callsign, and thus will reference the new search file when needed.
If the downloaded search file describes a callbook or QSL database that you expect to search frequently, you can assign the search to one of Pathfinder's 12 search buttons by following these directions.


text:
Ford's market cap tops $100 billion for first time ever
5 days ago 4 views0
Ford Motor Co. CEO Jim Farley walks to speak at a news conference at the Rouge Complex in Dearborn, Michigan, September 17, 2020.
Rebecca Cook | Reuters
DETROIT – Ford Motor's market value topped $100 billion for the first time ever as the automaker's stock hit a new 52-week high Thursday.
The company's shares jumped by as much as 5.7% to $25.87, hitting another 20-plus-year high. Its market value was about $102 billion as of 1:50 p.m. Thursday.
The gains have been fueled by Ford's plans to increase production of electric vehicles, including the Mustang Mach-E crossover and an upcoming electric version of its bestselling F-150 pickup that's due out this spring. The efforts are part of a Ford+ turnaround plan led by CEO Jim Farley, who took over the helm in October 2020.
Ford's now worth more than crosstown rival General Motors, at about $90 billion, as well as electric vehicle start-up Rivian Automotive, at $75 billion, which has failed to sustain gains following a blockbuster IPO in November. Ford continues to significantly trail Tesla, which has a market cap of more than $1 trillion.
Biden deploys military medical teams to hospitals in six states as omicron disrupts essential services
Woman arrested near Capitol had loaded shotgun, wanted to talk about Jan. 6, cops say
Microsoft's $68.7 billion deal for Activision shows big tech's dominance over legacy media
Microsoft takes big $68.7 billion swing on video game company Activision Blizzard while legacy media ...
Covid-19 will never be eradicated, but society has a chance to end the public health ...
The Kremlin has previously denied that it was preparing for an invasion of Ukraine.


text:
Martin Kirkup is a British-born music industry executive. He is a founding partner of the Los Angeles-based Direct Management Group. Over the course of his career,  Kirkup has worked with artists including Katy Perry, Adam Lambert, k.d. lang, Counting Crows, The B-52s, Echo and the Bunnymen, and Orchestral Manoeuvres in the Dark.

Early life and education
Kirkup was born and grew up in Tynemouth, Northumberland. He attended the University of Leicester, and came to the United States in 1973 as a visiting professor at the University of Rhode Island. He later moved to New York, where he began his career in the music industry in the publicity department at Elektra Records.

Career
Kirkup was hired by A&M Records in 1975 as director of creative services.  He moved to Los Angeles in 1978, and was named vice president of artist development, overseeing campaigns for the artists on A&M's roster, which at the time included Peter Frampton, Nils Lofgren, Supertramp, Squeeze, The Tubes, Bryan Adams, Joe Jackson, The Police and Joan Armatrading.

In 1984, he founded Direct Management with Steve Jensen, who was previously a booking agent. Kirkup and Jensen's first clients were Boy Meets Girl and Nell Carter. Their first significant success was with Orchestral Manoeuvres in the Dark; they placed "If You Leave" on the Pretty in Pink soundtrack, and the song became a Top 5 hit on the Billboard Top 100. While the band previously had hits in Europe, the album which followed the Pretty in Pink soundtrack,  The Pacific Age, was their first American gold album.

Bryan Ferry was signed in 1988 Echo and the Bunnymen were signed in 1986, and in 1989 Kirkup and Jensen began working with The B-52's, reformed after the death of guitarist Ricky Wilson.
 Their first release as a Direct client, Cosmic Thing included the hit singles "Roam" and "Love Shack" and more than 5 million copies of the album were sold. Kirkup and Jenson were credited for "steering  (the B-52s) into a major comeback."

In 1992 Kirkup and Jensen signed Counting Crows; their debut, August and Everything After, sold in excess of 10 million albums.  Direct worked with the band until 2001. They have managed Lang since signing her in 2000.

Bradford Cobb joined Direct in 1997, and in 2004, he met Katy Perry and producer Glen Ballard. She was signed by Direct shortly thereafter. The first single from the debut Katy Perry album, One of the Boys, I Kissed a Girl", became her first Billboard Hot 100.  Her next album, Teenage Dream  became the first album by a female artist to produce five number-one Billboard Hot 100 singles  As of 2018, Perry had sold more than 100 million records.

Direct also manages AU/RA.  The company managed Adam Lambert from 2011 until 2017.

References

External links
 Direct Management

1948 births
Alumni of the University of Leicester
American music industry executives
American music managers
Businesspeople from Los Angeles
British music industry executives
English music managers
Living people
People from Tynemouth
Businesspeople from Tyne and Wear

redpajama_set_name: RedPajamaWikipedia


text:
package runtime

import (
	"internal/cpu"
	"internal/goarch"
	"unsafe"
)

// For gccgo, use go:linkname to export compiler-called functions.
//
//go:linkname memhash0
//go:linkname memhash8
//go:linkname memhash16
//go:linkname memhash32
//go:linkname memhash64
//go:linkname memhash128
//go:linkname strhash
//go:linkname f32hash
//go:linkname f64hash
//go:linkname c64hash
//go:linkname c128hash
//go:linkname interhash
//go:linkname nilinterhash
//go:linkname memequal0
//go:linkname memequal8
//go:linkname memequal16
//go:linkname memequal32
//go:linkname memequal64
//go:linkname memequal128
//go:linkname strequal
//go:linkname f32equal
//go:linkname f64equal
//go:linkname c64equal
//go:linkname c128equal
//go:linkname interequal
//go:linkname nilinterequal
//go:linkname efaceeq
//go:linkname ifaceeq
//go:linkname ifacevaleq
//go:linkname ifaceefaceeq
//go:linkname efacevaleq
//go:linkname cmpstring
//
// Temporary to be called from C code.
//go:linkname alginit

const (
	c0 = uintptr((8-goarch.PtrSize)/4*2860486313 + (goarch.PtrSize-4)/4*33054211828000289)
	c1 = uintptr((8-goarch.PtrSize)/4*3267000013 + (goarch.PtrSize-4)/4*23344194077549503)
)

func memhash0(p unsafe.Pointer, h uintptr) uintptr {
	return h
}

func memhash8(p unsafe.Pointer, h uintptr) uintptr {
	return memhash(p, h, 1)
}

func memhash16(p unsafe.Pointer, h uintptr) uintptr {
	return memhash(p, h, 2)
}

func memhash128(p unsafe.Pointer, h uintptr) uintptr {
	return memhash(p, h, 16)
}

// runtime variable to check if the processor we're running on
// actually supports the instructions used by the AES-based
// hash implementation.
var useAeshash bool

// in C code
func aeshashbody(p unsafe.Pointer, h, s uintptr, sched []byte) uintptr

func aeshash(p unsafe.Pointer, h, s uintptr) uintptr {
	return aeshashbody(p, h, s, aeskeysched[:])
}

func aeshashstr(p unsafe.Pointer, h uintptr) uintptr {
	ps := (*stringStruct)(p)
	return aeshashbody(unsafe.Pointer(ps.str), h, uintptr(ps.len), aeskeysched[:])
}

func strhash(a unsafe.Pointer, h uintptr) uintptr {
	x := (*stringStruct)(a)
	return memhash(x.str, h, uintptr(x.len))
}

// NOTE: Because NaN != NaN, a map can contain any
// number of (mostly useless) entries keyed with NaNs.
// To avoid long hash chains, we assign a random number
// as the hash value for a NaN.

func f32hash(p unsafe.Pointer, h uintptr) uintptr {
	f := *(*float32)(p)
	switch {
	case f == 0:
		return c1 * (c0 ^ h) // +0, -0
	case f != f:
		return c1 * (c0 ^ h ^ uintptr(fastrand())) // any kind of NaN
	default:
		return memhash(p, h, 4)
	}
}

func f64hash(p unsafe.Pointer, h uintptr) uintptr {
	f := *(*float64)(p)
	switch {
	case f == 0:
		return c1 * (c0 ^ h) // +0, -0
	case f != f:
		return c1 * (c0 ^ h ^ uintptr(fastrand())) // any kind of NaN
	default:
		return memhash(p, h, 8)
	}
}

func c64hash(p unsafe.Pointer, h uintptr) uintptr {
	x := (*[2]float32)(p)
	return f32hash(unsafe.Pointer(&x[1]), f32hash(unsafe.Pointer(&x[0]), h))
}

func c128hash(p unsafe.Pointer, h uintptr) uintptr {
	x := (*[2]float64)(p)
	return f64hash(unsafe.Pointer(&x[1]), f64hash(unsafe.Pointer(&x[0]), h))
}

func interhash(p unsafe.Pointer, h uintptr) uintptr {
	a := (*iface)(p)
	tab := a.tab
	if tab == nil {
		return h
	}
	t := *(**_type)(tab)
	if t.equal == nil {
		// Check hashability here. We could do this check inside
		// typehash, but we want to report the topmost type in
		// the error text (e.g. in a struct with a field of slice type
		// we want to report the struct, not the slice).
		panic(errorString("hash of unhashable type " + t.string()))
	}
	if isDirectIface(t) {
		return c1 * typehash(t, unsafe.Pointer(&a.data), h^c0)
	} else {
		return c1 * typehash(t, a.data, h^c0)
	}
}

func nilinterhash(p unsafe.Pointer, h uintptr) uintptr {
	a := (*eface)(p)
	t := a._type
	if t == nil {
		return h
	}
	if t.equal == nil {
		// See comment in interhash above.
		panic(errorString("hash of unhashable type " + t.string()))
	}
	if isDirectIface(t) {
		return c1 * typehash(t, unsafe.Pointer(&a.data), h^c0)
	} else {
		return c1 * typehash(t, a.data, h^c0)
	}
}

// typehash computes the hash of the object of type t at address p.
// h is the seed.
// This function is seldom used. Most maps use for hashing either
// fixed functions (e.g. f32hash) or compiler-generated functions
// (e.g. for a type like struct { x, y string }). This implementation
// is slower but more general and is used for hashing interface types
// (called from interhash or nilinterhash, above) or for hashing in
// maps generated by reflect.MapOf (reflect_typehash, below).
// Note: this function must match the compiler generated
// functions exactly. See issue 37716.
func typehash(t *_type, p unsafe.Pointer, h uintptr) uintptr {
	if t.tflag&tflagRegularMemory != 0 {
		// Handle ptr sizes specially, see issue 37086.
		switch t.size {
		case 4:
			return memhash32(p, h)
		case 8:
			return memhash64(p, h)
		default:
			return memhash(p, h, t.size)
		}
	}
	switch t.kind & kindMask {
	case kindFloat32:
		return f32hash(p, h)
	case kindFloat64:
		return f64hash(p, h)
	case kindComplex64:
		return c64hash(p, h)
	case kindComplex128:
		return c128hash(p, h)
	case kindString:
		return strhash(p, h)
	case kindInterface:
		i := (*interfacetype)(unsafe.Pointer(t))
		if len(i.methods) == 0 {
			return nilinterhash(p, h)
		}
		return interhash(p, h)
	case kindArray:
		a := (*arraytype)(unsafe.Pointer(t))
		for i := uintptr(0); i < a.len; i++ {
			h = typehash(a.elem, add(p, i*a.elem.size), h)
		}
		return h
	case kindStruct:
		s := (*structtype)(unsafe.Pointer(t))
		for _, f := range s.fields {
			if f.name != nil && *f.name == "_" {
				continue
			}
			h = typehash(f.typ, add(p, f.offset()), h)
		}
		return h
	default:
		// Should never happen, as typehash should only be called
		// with comparable types.
		panic(errorString("hash of unhashable type " + t.string()))
	}
}

//go:linkname reflect_typehash reflect.typehash
func reflect_typehash(t *_type, p unsafe.Pointer, h uintptr) uintptr {
	return typehash(t, p, h)
}

func memequal0(p, q unsafe.Pointer) bool {
	return true
}
func memequal8(p, q unsafe.Pointer) bool {
	return *(*int8)(p) == *(*int8)(q)
}
func memequal16(p, q unsafe.Pointer) bool {
	return *(*int16)(p) == *(*int16)(q)
}
func memequal32(p, q unsafe.Pointer) bool {
	return *(*int32)(p) == *(*int32)(q)
}
func memequal64(p, q unsafe.Pointer) bool {
	return *(*int64)(p) == *(*int64)(q)
}
func memequal128(p, q unsafe.Pointer) bool {
	return *(*[2]int64)(p) == *(*[2]int64)(q)
}
func f32equal(p, q unsafe.Pointer) bool {
	return *(*float32)(p) == *(*float32)(q)
}
func f64equal(p, q unsafe.Pointer) bool {
	return *(*float64)(p) == *(*float64)(q)
}
func c64equal(p, q unsafe.Pointer) bool {
	return *(*complex64)(p) == *(*complex64)(q)
}
func c128equal(p, q unsafe.Pointer) bool {
	return *(*complex128)(p) == *(*complex128)(q)
}
func strequal(p, q unsafe.Pointer) bool {
	return *(*string)(p) == *(*string)(q)
}
func interequal(p, q unsafe.Pointer) bool {
	return ifaceeq(*(*iface)(p), *(*iface)(q))
}
func nilinterequal(p, q unsafe.Pointer) bool {
	return efaceeq(*(*eface)(p), *(*eface)(q))
}
func efaceeq(x, y eface) bool {
	t := x._type
	if !eqtype(t, y._type) {
		return false
	}
	if t == nil {
		return true
	}
	eq := t.equal
	if eq == nil {
		panic(errorString("comparing uncomparable type " + t.string()))
	}
	if isDirectIface(t) {
		return x.data == y.data
	}
	return eq(x.data, y.data)
}

func ifaceeq(x, y iface) bool {
	xtab := x.tab
	if xtab == nil && y.tab == nil {
		return true
	}
	if xtab == nil || y.tab == nil {
		return false
	}
	t := *(**_type)(xtab)
	if !eqtype(t, *(**_type)(y.tab)) {
		return false
	}
	eq := t.equal
	if eq == nil {
		panic(errorString("comparing uncomparable type " + t.string()))
	}
	if isDirectIface(t) {
		// Direct interface types are ptr, chan, map, func, and single-element structs/arrays thereof.
		// Maps and funcs are not comparable, so they can't reach here.
		// Ptrs, chans, and single-element items can be compared directly using ==.
		return x.data == y.data
	}
	return eq(x.data, y.data)
}

func ifacevaleq(x iface, t *_type, p unsafe.Pointer) bool {
	if x.tab == nil {
		return false
	}
	xt := *(**_type)(x.tab)
	if !eqtype(xt, t) {
		return false
	}
	eq := t.equal
	if eq == nil {
		panic(errorString("comparing uncomparable type " + t.string()))
	}
	if isDirectIface(t) {
		return x.data == p
	}
	return eq(x.data, p)
}

func ifaceefaceeq(x iface, y eface) bool {
	if x.tab == nil && y._type == nil {
		return true
	}
	if x.tab == nil || y._type == nil {
		return false
	}
	xt := *(**_type)(x.tab)
	if !eqtype(xt, y._type) {
		return false
	}
	eq := xt.equal
	if eq == nil {
		panic(errorString("comparing uncomparable type " + xt.string()))
	}
	if isDirectIface(xt) {
		return x.data == y.data
	}
	return eq(x.data, y.data)
}

func efacevaleq(x eface, t *_type, p unsafe.Pointer) bool {
	if x._type == nil {
		return false
	}
	if !eqtype(x._type, t) {
		return false
	}
	eq := t.equal
	if eq == nil {
		panic(errorString("comparing uncomparable type " + t.string()))
	}
	if isDirectIface(t) {
		// See comment in efaceeq.
		return x.data == p
	}
	return eq(x.data, p)
}

func cmpstring(x, y string) int {
	a := stringStructOf(&x)
	b := stringStructOf(&y)
	l := a.len
	if l > b.len {
		l = b.len
	}
	i := memcmp(unsafe.Pointer(a.str), unsafe.Pointer(b.str), uintptr(l))
	if i != 0 {
		return int(i)
	}
	if a.len < b.len {
		return -1
	} else if a.len > b.len {
		return 1
	}
	return 0
}

// For the unsafe.Pointer type descriptor in libgo/runtime/go-unsafe-pointer.c.

func pointerhash(p unsafe.Pointer, h uintptr) uintptr {
	return memhash(p, h, unsafe.Sizeof(unsafe.Pointer))
}

func pointerequal(p, q unsafe.Pointer) bool {
	return *(*unsafe.Pointer)(p) == *(*unsafe.Pointer)(q)
}

// Force the creation of function descriptors for equality and hash
// functions.  These will be referenced directly by the compiler.
var _ = memhash
var _ = memhash0
var _ = memhash8
var _ = memhash16
var _ = memhash32
var _ = memhash64
var _ = memhash128
var _ = strhash
var _ = f32hash
var _ = f64hash
var _ = c64hash
var _ = c128hash
var _ = interhash
var _ = nilinterhash
var _ = memequal0
var _ = memequal8
var _ = memequal16
var _ = memequal32
var _ = memequal64
var _ = memequal128
var _ = f32equal
var _ = f64equal
var _ = c64equal
var _ = c128equal
var _ = strequal
var _ = interequal
var _ = nilinterequal
var _ = pointerhash
var _ = pointerequal

// Testing adapters for hash quality tests (see hash_test.go)
func stringHash(s string, seed uintptr) uintptr {
	return strhash(noescape(unsafe.Pointer(&s)), seed)
}

func bytesHash(b []byte, seed uintptr) uintptr {
	s := (*slice)(unsafe.Pointer(&b))
	return memhash(s.array, seed, uintptr(s.len))
}

func int32Hash(i uint32, seed uintptr) uintptr {
	return memhash32(noescape(unsafe.Pointer(&i)), seed)
}

func int64Hash(i uint64, seed uintptr) uintptr {
	return memhash64(noescape(unsafe.Pointer(&i)), seed)
}

func efaceHash(i any, seed uintptr) uintptr {
	return nilinterhash(noescape(unsafe.Pointer(&i)), seed)
}

func ifaceHash(i interface {
	F()
}, seed uintptr) uintptr {
	return interhash(noescape(unsafe.Pointer(&i)), seed)
}

const hashRandomBytes = goarch.PtrSize / 4 * 64

// used in asm_{386,amd64,arm64}.s to seed the hash function
var aeskeysched [hashRandomBytes]byte

// used in hash{32,64}.go to seed the hash function
var hashkey [4]uintptr

func alginit() {
	// Install AES hash algorithms if the instructions needed are present.
	if (GOARCH == "386" || GOARCH == "amd64") &&
		support_aes &&
		cpu.X86.HasAES && // AESENC
		cpu.X86.HasSSSE3 && // PSHUFB
		cpu.X86.HasSSE41 { // PINSR{D,Q}
		initAlgAES()
		return
	}
	if GOARCH == "arm64" && cpu.ARM64.HasAES {
		initAlgAES()
		return
	}
	getRandomData((*[len(hashkey) * goarch.PtrSize]byte)(unsafe.Pointer(&hashkey))[:])
	hashkey[0] |= 1 // make sure these numbers are odd
	hashkey[1] |= 1
	hashkey[2] |= 1
	hashkey[3] |= 1
}

func initAlgAES() {
	useAeshash = true
	// Initialize with random data so hash collisions will be hard to engineer.
	getRandomData(aeskeysched[:])
}

// Note: These routines perform the read with a native endianness.
func readUnaligned32(p unsafe.Pointer) uint32 {
	q := (*[4]byte)(p)
	if goarch.BigEndian {
		return uint32(q[3]) | uint32(q[2])<<8 | uint32(q[1])<<16 | uint32(q[0])<<24
	}
	return uint32(q[0]) | uint32(q[1])<<8 | uint32(q[2])<<16 | uint32(q[3])<<24
}

func readUnaligned64(p unsafe.Pointer) uint64 {
	q := (*[8]byte)(p)
	if goarch.BigEndian {
		return uint64(q[7]) | uint64(q[6])<<8 | uint64(q[5])<<16 | uint64(q[4])<<24 |
			uint64(q[3])<<32 | uint64(q[2])<<40 | uint64(q[1])<<48 | uint64(q[0])<<56
	}
	return uint64(q[0]) | uint64(q[1])<<8 | uint64(q[2])<<16 | uint64(q[3])<<24 | uint64(q[4])<<32 | uint64(q[5])<<40 | uint64(q[6])<<48 | uint64(q[7])<<56
}

redpajama_set_name: RedPajamaGithub


text:
'use strict';

/**
 * Get monitoring data response.
 *
 */
class IntegrationRuntimeMonitoringData {
  /**
   * Create a IntegrationRuntimeMonitoringData.
   * @member {string} [name] Integration runtime name.
   * @member {array} [nodes] Integration runtime node monitoring data.
   */
  constructor() {
  }

  /**
   * Defines the metadata of IntegrationRuntimeMonitoringData
   *
   * @returns {object} metadata of IntegrationRuntimeMonitoringData
   *
   */
  mapper() {
    return {
      required: false,
      serializedName: 'IntegrationRuntimeMonitoringData',
      type: {
        name: 'Composite',
        className: 'IntegrationRuntimeMonitoringData',
        modelProperties: {
          name: {
            required: false,
            serializedName: 'name',
            type: {
              name: 'String'
            }
          },
          nodes: {
            required: false,
            serializedName: 'nodes',
            type: {
              name: 'Sequence',
              element: {
                  required: false,
                  serializedName: 'IntegrationRuntimeNodeMonitoringDataElementType',
                  type: {
                    name: 'Composite',
                    additionalProperties: {
                      type: {
                        name: 'Dictionary',
                        value: {
                            required: false,
                            serializedName: 'ObjectElementType',
                            type: {
                              name: 'Object'
                            }
                        }
                      }
                    },
                    className: 'IntegrationRuntimeNodeMonitoringData'
                  }
              }
            }
          }
        }
      }
    };
  }
}

module.exports = IntegrationRuntimeMonitoringData;


text:
Q: golang http.Get request works usual way, but do not work inside go routines I have some server working with GET requests. Need to create highload for this server
Simple test client:
func main(){
    http.Get("http://localhost:8080/8")
}

It works, server show that he received request
Another test:
func main(){
    for i:=0; i<5; i++{
        go func() {
            http.Get("http://localhost:8080/8")
        }()
    }
}

or even
func main(){
    for i:=0; i<5; i++{
        go http.Get("http://localhost:8080/8")
    }
}

It didn't work, server did not receiving any requests
So, what is a problem?

A: I think it's because your application terminated right after your loop end.
to handle this you can use WaitGroup. and change your code to be like this:
func main(){

    wg := sync.Waitgroup{}

    for i:=0; i<5; i++{
        wg.Add(1)
        go func() {
            defer wg.Done()
            http.Get("http://localhost:8080/8")
        }()
    }

    wg.Wait()
}

redpajama_set_name: RedPajamaStackExchange


Running businesses, we are all focused on what critical levers we can push, which will result in growth. Not just slow-and-steady growth, but blow-your-socks-off growth. The kind of growth that injects cash and momentum into a business -- and which is sustainable.It can't just be growth for a year or two, which leads to breakdowns later. We are all interested in knowing what steps we can take to drive our businesses forward aggressively.
Later this year (in November), Jackson Leadership consultant and Dartmouth B-School Prof Syd Finkelstein (with 2 co-authors) comes out with his next book on this very topic. For more info, check out this link.
At Jackson, we already have an opinion on what the critical levers are. However, unlike some consultants, who simply devise a theory, sell it to clients, and later (if ever) test it to see if it is actually linked to success, we are testing our theory before selling the results.
If you would like to take part in our research and complete a 12-minute Web survey on your own organization, please let me know (click here). We'll be sure to email you a complete report later of our findings (and non-findings).
Thanks for contributing to our knowledge of organizational science.
It's rarely discussed, at least not as much as the habits of succ essful CEOs, but the truth is that it takes some special personal qualities to be spectacularly unsuccessful.
In this Ivey Business Journal article from 2 years ago, Syd Finkelstein discusses how leaders can be not only instruments of success, but sometimes also architects of failure.
It's the most popular downloaded white paper from the Jackson Leadership website.
Welcome to the 'Breakout Performance' weblog launch. This is intended to be a forum to allow for those with an interest in how leadership, strategy, and process drive exceptional organizational performance to share thoughts and ideas.
I have studied and consulted about this area for over a decade. For the academics out there, I studied at the Columbia Business School's Department of Management under Don Hambrick. My doctoral dissertation studied the link between pre-IPO firms' officers' and directors' backgrounds and IPO and post-IPO performance.
My consulting firm, Jackson Leadership Systems, Inc., has worked with with organizations on helping their leadership, strategy, and process drive 'breakthrough performance' since 1989. Recently, we collaborated with Sydney Finkelstien, Dartmouth Tuck School of Business Professor of Management, on 2 new practice areas which address this topic: Driving Breakout Performance and SMART Early-Warning System.
I look forward to chatting with you over the coming months and sharing more info.


LIONEL MESSI has paid an emotional tribute to the thousands of people affected by the devastating earthquake that rocked Mexico.
The 7.1 magnitude earthquake ripped through Mexico City and surrounding states, with official figures stating that 333 people have been confirmed dead.
The Barcelona and Argentina striker posted on Facebook expressing his sadness at how the natural disaster has wrecked so many people's lives.
Messi wrote: "Saddened by the events that have taken place over the past few weeks, in which many people have suffered the consequences of natural disasters in Mexico, the United States, Puerto Rico, as well as Southern Asia, Sierra Leone and in other places.
"My thoughts and support go out to the families of the victims and all of those who have been affected."
Messi is not the first professional footballer to show their support for the relief effort in the central American country.
SunSport previously reported how West Ham striker Javier Hernandez set up an initiative called "#YoXMexico" along with countryman Miguel Layun, who plays for Porto.
They are trying to raise funds that will help deliver food and supplies to those most affected by the disaster.
Hernandez said: "Being so far from Mexico and seeing the suffering of our compatriots in the distance has been very painful.
"So, after discussing it, we decided to take the initiative for Mexico and give our people a helping hand.
"We know that many see us as a source of inspiration, but in this case, what has inspired us is to see millions of Mexicans take to the streets and to lend a hand without asking for anything in return.
"We hope, with this initiative, to help those who need it and motivate more people to do it with us.
"Miguel and I are very grateful to have the backing of everyone at West Ham United and all of its supporters at this difficult time for our country.
"It is a fantastic gesture and we hope it can help us raise funds that will make a difference in Mexico."
Cristiano Ronaldo and Sergio Aguero have previously also sent out messages of support for Mexico on social media.