Most tax experts considered the removal a budget gimmick so that the 2017 December republican majority could quickly pass a new budget using the budget reconciliation process, which can't be used to increase the deficit after a 10-year period so they had to add a time limit to a bunch of benefits "on paper" to use the reconciliation process. There appeared to be broad support for fixing it later, but the bipartisan spending bill expected to include it fell apart because they couldn't get agreement on other parts of it.
To the best I can tell this isn't tech companies complaining about paying fair tax; it's a congressional oversight that is quadrupling the taxes of small business out of nowhere which nobody in power has bothered to fix.
Given how difficult it is to predict policy outcomes this is probably a good idea. Even if a collection of policies are good on the individual level there is no way to figure out if the interaction will be net positive, nor if the cost of remedy reverses the calculus.
2. Filibusters are not in the Constitution, weren't possible for decades after it was signed, weren't used for half a century after it was signed, and didn't become the "sixty votes required for anything" tool they are today until 10-15 years ago. The founders had nothing to do with it.
https://en.wikipedia.org/wiki/Filibuster_in_the_United_State...
IMO it all comes down to the insight that the opposition party has nothing to gain from cooperating. If something good gets passed, the majority party gets the credit. If nothing gets passed, the majority party gets the blame, regardless details how that outcome was achieved and what role the minority party played. So blocking everything is the best strategy. IMO, it's disgusting to have politicians put party over country, but here we are.
The ones who represent me are highly skilled, very experienced, and have the seniority to ensure my hometown gets it’s fair share,
The ones who represent you are lazy, entitled scammers who should be prevented from fleecing my hometown by the imposition of term limits.
"The ones who represent me give me feelings of schadenfreude over how they deal with the other party and people"
"The ones who represent you give me feelings of angst over how my party is treated"
Now legislators are accountable to corporate donors, not their constituents. It's easy to track which legislators provide a good ROI. There's more to it than that, but those are the major causal events that lead to the change in legislator incentives.
A chart of filibuster usage over the past ~century speaks for itself: https://bit.ly/3mL6IOU
And that's not even fully up to date: the 2019-20 session ended with 298 cloture votes and the 2021-22 session with 289, per https://www.senate.gov/legislative/cloture/clotureCounts.htm .
> the first filibuster was 11 years after the Constitution was ratified
Sure, whatever - your citation is "wikipedia.org/wiki/Filibuster_in_the_United States_Senate" and mine is "wikipedia.org/wiki/Filibuster#Senate". The exact details don't matter: the relevant points are that it's not a mechanism created by the Constitution, was not common in the lifetime of the Constitution's drafters, and has massively different effects on the governance of the country now than it did in the 20th century, much less the 19th or 18th.
It's really a bipartisan agreement to defer to Senate Republicans on everything controversial, and to let them take both the blame and credit for it. Democrats are happy with that because when their votes don't count, they can pretend to support anything. When Democrats lose, it energizes their base. Republicans are happy to take credit for economically liberal and nationalistic legislation. And for the legislation that just rewards the wealthy for being wealthy (say, bailouts), movement right-wing and libertarian Republicans can vote against it (and they're mostly in the House) while small consistent groups of Democrats can cross over to make sure it passes anyway.
This is friends cooperating.
Yes true, but it didn't feel widespread then. It was mostly just people who follow politics closely. Now it's nearly everyone.
People forget how quickly Carter screwed up the economy.
Most of the journalists who remain popular tend to be those who are more radical/on the edge of cultural which is how they remained relevant beyond their era so it's easy to assume those people are representative of the population or even the educated class.
The oil shock and stagflation began under Nixon/Ford, and stagflation itself was spurred by Nixonian policy. People seem to forget this quite often. Carter was only president during the last 3 years of the 70s.
Volcker was appointed by Carter and made things really bad for a brief time, but those 20% interest rates ended stagflation, leading to Volcker's reappointment by Reagan.
Biden Abruptly Pulling out of an Afghanistan, was a complete utter disaster. Let’s blame someone else!
Carter made mistakes. His major economic political mistake was to tell everyone that they'd have to basically take one for the team. And we had 12 years of Republican presidents after because of it.
Nixon was just a major chump in many ways. Moreso than almost any other president.
Even a simple look at the timeline shows that is wrong. It doesn't even stand up to a cursory look at the evidence.
Reagan massively escalated the Cold War. There is literally a heading on his wikipedia page entitled "Escalation of the Cold War".
The Soviet Union fell after Reagan left the oval office! The 1989 Revolutions all happened after Reagan left. The breakup of the Soviet Union itself happened well over a year later.
Reagan left the US in bad shape. He slowed down inflation but massively expanded public debt. He left Bush such a crappy economy that it immediately entered a recession that resulted in him losing his reelection run.
Not only that, he started the decline of the US economy. https://www.piie.com/sites/default/files/styles/slimmed_natu... Before Reagan nominal GDP growth was high, after the US turned hardcore conservative, GDP growth has been poor.
I have no idea how Republicans managed to brainwash people so badly that they don't even look at the most basic evidence.
It can really be no other way, short of stuffing all the parliamentary rules like that into the Constitution.
Simply on the basis of accomplishments, whether for good or bad, the founders rank amongst the greatest people to ever exist.
But the writers of the constitution in 1788 wanted a strong one because the existing weak one sucked.
One could squint and say states matter today, but that's just admitting a need for glasses. They are ghosts of what they were, and increasingly need to be retired.
It will be nice when we put to pasture the policy-as-experiments across states for things that are clearly universally demanded: finance, health insurance, women's medical care, education, defense, gun control, decreased corporate control of the food supply, transportation, environmental regulation, and so forth. It's amazing how much the modern GOP has pushed folks towards this, may they continue their business Republican-led shenanigans to unite the country and encourage progress when otherwise we would be slovenly.
Why is this the case? Duplication of fixed costs are expensive.
Let's get rid of these crufty overindulgent home-owners-associations-on-steriods and federalize already.
(paragraphs 1, 4 serious, the rest in jest)
There's ~150 million people that think the opposite should be done.
The problem is that there are too few representatives and so they can build collations that explicitly exclude your interests while still representing you.
I think it would be much better to have some dual-system to send representatives to congress where you could either Vote or Petition to get a representative. If you Vote its basically the same as currently. But if you Petition you and ~150k other people do not get to Vote but the person you're petitioning for is your representative.
Modern capitalists prefer seasonal labor for agriculture. They don't have to feed/clothe/house people year round, and have no personal investment. Seasonal migrant agriculture labor cheap and easily exploited, with little legal protection. Slaves, like domestic a nimals (reprehensible as that simily is), must be treated well enough to keep working productively. There is no such need with migrant labor. If they are abused or killed it is easy to sweep under the rug. There'll be new migrants available next year.
NOTE: I'm not saying slavery is good, or even better than migrant labor. They are both highly unethical if you consider how corporations treat migrant labor today.
…except slavery still exists all over the place in industrialized countries? There’s nothing incompatible between industrialization and slavery, as myriad historic and contemporary examples have shown.
https://www.walkfree.org/reports/global-estimates-of-modern-...
2) Migrant labor is the replacement for slave labor in the USA. These are workers who do not legally exist and thus are subject to the worst of exploitations by employers and criminal concerns.
3) Human beings of all races have a pretty bad record of how they may treat other races/tribes/outgroups. Genghis Kahn killed and raped so many people that he altered the genetic profile of humans. African tribes routinely enslaved each other. Arabs took white slaves. People can be dicks. The list goes on and on: cruelty is a part of the universal human condition.
As bad as the USA, it's the only country to go to civil war to free slaves of another race, even if that wasn't the complete reason for the Civil war.
Even at that, the steam engine was in the process of replacing slaves for many tasks. There were just a lot of tasks left that the steam engine wasn't yet practical to replace slaves - but that would have happened anyway.
"free slaves of another race"? Some of those going to war were people of that race. On both sides.
This is also a bit ahistorical as Lincoln was willing to allow slavery in order to keep the union. It was really the south who chose to go to war in order to guarantee slavery would stay; the north chose to go to war in order to keep the union. The slavery issue was used by the north, initially, to keep the anti-slavery UK from siding with the south.
Of course there was some lead up to that but the actual flashpoint is that the south started it and they didn't do so to free northern slaves. Northern congressmen were not pushing for any bills that removed slavery from the south and etc; there wasn't an imminent (i.e. during Lincoln's presidency) existential threat that the North would end slavery in the South except the one the South manufactured.
Yeah, that's even better than what I stated.
And I forgot to mention that some of those slaves were blonde-haired and blue-eyed with skin lighter than most Caucasians. Maternal inheritance of slavery rule. https://rarehistoricalphotos.com/white-slave-children-photog...
It's weird that you think that they had it better than migrant laborers.
An (immigrant) worker gets none of that and might barely be able to get by even without counting the healthcare (in the US).
Sounds to me like a slave might indeed be cheaper in some/many situations than a minimum wage worker. I'm not convinced either way.
A slave also needs more management. Migrants and free workers will get themselves to the job and in general work. A slave has no motivation to work harder so you need some form of "slave driver" to keep them working. If you try to move your slaves around like migrants move, then you need a manager to go with the slaves to keep them working - migrants manage themselves.
A slave is cheaper if you have a lot of repetitive, low-skill, year round work that must be done by hand. However most of that type of labor is easy for the industrial revolution to automate.
And just notice how often the writers mention not having enough food, or basic clothing. Then get back to us on the idea that slave owners would have taken even minimal care of slaves.
You’ve written how you think it ought to have worked. But that’s not how it actually worked.
Many types of slaves existed and still exist in the history of humanity.
The slaves around Julias Ceasar probably had a different life than the average native Columbus slave (they where almost all quickly worked to death genocide style and he was a total sadist).
Fredrick Douglas didn't have motivation to treat slavery fairly either. (few writers of the day did - thus making it hard for historians to figure out the truth, though in this area there is a lot more data than historians studying something of several thousand years ago).
You might want to check on accounts from e.g. Haiti where slaves' lives were considered very cheap and that's precisely why they were used for the dangerous labour around sugar production.
> Fredrick Douglas didn't have motivation to treat slavery fairly either. (few writers of the day did - thus making it hard for historians to figure out the truth, though in this area there is a lot more data than historians studying something of several thousand years ago).
How does an ex-slave treat slavery "fairly"? He lived that shit, he knows how despicable it is. What other side is there to present? The economic interests of the slaveowners?
>How does an ex-slave treat slavery "fairly"? He lived that shit, he knows how despicable it is.
He can exaggerate how bad it was for one thing. It is well known that people's memories are not exact to what happened, and it is likely he would remember dramatic incidents and not the day to day reality.
Try reading "uncle tom's Cabin" - a book that was written with the intent to start the civil war to end slavery. Despite that intent to presents a picture of slavery that was in general much nicer for the slave owners.
Don't take anything of the above as statement that slavery was good. Only that it wasn't in general as bad as what you see on TV.
If they were too harsh with slaves they'd spend a lot more time and energy managing their behavior. Even in prison privileges are given so they can be taken away. Slave owners probably treated their slaves well enough, in aggregate, that they were capable to work productively and did not have immediate cause for revolt. The slave owners had to live in close proximity to their slaves after all.
The Hollywood portrayals of slavery as essentially unrelenting cruelty and sadism don't make sense, except for on TV. Any farmer would have known that you don't get the best work out of your horses or mules by abusing and starving them. There's a knee point of optimal treatment for all labor arrangements. The EVIL fact that slaves were property of their masters does not change this.
Read the history of the cotton gin and then how steam power made larger transportation easier and expanded populations to consume cotton and tobacco. Industrially produced guns and other tools helped "manage" slaves and later prisoners.
Post-civil war, industrial prison system instituted chain gangs to recreate "legal" slavery and forced prison labor still exists in many states.
The US south ended slavery with the civil war, but most places in the world had a peaceful end. It wouldn't have been peaceful if it was economical as the rich would have fought to keep it.
https://en.m.wikipedia.org/wiki/Confederation_period. "...could not accomplish anything independent of the states. It had no chief executive, and no court system. Congress lacked the power to levy taxes, regulate foreign or interstate commerce, or effectively negotiate with foreign powers. The weakness of Congress proved self-reinforcing, as the leading political figures of the day served in state governments or foreign posts. The failure of the national government to handle the challenges facing the United States led to calls for reform and frequent talk of secession".
The founders wrote reams upon reams discussing exactly what they wanted to do with the constitution and how they intended each and every bit of the constitution to work toward that goal. The intent was basically "we need just a little more centralization in order to deal with the truly national issues."
The government they created to replace the articles of confederation was weak by the standards of the time let alone modern ones.
There's a reason even we don't tend to push a US-style system on fledgling democracies, when setting them up. It's got well-known, grave, fundamental, and avoidable flaws.
The system is broken in ways that prevent fixing that very brokenness. We know exactly what's wrong, but can't do anything about it. You'd have to get a whole bunch of people whose personal power is tied up with the status quo, to, all at the same time, vote to weaken that power and the power of the organizations that put them where they are. Or you'd have to get at least some of the states that benefit from the brokenness to agree to weaken themselves. Neither is likely to ever happen—short of some very risky and probably-bad-rather-than-good developments that are more likely to end in authoritarianism than an improved democracy.
The supermajority of the electorate in the smaller states might be willing to exchange future political influence for sufficient wealth or some other compensation.
The vast majority of things the government touches turn to shit, including things with wide bipartisan support. How does making government able to do more, faster, fix that?
Overtime I've really begun to see this as propoganda that Reagan invented based on little to no empirical data. I'm not convinced that the government is anymore dysfunctional than any large corporation. The belief that the everything the government touches turns to shit does far more harm than good; and furthermore gets in the federal government's way of actually solving problems. The federal government may have a problem with incentives (like any corporation), but it's hard for me to believe they are inept. It ends up being a self fulfilling prophecy - the government tries to do something, a hundred road blocks are put up for fear of ineptitude, then when the government is slow due to said roadblocks, they are called inept. When those roadblocks are removed - for example in the vaccine distribution of 2020, it's clear that the government is capable of good outcomes. Millions of highly controlled and sensitive vaccines were deployed across the country in only a couple months under an administration that nearly became hostile to its deployment.
If you'd please review https://news.ycombinator.com/newsguidelines.html and stick to the rules when posting here, we'd appreciate it.
Robust systems are made up of interacting parts that tolerate partial failures. The reason the U.S. economy as a whole remains strong is because its least efficient businesses are continually failing, and their resources get reabsorbed by more competitive parts. When this ceases to happen (eg. the "too big to fail" banks in 2008, "what's good for GM is good for the country" in 1953), the economy as a whole becomes much weaker. There is no similar ablation process for the U.S. government - lately, there hasn't been an easy way to let parts of it fail while still preserving the government as a whole. This will likely lead to the collapse of the whole government, which is unfortunate. It can't avoid the dynamic common to all systems: the way to avoid total failure is to tolerate and adapt to partial failure.
All of this is to say is that even though large corporations and large governments are alike, the most efficient solution for a corporation (bankruptcy) is not a good solution for government and so despite the inefficiencies we are sort of forced to accept them as the engineering realities of the situation. I fully understand large governments have large government problems, I just don't agree with the notion that having a smaller government is a solution and that the small government meme has largely been toxic to the detriment of the middle class.
In theory democratic government is the check on this - if the government wastes too much money, the electorate is supposed to vote out their representatives and elect new ones that will cut the budget. (In this sense, Reagan-style conservatism is working as intended). In practice, this rarely happens, largely because the average voter is terrible about judging opportunity cost, and every expenditure seems worthwhile in a vacuum.
This is a bit like saying that the goal of government is GDP per capita. Yes, both are important, and both are indicators of doing a good job at something, but what a business does is the most important thing: how does it adapt to reality and make sure it is always doing something useful enough to pay for?
Government doesn't necessarily do things people want to pay for, as then it might do much less stuff, but people do want to feel as though they're getting value for money from their taxes, and that the government isn't spending so much that taxes go up vastly and their currency is inflated so much their careful savings are wiped out.
Why is the longevity of a nation more important than the values it stands for (as laid down in its constitution)? One could argue that it's better to have a great constitution that treats its citizens equally and fairly, even if the nation is short-lived and eventually disintegrates into smaller nations.
The interpersonal equivalent of this would be "It doesn't matter how great your relationship is if your marriage is dead". I'm not sure many would agree with keeping a marriage alive at any cost.
Relatedly, I'm not sure if the GP's Scalia speech actually gets the causality right. I think we could make a good case that the United State's dominance and longevity comes from two oceans, fertile cropland, and advanced technology, and form of governance is a mostly-irrelevant sideshow. You could plop a different government down in North America, and as long as it had adequate incentives for individual innovation, it'd still end up a superpower.
OSHA has no teeth (they are just a nuisance to the scofflaws)
FTC is underpowered
EPA needs shut down
FDA is on record for enabling very harmful medical devices
I remember something about Boeing colluding with regulators to put people in harms way.
I could hop on a search engine and dig up a tome-worth of completely unacceptable shit from the last 40 yrs in this regard.
Power abhors a vacuum. I would rather that power be in the hands of the citizen votes.
The fact is that all these government agencies are preventing specific harms. Throwing them out because of some vague “big government is bad because it might turn into a tyrrany later” isn’t an argument that the harms being prevented don’t exist. It’s a non-sequitor, like saying the sky is blue when someone complains about airplane noise.
>employed by American conservatives ... to deprive the federal government of revenue
which appears to refer to federal level. The general trend of federal receipts have been fairly flat above 15% for decades (except during great recession circa 2009), and the spending slightly different rising a bit above and funded by debt and/or inflationary effects.
My takeaway is here the beast has not been starved, although the beast is spending more of our children's future incomes in the form of increasing debt.
https://stats.areppim.com/ressources/us_spendxrevxgdp_29x10_...
Spot on. Yet we continue to insist on using the system in a way (i.e., overly strong fed gov) that it's not good for. This isn't a Dem or Republican issue. It's history.
And the more taxes Uncle Sam collects, the stronger and more bloated he gets. At some level we need to come to terms with the fact that we're using a screwdriver as a hammer. That doesn't work well. Ever.
Yet nobody seems to be saying the answer is going back to horses and written mail in the name of making our government fit our lives better.
No one is suggesting horses or written email.
It's a simple understanding of history, and a practical and honest observation of how dysfunctional things continue to be. Yet we keep pushing that the answer is more of the same? That's naive. That's not sustainable.
I am not convinced in the "go back to the way it was designed" argument, since you either have to cherry pick the aspects you like, or advocate for reversing women's suffrage, emancipation of slaves, etc.
As soon as we agree that the founders got some things right and some things wrong, there is no more argument that they were prescient and we should revert to their designs.
IMO better to take stock of the current situation and seek changes based on their merits today, independently of whether they align to the ideas of 250 years ago.
Are they really - or are they pretty obvious to anyone who casually glances at the headline of the policy, but the consequences are a problem after the next election. If you win you can always just blame the other side and if you lose you can blame the other side as well.
If you look away from the senators and consider the people the senators represent, it was intended to be even without the filibuster.
But what should be truly opposed is the cowardly way in which the filibuster is done today.
You should make 41 people vote against the bill, on record with their names, then go back to their constituents and explain why they did it in a town hall sometime soon.
Right now a senator can rely on the fact that their re-election is five years away when killing a bill which is supported by their constituents.
41 of them cannot assume they have years for the public to forget their vote on this particular thing (like hurting small businesses by inaction too).
Now anyone can start a filibuster, it largely goes unrecorded - and pressure for party unity prevents it from being killed.
A large enough majority can just change the rules. It isn’t that hard to actually do.
But they prefer it this way.
> people who vote in Republican primaries, who ate it up.
To the best of my knowledge nobody made a movie about Cruz's speech. Davis's speech, on the other hand, became the subject of a documentary debuting at SXSW:
https://spectrumlocalnews.com/tx/austin/news/2022/03/09/docu...
From https://constitutioncenter.org/blog/filibustering-in-the-mod...
"When a Senator signals the intent to filibuster, an informal cloture process starts to determine if 60 votes exist to move a measure forward in two ways. One cloture vote is to approve a motion to consider a measure; the second vote is on the actual measure. If either cloture vote fails, the measure remains in limbo. "
Machaela Cavanaugh has been filibustering the legislature for weeks! 12+ hours a day, weeks on end. She has monumentally impressive resolve.
Actually, I think you missed it. The Nebraska legislature finally passed a bill today.
But then some geniuses decided that we should direct elect both and have two dumpster fires.
this was done because the election process via the state assemblies was so corrupt that Americans regularly made fun of the Senate for this fact.
Rather, you've just got these people who are, at the time of the government's founding, equally powerful (at least in sum) to the government — thus, peers to the government. These people can do whatever they like; they can even have their own private standing armies et al, because your own standing army — the military — isn't powerful enough yet to prevent that.
Thus, you have to give these powerful people a seat at the table, or they'll challenge the legitimacy of your government (or maybe even just get together to overthrow it.) Maybe that's even what they were just doing, until you got them to calm down and talk to you.
One might say that the whole process of establishing a government out of a feudal or contested state, is the bringing of these "peers" to a common table, convincing them that it's in their best interests to solve their problems with the nascent government using plain in-the-open debate, rather than violence or subtle manipulation.
Whereever the peers meet to have that open debate, then, is a de-facto "House of Lords." It doesn't need any laws about it to make it so. The laws grow up over time to enshrine what would be happening regardless.
And in that light, the way "appointment to" a Westminster-system House of Lords works, makes total sense. The government isn't granting people a seat at the table just because; rather, it's tracing the transfer of political power through dynastic inheritance (and explicitly stamping whoever received it with a heritable noble title, so that there's no argument about who the government thinks received the political power.) This is also why noble titles can be extinguished — if nobody directly inherits a lump of political power, then there should no longer be a seat at the table for "the person who currently holds that lump of political power."
The ideal end to a House of Lords, AFAICT, is that eventually all the noble titles go extinct; all the seats are removed; and the House becomes obsolete. I'm not aware of that having ever happened yet anywhere, but it seems to be the intention from the start of every government.
(The American system, at first glance, is incompatible with this end; but it could in theory have approached it, if the American people had been less fans of federalism, and had instead insisted that their own states revert to territories in exchange for seats allocated in a central parliament. I think this could have even been likely, in an alternate world where any of the colonies went down a monarchic or oligarchic route with their state governments.)
Isn’t this “lump of power” just monetary wealth, property, social connections etc? Why does it have to be passed onto a relative instead of any other individual the current power holder chooses?
Rarely people were "adopted". But generally because any relative who might be in line to the power would also have enough power to object to the inheritance passing to another. The hundred years' war was bad enough between two states. Having it within a state is not something the state wants.
In est, your "social connections" — Grey's "keys to power" — value stability of their own powerful positions in your government (or noble house, or family-run utility company/industry monopoly, or whatever other forms lumps of power can take.)
The key-holders' own political power exists regardless, but whether it translates to active ability to affect change right this moment depends on favor of the current ruler. Who better to place their bets on, then, as a replacement for a ruler who will continue to favor them — a ruler who will ensure the stability of the previous ruler's power base — than someone the previous ruler has been grooming for that very job from birth?
But I would argue that, at least for non-totalitarian states, there's also another, more interesting and crucial influence on what makes power legitimate.
When governments and noble houses generate revenue and get things done through free people who they employ or contract — not slaves or serfs or indentured servants — then it's the opinion of those free people on who is the legitimate next ruler, that actually determines who the legitimate next ruler will be. In a non-totalitarian state, a ruler cannot rule without the will of the people. To do otherwise provokes a populist-led revolution to abolish the seat of power altogether.
Looking at how lines of succession of royal seats of power work/are calculated can be enlightening, because there's a certain point where the rules cross over from "what anyone actually a part of the current royal house would want" into "what the population thinks makes someone a legitimate heir."
(The particular thing the population thinks makes someone a legitimate ruler, is usually a result of a centuries-long propaganda campaign by those in power; but no individual who wants power can entirely overwrite that belief during a succession crisis, which is the important thing here.)
Here's the way this works for the UK: https://www.youtube.com/watch?v=46N-bulO-aM
Note in the above, the people that get referred to as "royals" and have little crown icons. Those are the people that the existing ruler grooms as potential replacements, trying to get them established in the minds of their power base.
But note how there are so many other candidates to succession outside of this small group. These other candidates are there not because the royal family would rather transfer power to them, but rather because the will of the people in this case is to follow this weird rule (patrilineal primogeniture) wherever it takes them. (Which is a kind of rule-utilitarianism, in the sense that a society notoriously following this rule wherever it may lead, tends to result in the fewest wars of succession.)
If Westminster gets hit with a nuke one day, and all the current UK "royals" die — and then some con-artist pops up who was living in Morocco, and claims that they're the secret son-by-marriage-twice-removed of the Earl of Sandwich — then what that person is trying to do, is to claim legitimacy in the eyes of the people. They don't hold any of the current "keys to power"; but they think they might be able to step into those relationships and be accepted by those "keys to power", if they can first get the people who work for those key-holders seeing them as the key-holders' new legitimate boss.
This is also true when deciding who initially forms government in a feudal/contested state. Who "won" the War of the Roses, between the houses of Lancaster and York? The entirely-separate House of Tudor. The houses of Lancaster and York, through their violent conflict, ended up killing all the groomed male heirs of both houses — making them both invalid choices for succession in the eyes of the people (because patrilineal primogeniture), and in the eyes of the "keys to power" (because no established relationships left with anyone in those houses.)
And yes, this all still applies even in a country with democratic elections.
Most modern democracies are templated off the Westminster system, and so don't directly elect a president, but rather elect a legislature who in turn appoint a Prime Minister, like a corporate board of directors appointing a CEO. Guess who's getting appointed? Someone with established relationships with keys to power; perhaps hereditary ones. (Consider: Justin Trudeau.)
For countries that directly elect a president and have term limits, the choice might seem to be more in the hands of the people... and often is, at the country's founding. But you then get a primacy of political parties as noble-house-esque government-in-waiting entities, each trying to find and groom politicians into figureheads for the "party line", such that it's actually the party, and not the individual, that establishes the continuous key-holder relationships and carries them forward. The political party acts in lieu of a noble dynasty as the immortal entity conferring stability-of-power to key-holders.
The one way in which political parties aren't just noble houses, is that they will sometimes voluntarily allow outside entities who don't "toe the party line", to come in and take over for a bit — if those outsiders hold their own lumps of power. For a noble house, this would be suicide—they'd be "overwritten" by the outsider's new dynasty. But a political party will continue on just as they were afterward... but now having absorbed and digested the key-holder relationships that the outsider brought with them, into itself. (Consider: Donald Trump.) Though, note, noble houses do absorb external key-holder relationships — they do it through political marriages.
Says who?
From Red Roulette:
> The struggle pitted Xi Jinping against an official named Bo Xilai. Both were sons of Communist "immortals", veterans of Mao's revolution. And both owed their careers to a Party decision made in 1981 and pushed by a high-ranking Communist named Chen Yun to establish a special office in the Party's personnel department called the Young Cadres Section. That section's purpose was to ensure that the sons and daughters of senior Party members were given good positions in the government and the Party. "If our sons and daughters succeed us," Chen Yun declared, "they won't dig up our graves."
> The Tiananmen Square crackdown of 1989 gave this work added urgency. A key lesson that the red aristocracy drew from that turmoil was that, as the saying went, "you can best depend on your own kids." Each leading family chose an heir to be groomed for political leadership. Nominated by their fathers, Xi and Bo rose through the Party ranks.
It occurs to me after typing this that when you said “as entities” you were probably alluding to this dichotomy.
If you’re a big believer in the mythological principles of US government, the idea of people electing representatives shouldn’t be seen as a diminishing of the state. State power is endowed by the creator to the people.
Legislatures aren’t states. The governor is the head of state executing the laws of the people as expressed by the legislature.
If you're a believer in the somewhat more modern American ideal of a purely populist government then yes, the current Senate makes more sense, but then it doesn't make sense as to why the Senate grants equal power to each state no matter how populous.
This has been an argument since the beginning. The thinnest layer (Confederation) was found non-viable and was replaced by a somewhat thicker layer after about six years. There was a lot of argument then, and a lot of argument after the fact, leading to thinning and thickening of the layer.
> but then it doesn't make sense as to why the Senate grants equal power to each state no matter how populous.
Or, under the previous system, why Senators were elected for 6 year terms when they would more easily represent the states' current interests with 2 year terms.
https://en.wikipedia.org/wiki/Cherokee%E2%80%93American_wars
https://en.wikipedia.org/wiki/Northwest_Indian_War
https://en.wikipedia.org/wiki/Shays'_Rebellion - Note that this last one was a Civil War.
The US is currently in 24th place on the corruptions index: https://www.transparency.org/en/cpi/2022/index/usa
And it seems that corruption was not unknown in the states during the Confederacy period, and is claimed to have increased during the Confederacy: https://www2.byui.edu/i-learn/examples/AF_beforetext.pdf
> Between 1776 and 1787 corruption in state governments increased. States where debtors gained control of the legislatures issued large quantities of paper money which depreciated rapidly in value. In Rhode Island the small farmers in the assembly adopted a Force Act requiring creditors to accept the money at original value. Creditors in other states were also discriminated against by mortgage stay laws which prevented mortgage foreclosures for indefinite periods. The problem of factions within a republic, that was supposed to be solved by keeping republics small like the states, seemed became acute as legislatures became controlled by one faction or another and those factions passed discriminatory legislation.
> There were many disputes and tensions between the states that arose over foreign and interstate commerce. The states began using their power to levy tariffs after the war when England dumped such quantities of cheap goods in America that domestic producers were threatened with ruin. As the tariffs were not uniform among the states, commerce gravitated toward such low-tariff states as Rhode Island. Other states, jealous of this trade, began levying retaliatory tariffs against the goods of those favored states. Merchants and manufacturers wanted an end to destructive interstate tariffs and commercial rivalry, as well as aid in their dealing with foreign governments. States also began to argue with each other over the control of rivers and ports so essential to foreign and interstate trade; causing more bitter disputes between the states.
I got the bookends, you can address "global economic whipsaw manipulation, climate crisis, mass incarceration, widespread poverty" if you want.
“USA is 24th on this list!” Great, what were they in 2016? 18. Etc., etc.
Seems like in this new LLM oriented world there’s eventually going to be a way for a post like that to never even appear on my screen.
I normally wouldn't have copy and pasted that much text, but I thought I'd save anyone the time of having to scroll through a 63 page PDF.
And would it have been preferable if any colony could, itself, decide to start a confrontation? "in 1786 the Kentucky militia launched the first major frontier military action since the end of the Revolutionary War."
To save you the effort: I am familiar with US history.
You bet. And I will keep on keeping on into the future. Though I've probably reached my limit for this back-and-forth.
Calling a 10 year war a 1 year war is "familiar with US history"?
Let's go to another confederated country as an example of what might have happened had the US stayed under the Articles of Confederation.
https://en.wikipedia.org/wiki/List_of_wars_involving_Switzer...
It looks like, after the founding and expansion of Switzerland, they had to deal with a number of civil wars (at least one involving no conflict, though others had deaths), as well as periodic wars with surrounding great powers.
I’ve read some interesting opinions on the internet. But I have never heard anyone advocating a pro articles of confederation position.
Had that stuck around, the US would be a dominated an expansionist New York, surrounded by some expanded British colonial entity in the west. The south would be a backwater set of post-colonial agricultural colonies.
I'd recommend hitting up the Library of Congress. I've found a lot of fraudulent versions of Founder writings online, but the Library of Congress should have digital scans of the originals.
Imagine a world where a judge in a post-colonial agricultural colonies tried to tell someone in the modern western world that because the Lord of the universe was very upset about abortion drugs, they were henceforth banned. That judge would be laughed at and life in the civilized world would go on.
I’m not seeing how the AoC would have prevented any of those things. (In respect to some of the global effects, they might have made it more likely the US was part of the global peripheries rather than great power in respect to them, but that doesn’t really change the global situation, just the local experience, and if you think the periphery experience of those things is better…I don’t know how to help you.)
America built in its own rotten boroughs problem as part of the foundation
It removed one of the big checks of "checks and balances" fame.
> Legislatures aren’t states. The governor is the head of state executing the laws of the people as expressed by the legislature.
I'd watch that clusterfuck on pay-per-view. But sure, it'd still be an improvement if you want governors to appoint them.
I disagree on the point that the states have cleaned up their act, what has happened is that the Federal government has taken on more power and responsibility from the States, for better and worse.
Meanwhile, people have become more disconnected from their state politics and only focus on the federal. Up to the point of blaming the federal government for not acting when it is the state's responsibility.
Just like modern reactionary politics isn’t good for people or popular, the biggest fear of slave owners was that free whites would figure out that slaves gutted the value of their labors.
It doesn’t take a “genius” to figure out that having state legislatures select federal legislators is foolish. Anyone suggesting that the US Senate as constituted for the last century is a populist institution may require institutional help of another kind.
> Lol. That was done to placate the slave owners.
This is so wrong that even if it is ignorance and not an intentional lie it is a distinction without a difference.
The 17th amendment was passed ~50yr after the civil war, a point in time when the overwhelming majority of the electorate had no memory of overt slavery and the people who did or who's parents did were even less influential than before due to immigration waves and industrialization (which concentrated population money and power in the northeast and Midwest generally speaking). Please f right off with your revisionist history.
>Anyone suggesting that the US Senate as constituted for the last century is a populist institution may require institutional help of another kind.
This is rich coming from the guy that just said an amendment passed in the 1900s was done to placate slave owners.
Regardless of the intent of the amendment, only a complete fool would claim that making appointed positions directly elected makes the body formed by those positions more subject to populist sentiments than it previously was.
I'm not entirely sold on the idea that direct electing the senate is a bad thing but it doesn't take a genius to look at the situation before and after and see that there are pros and cons to both. Like you can literally pick up a history book and look at the influences the senate was beholden to and strongly pushed around by before and after the change.
Electing Senators directly took a long time to move forward because constitutional amendments are hard. Senatorial elections are statewide events, they are the only federal elected officials elected by the people of a state free of gerrymandering.
The Union is predicated on the States agreeing to certain terms and conditions that guarantee certain State Rights while compromising on others.
One such compromise is representation within the Union, whereby the Lower House (House of Representatives) has the States represented proportionally by population and the Upper House (Senate) has the States represented equally regardless their population. Territories that aren't a State receive no representation.
Additionally, the Lower and Upper Houses each have different duties and powers afforded to them. The Lower House legislates matters concerning money, among other things, while the Upper House legislates matters concerning government appointments and foreign diplomacy (eg: treaties), among other things. Both Houses must also agree with each other on any bills that are intended to go to the President for signing into law.
The States in the Union are tantamount to independent countries in most other contexts, so States' Rights are a very big deal.
Prior to 1913 Senators weren't even elected by the popular vote, they were elected by state legislators. Literally elected by the State. One could argue that actually makes more sense.
That something is working as designed is not an endorsement if the design is bad.
1) Things the founders got wrong on purpose. We've fixed a bunch of these, by e.g. broadening the franchise and ending chattel slavery with that whole Civil War thing. The way our Senate is composed is arguably an un-fixed one of these—it's that way on purpose, but it's, you know, bad.
2) Things they got wrong by accident. These are usually cases where politicking, application of game theory, and bad actors in general conspire to make things work differently than they were intended. This is stuff like the system stabilizing at two viable political parties, and the way the electoral college has worked in-practice almost from day one (but not the way the electoral college favors low-population states, because that part was on purpose, so would go under point 1 if we're regarding it as an error)
As originally designed, the US is not a nation with a strong central federal government that happens to be made up up 50 weak states and a handful of territories and districts. It's 50 strong states who happen to be united under one central but relatively weak federal government. In that context, having States represented equally, without regard to their populations, makes complete and total sense.
Completely by chance, that happens to indirectly overrepresent people you disagree with. That's unfortunate (depending on your ideology), but it certainly doesn't make the entire system broken or bad.
I would love to know what this by-definition version of "bad" is. That's a remarkable finding.
The idea of compromise rarely survives the day. It's a 100% or zero game, lest we look like we actually agree with some of the other side... oh the horror.
Since value is subjective, there is literally no other viable definition of broken, and if you think this is a modern idea, you haven't seen much of history.
Minority rule would be if 40% of the Senate could pass laws at will.
Fractious multi-party coalitions in parliamentary systems commonly fail to scrape together bare majorities- they're not exactly known for making it easy to produce supermajorities either.
Australia, even with a 2 party preferred, still often has smaller parties hold the balance of power. Often this is quite beneficial since the big party has to water down their ambitions.
Perhaps related, but I find minority governments to be the most aligned to how I think things should work. It's not that they can't get anything done, but rather they have to actually engage with the other parties to find common ground. Crazy idea, I know...
My understanding of what happened with the electoral reform promise is that the Liberals wanted a specific form of electoral reform: ranked choice. Unsurprising, because as the centrist party, they would stand to benefit most from that system. Which isn't to say I necessarily disagree with it; personally I think a system that encourages moderation is probably a good thing. Anyway, when the committee they put together to study the issue didn't come back with that option, they just shelved the whole thing.
The problem of using Switzerland as a yardstick is that barely any population anywhere can match up maturity and morality of them, maybe some nordics. Give a glimpse of same freedom/responsibility to otherwise mature British folks and we have brexit.
US has many fine things running for it, but politics (and healthcare, education, criminality etc) definitely ain't it and should not be taken as inspiration. The whole us-vs-them mentality that such longterm bipartisan system brings is very limiting. What if I like low taxes, while also supporting abortions and legal soft drugs? Or any other mix that would be pretty schizophrenic in US.
GP isn't talking about direct democracy but their governing cabinet which is basically how governing cabinets in the majority of Europe are formed.
I don't think that's fair, both to nordics and to British folks. People are mature because the system treats them as mature. If the system obviously has contempt for you and everyone like you, then of course you will act out like a youngest child.
It forces fringe, extremist and "eternal" oppossition parties to compromise and negotiate better terms and it can change elections that are really close.
The filibuster was a hack which has since been weaponized. It should be eliminated. If only to rationalize and normalize the Senate.
The anti-majoritarian case for maintaining the filibuster presumes that tyranny of the minority is preferable to the tyranny of the majority. Often dressed up dressed up in doublespeak slogans like "states rights" (John C. Calhoun) and "entrepreneurial freedom" (James M. Buchanan, Peter Thiel).
It works for that purpose and in that context and IMO is good.
We should return the Senate to be the States representatives in congress, and the House is the People. Instead of having both the Senate and the House be popularly elected.
Return to more republican (i.e Republic not the party) style of governance, and less democratic, but I know that is heresy today where democracy is the new religion and people fail to learn the lesson of Athens
The majority of US problems come from the inherent duality of the political system. Every matter gets split among political lines, with one party for, the other against, regardless of merits. What would fix that would be to move to popular votes (real, proportional popular votes, not first past the post disenfranchising the vast majority of the population), which would result in more parties emerging, which would lead to more nuance, actual debates and compromises.
If your proposal is enacted, what changes? Governors, elected by first past the post (checking the stats for 2022, with 40-60% of the vote)[1], or state congresses, which are also elected by first past the post and thanks to gerrymandering are usually highly partisan with near total domination of one party[2], elect the two senators for the state. What's the difference? Same two parties as before, same stupid dividing lines on every single topic, same impossible to achieve supermajority needed to do anything significant.
Oh, and actual political finance limits. Whoever came up with "companies donating millions to politicians is free speech so nothing can be done to limit that" is either a massive idiot or extremely biased towards big money influencing elections.
https://en.wikipedia.org/wiki/2022_United_States_gubernatori...
https://en.wikipedia.org/wiki/2022_United_States_state_legis...
Isn't this a straightforward deduction from combining an extension of the first amendment with corporate personhood?
I'd think that the actual problem (which manifests itself in many ways other than this one) is that latter legal situation, not the first amendment or the logic itself.
So Elon Musk wants to spend millions on politics it is OK, but if I and 10,000 of my friends want to form a corporation to spend millions it is idiotic??
And if you want to Limit Elon how do you get around the 1st amendment ?
I dont see how you can achieve that while maintaining a support free expression, unless of course you do not care about free speech?
You enforce that all media networks give similar time (and slots) to the different political candidates, treating time spent talking about a candidate or interviewing them separately from ad time.
- greatly reduce the power of the Senate, effectively limiting it to the ability to veto legislation and judicial appointments with a two-thirds majority (effectively a "state's veto" over a runaway federal government)
- the House of Representatives should be elected based on per-state proportional representation; districts are an antiquated concept from an era where people traveled by ship and horseback, and don't really make sense in an age of telecommunications, air travel, automobiles, etc.
- the President should be elected by a direct majority, as the electoral college has outlived its usefulness and exists only to enable a president to win an election with a majority of votes
I am not sure how that is different from today? Do you want all Reps to be "At Large" so instead of voting for 1 person, in CA would would vote for 54 people?
I am not sure that is tenable but an interesting concept.
I have always supported the Wyoming Rule, and supported taking congressional redistricting out of the hands of legislatures moving towards fixed allocation based on something non-political like zip codes.
On the Electoral College... 10000000% disagree. The President should absolutely not be elected by direct majority, that is taking the same mistake of the senate and making it for the president
First and foremost the office of president should be reduced in power, Congress and abdicated far too much power to the executive, that is what has made the Presidential election soo important, is should not be.
Secondly, I would be in favor of a change to the electoral process where by the votes are allocated proportional just like the house, instead of First Pass the Post like we do today, but I would Strongly Oppose just moving to a pure democracy system. That would effectively make many states have no vote in the election of the president and almost fully remove republicanism from the US system, if not completely put us on that path
Ryan Chapman has a great video on DEMOCRACY: From Antiquity to Modernity [1]
Your claim is not based in the actual history of the US, but instead viewing it through a politicized and simplistic lens.
Other than an incredible brief era at the start of the US, we've been imperialistic in our foreign policy.
The problem with state-appointed Senators is that it was warping gubernatorial politics. If you didn't like your Senator, you had to have the state governor replace him, and in practice most people were treating their vote for state governor as a senatorial vote anyway. Direct election of Senators just cut out the middleman.
Furthermore, we should be very careful with veto powers in a democratic system. Have you ever heard about a study which claims that the US is run by rich people? Well, the thing is, it's true, but not entirely. All classes are still capable of advancing an agenda. Louis Rossman can sit on a chair and yell into the microphone about right-to-repair[0] and get a bunch of state bills proposed. But rich people uniquely have veto power. They can, say, have a 'robust conversation' with a Senator or Representative to kill an R2R bill, or have New York State's governor change the R2R bill at the last minute to completely remove the legislative intent.
Filibusters are another veto mechanism; they raise the vote threshold from 50 to 60. Furthermore with the procedural filibuster they are significantly easier to use, so they get used all the time.
You know how Brexiteers were really mad about how the EU has a lot of unelected political appointees making law? They're not wrong about that. You see, whenever a political party in Germany, France, or the UK (pre-Brexit) wanted to push an unpopular policy, they'd make it into an EU-wide regulation and then blame the EU for it, because they think voters are stupid[1]. They were able to do this specifically because the EU works exactly like how the US Senate used to, with member state representatives not elected by the people and thus not accountable to them. And the only democratic accountability provided to stop this is to replace your member state's government with one that'll replace the appointee in the European Commission, which is now two levels of indirection.
Personally I'd rather live in the world with a straightforward democratic system with as little indirection as possible and few veto powers. Yes, you can point to rising populism as a counterargument, but the problem is that populism is rising because nobody's voice is getting heard. The more that the rich use their veto powers instead of relenting to the will of the majority, the more that the majority will turn to non-democratic means of power, and then we'll wind up in a dictatorship with exactly the kinds of people you don't want running things in office.
[0] Right to repair is a political campaign to undo several harmful effects of copyright and trade secrets law by explicitly requiring manufacturers to sell replacement parts and provide unlock codes to pair them onto equipment. It does not actually obligate them to repair the device, in fact that's counterproductive to the actual point, which is to restore ownership of your device (or car, or tractor) back to you.
[1] They're not.
Is 2 wolves and lamb voting on what they will have for dinner. I have no desire to be ruled by the majority. If we had a a straightforward democratic system we would have no free speech, no gun rights, no rights at all really. We would be like Canada or the EU, I have no desire for that dystopia ( and yes I did call the EU and Canada a dystopia for which I am sure many will disagree)
I abhor collectivism, and systems of government designed to promote majoritarianism over the minority... and the smallest minority is the individual
And yes, there must always be dinner. Ok, we aren't literally eating people in real politics, but still, winners and losers must be picked on occasion. This is simply because political resources are limited. Furthermore, the "2 wolves and lamb" situation is less common than you think. Literally speaking, one lamb cannot support that many wolves. Applied to human politics in the real world, 70% of the population can't benefit from harming the other 30% - there's not enough "meat" to go around. But 1% can benefit greatly from harming 99%. So in practice, democratic accountability puts bounds on how shitty governments can get.
Free speech is not a pesky barrier that democracy tries to get around. It is a peace treaty; an agreement by the government that it will not prosecute culture wars. Furthermore, said culture wars are usually pushed by extremely small minorities - i.e. one wolf splits the two hundred lamb votes in half so he can eat one or two of them in the ensuing chaos. That's how you usually get "two wolves and a lamb" rather than the opposite of "two lambs and a wolf", which is more common
And for the record: yes Canada and the EU have free speech. Maybe not as extremely guarded as America does, but it's still there.
I'm not going to get involved in the gun debate aside from pointing out that guns are not a backstop against abuses of government power. You have a pistol, they have nuclear weapons.
The only thing I can think of for why you'd argue that Canada or the EU are dystopias is that they have mildly more progressive governments and higher tax rates. While I'm not going to argue that paying tax is a moral imperative, I will argue that this is the kind of argument a wolf would make. In fact, wolves have been pointing out the whole "two wolves and a lamb" thing for a while now. This isn't an argument against democracy, it's a threat. "Give us what we want, or we'll stop asking nicely."
Collectivism and individualism are a false dichotomy. Any functional society requires both. Extreme collectivism was the fallacy of the Soviet Union, but extreme individualism has it's own problems.
I think we are seeing today that is not true. You seem to be under the same false narrative that the rich do not "pay their fair share", and the poor pay more than their far share when in reality nationally more than 50% of the population pays zero income tax, and 60-70% get more direct government transfer payments than they pay into the system
The people have been continually voting for more and more government largess funded mainly by debt, and by continually moving the goal posts on what "fair share" is and who should be paying that "fair share"
>>Free speech is not a pesky barrier that democracy tries to get around.... And for the record: yes Canada and the EU have free speech. Maybe not as extremely guarded as America does, but it's still there.
Canada and the EU disprove your statement, when people are arrested / convicted because their dog raised a paw on video, or because someone was offended by a tweet or have compelled speech laws to refer to people if they declare their preference... you can not claim to have free speech. Sorry no the EU nor Canada has free speech today.
>>I'm not going to get involved in the gun debate aside from pointing out that guns are not a backstop against abuses of government power. You have a pistol, they have nuclear weapons.
I guess UKR should just give up to Russia then if that is your logic.
In reality you can not control a nation or its people with tanks, jets, battleships and drones. The fighter jets can not kick down your door at 3AM to search your home... The military can not maintain a police state, and enslave a nation. Those weapons are for decimating, flattening, glassing large area's.
The government would not want to kill all of this people and blow up its own infrastructure. These are the very things they need to be tyrannical in the first place.
Remember it took 20 years, 4 presidents, trillions of dollars, and plenty of tanks, jets, and military arms to replace the Taliban with the Taliban.... All the nuclear weapons in the US arsenal amounted to nothing.
So it is good you refrain from the gun debate as you would lose.
>While I'm not going to argue that paying tax is a moral imperative
not only is it not a moral imperative, Income based taxation is actively immoral and unethical.
Some types of Taxation could be ethical such as a Single Tax system on natural resources. Income based taxation should be viewed for what is it, theft of labor, something I assume you accuse the evil rich of doing
Cancel culture is a US thing, bro.
Having lived for more than a decade in both the US and France, I'd say the former is probably a bit more dystopic in terms of how awful it is if you're poor. Also, waaaayy more mass shootings (muh gun rights!).
The only real difference in free speech restrictions between the US and France is you're not allowed to be Nazi in France. You can critique the government all you want, the whole ultra-woke pronouns is somewhat present amongst leftist types but overall if you're a public figure (eg bigshot CEO) with a habit of saying outrageous things you're probably better off being French than American, you're less likely to get completely cancelled for saying something that isn't politically correct in France, although that may change.
> Some types of Taxation could be ethical such as a Single Tax system on natural resources. Income based taxation should be viewed for what is it, theft of labor, something I assume you accuse the evil rich of doing
Let's get one thing straight here - a government is a protection racket. They take your stuff, in return give you "protection", but the exchange is never voluntary - you can't really opt out short of leaving the country. Because the government needs to know just how much of your stuff to take, they invent money - you can read Graeber's Debt if you'd like more info on this, but basically, there's a reason all primitve coins had the heads of kings on them. Because now you know that every tax season you have to give the taxman X gold coins or risk being thrown in jail, gold coins are valuable.
Now if you define a rich person as someone with a lot of resources, you'll notice two things -
1) insofar as they are exploiting the labor of others to enrich themselves, they can only do so *with the help of the government*. Employment contracts only work when you have the threat of force to enforce them.
2) the government being a protection racket, the more you have to protect, the more work it has to do for you - the government do a lot more work making sure Bobby Billionaire's 3 houses don't get robbed, his private jet works because of all the massive technical and regulatory infrastructure that exists to make sure it doesn't fall out of the sky or crash into something, and his hundreds of happy collaborators are all educated in some common language so that they can efficiently create wealth and controlled by a legal system that ensure they won't do anything that could harm his business interest then it does for Homeless Harry who lives off of rats he manages to trap using a piece of moldy peanut butter as bait.
So they "rich people should pay more taxes thing" is not a moral argument - it's just business logic.
You expect AWS to charge Netflix more than some one dev team running a website that 5 people visit per year? Because it seems logical that if you get more value out of a business, that business will charge you more?
Congrats, you believe the rich should pay more taxes, by the logic expounded in the preceding paragraphs ^_^
feel free to ask for clarification if needed, or you can try to point out any flaws in my argument if you see any :)
We would all be a lot better off.
Also, it turns out that when the legislature doesn’t act, because it was deliberately hobbled by its designers, you end up with an ultra powerful executive rather than things being left to the states.
It would be better if more Americans recognized the flaws in the design of our system of government instead of quasi-worshipping the Founding Fathers and insisting that any problems are because we are unworthy of their great design.
Minor quibble, but the filibuster is nowhere in the Constitution. And it was most recently modified in 1975.
And beyond that, it lets party politicians who don't really want to have to take hard votes hide behind the procedural hurdles.
The current version, where you declare yourself filibustered, is too cheap. In the old days, they just filibustered stuff like voting rights, not procedures for borrowing money to support the adopted budget.
Still think they should make someone talk somewhere to keep the filibuster going. Cure seems worse than disease. Doubt they expected routine filibusters
There's no good reason to have the senate, let alone the filibuster and effective super majority required for legislation.
The interesting part of this appears to be that the Republicans removed this from the tax code but were expected to add it back in a new form. This did not occur in time for tax bills to be due.
> Most tax experts considered the removal a budget gimmick so that the 2017 December republican majority could quickly pass a new budget using the budget reconciliation process, which can't be used to increase the deficit after a 10-year period so they had to add a time limit to a bunch of benefits "on paper" to use the reconciliation process.
In 2017, the Republican majorities in Congress passed a budget that would have increased the federal debt significantly over a ten-year period (i.e., it was a long-term deficit increase). Such an increase is not allowed under the rules of the Senate's budget reconciliation process, so they added sunset provisions that would have brought the deficit back down by making some of the deficit-increasing provisions (in this case, mostly tax cuts) expire early.
The next sentence clarifies:
> There appeared to be broad support for fixing it later, but the bipartisan spending bill expected to include it fell apart because they couldn't get agreement on other parts of it.
These changes were made "on paper" to meet the reconciliation rules in time to pass a budget and avoid a government shutdown, but they were not intended to be permanent -- they were just a quick hack to work around procedural limitations. The intent was to fix this later, but the fixes were never implemented due to disagreement about how to handle other parts of the bill.
The advantage of this kind of description is that it gives you a piece of a larger story and leads to some obvious follow-up questions. Why did it take until the last minute for Republicans to pass a budget when they had full control of Congress and the White House? Why couldn't they pass a budget that didn't increase the deficit? Why does the Senate have such weird procedural issues and why haven't they been fixed? You can find some of the answers by looking into the bill itself[1]. But even if you don't you can pick up other pieces later by hearing other bits of news. The factions and political processes that produce bad legislation can be understood, and with that understanding the power to alter them, even if only by voting.
The other kind of description, which I see far too often, treats bad legislation the same way we treat bad weather. It can be predicted a few days in advance, but we have no control over it. It's just something that happens, and all we can do is let it wash over us. The clouds bring the rain and Congress brings bad legislation; thus has it ever been. It's an ahistorical form of learned helplessness.
[1] https://en.wikipedia.org/wiki/Tax_Cuts_and_Jobs_Act_of_2017
One way to think of libertarians is that they do secretly want all the same levers of political power, they just want different people in charge (themselves).
So while I am not endorsing a specific person, consider this next time you dismiss outsiders out of hand. Some people really do pay more correct attention to shit than all elected people in both parties in our government. It seems valid to complain about "amorphous" government sometimes.
As a minarchist (form of libertarian), I would love to see the state operate more efficiently. That would achieve a part of my own personal political beliefs. I recognize the need for a state and the role society must have in shaping it for it to be a stable, functioning state.
Surprise rules dramatically increasing taxation due to political judo performed six years prior is horrible.
An exemption might expire, but then be retroactively reinstated. This happens all the time.
There is the tax law that applies to your 2022 income now, and then there's the tax law that will apply to your 2022 taxes in five years.
I mean this is an accounting trap, it seems the best way to get out of it is to use accounting.
> As the House legislation is introduced, a grassroots effort is gaining momentum among software developers, with nearly 600 small business owners including Landsman and Bennett signing a letter to the Hill desks of House Way and Means Committee chair Jason Smith (R-Missouri) and Senate Finance Committee chair Ron Wyden (D-Oregon) on Tuesday morning, asking for “urgent relief” and warning that failure to bring back full R&D expensing may wipe out their companies.
I assume that's what he signed.
No small business accountant is incentivized to give you creative opinions, they're just going to go with whatever is the most popular practice. They don't give a fuck how much tax you actually pay.
I am not an accountant, but I took 2 years of accounts, and learning to categorize expenses correctly was probably 75% of the classes.
In the example given they received a revenue that covers the entire cost of the software. The problem is that they then used that revenue for payroll which would be fine previously as if you make $X and pay $X in payroll then you pay ($X - $X) 0 in taxes and there isn't a cash flow problem.
To stick with the apples-oranges lathe example. Imagine GM got a loan of $1M for the lathe and they can only depreciate 1/5 the cost of the lathe. So come tax time, GM has to pay taxes on their 800K of "profit" since they can't fully count the cost of the lathe against the loan.
Then they pay taxes on $357,100 of adjusted earnings because under a 7-year MACRS depreciation, it's assumed the lathe lost $142,900 of value in its first year of ownership (under double-declining or straight-line methods).
Your first part is accurate though.
Anyways, this tax law is fucking terrible. W2 Wages should not be capital expenses because you generally won't be using loans to pay them.
If GM needs a lathe and has a reasonable business strategy, they should be able to get their accounting office and their leadership to align on how to make it make sense over 5 years. If they can't, it's a business run poorly, and according to the basic tenets of free market capitalism (which you seem to be leaning on heavily) that business would and should fail.
More generally, this seems a natural consequence of the impersonal ways that businesses treat employees, aka "human capital stock" to use the term of art. Capital stock / assets used for generating revenue should be taxed the same across the board.
Established companies can probably debt-finance development the way GM would debt-finance a lathe (yes, large enterprises often use debt to buy everything possible). Small companies likely won't have that benefit. Particularly because that software isn't necessarily a capital asset that can back a secured loan, the way a lathe is.
VC has spoiled software folks for the past decade. This is just how small businesses become bigger businesses. The dogma of "bootstrapping" in software circles has been distorted into what is now clearly, retrospectively, an unsustainable means of developing industries. There doesn't seem to be any reason to treat software differently from others.
The arguments here given scream of panicked, defensive rationalizations how actually we're super special and saving the world through technology, and how dare they claw back the rewards we're given for enabling humanity's progress.
Arguably, software fits this definition, and under 1221(a)(3)(C) it would not be a capital asset for most closely-held companies (eg a lot of bootstrapped firms).
For most companies, 1221 doesn't apply, but some companies are going to get screwed on this front by having to incur a capital loss to pay for something that is not a capital asset.
In a less legalistic sense, I'm not sure if there are many companies who provide software-backed debt anyway. That would make software less of a "capital asset" than almost any other intangible asset out there.
Also, what are you referring to as "TFA"? The 2023 tax bill?
And generally, corporate-created IP is treated as a capital asset on the books. This is in line with how capital assets are generally treated; as other commenters have noted, the expense of building a factory (including the salaries of the construction workers, if employed directly by the taxpayer) is also subject to capitalization.
So back to software. If I have an idea for some company (lets say Twitter2.0) and I bring in ~10M in revenue from selling ad slots but I also paid a bunch of programmers ~8M over the course of the year and somehow the rest of overhead/expense was 1M. I think we can both agree 10M > 9M and so my business venture is profitable.
However, come end of year I have book 10M - (1M + 1.6M) = 7.4M of profit. You may wonder how I can book 7+M of profit when I spent 9M on 10M of revenue and this is exactly what this whole thread is about, programming salaries must be amortized.
This leads to the problem I have to pay taxes on 7.4M of profit using the 1M that I actually have left over so as long as the tax rate is below 13% there's no problem but if its any higher than I need to take out a loan to pay taxes.
But what this does is says that if the product you created is an asset, the salaries that go into creating that asset should be treated as if it were purchasing that asset. The office building equivalent would be the builder having to treat the salary it paid its labor as a capital expense and amortizing it.
That sounds beyond insane.
That being said, it’s not a material change, if phased in properly, so companies have time to spread their expenses over a period of time.
But it looks like neither was this planned for (not surprising because it’s ridiculous on its face), nor does the legislation phase it in a manner that can be properly absorbed.
In practice companies will get hit hard the first year, but save the equivalent amount over the next 3-4 years. So after 5 years it will be a wash (ignoring the time value of money…factoring in that makes it a loss, but not as much of a loss). The problem is that it will create tremendous cash flow problems as 5 years of tax is paid in 1 year.
Even that seems like a pretty weak argument for what is essentially a tax penalty.
At least for a purchase of a liquid (or somewhat liquid) capital asset, one could, in principle, re-sell it. But most R&D has essentially no direct resale value and is not being done to create a salable asset. It’s done to create knowledge or IP, which, in turn, is used to create something salable.
I assume the purpose of requiring amortization of capital expenses is to prevent abuses like buying an extremely liquid asset, deducting the purchase price, and thus deferring a tax bill.
If the builder is building the thing for themself, they do in fact have to depreciate over the IRS-provided lifespan of the building.
The software equivalent to a builder is an agency. If the agency is building their own software, they now have to do the same thing. If the agency is building for someone else, they expense the labor immediatley.
The two constants are death and taxes, if you don't have the revenue to pay them at your current burn rate, you either find a way to burn less or your company just isn't viable.
I for one can't find it in me to get all that upset about startups paying their fair share of taxes instead of artificially inflating salaries to consume all of their "revenue", thereby hoarding talent away from the labor pool that would likely better serve the country as a whole by working in... really anything besides risky chronically unprofitable startups.
But without that you just seem like you have a chip on your shoulder.
You do understand that if this law were applied to any industry it would similarly kill small companies in those? Like if restaurants had this rule for wages it would devastate smaller, family run restaurants.
Given restaurants aren't in the business of R&D I don't see why you're trying to make an argument based on applying R&D tax law to them. It's disingenuous, at best.
This is precisely what happens!!
In any case, it seems like the result of these changes (if they stand) will probably be to change in some way the amount /and type/ of software that gets written. If the tax treatment of software essentially requires it to be a capital asset, we will probably see people write more software that behaves like a capital asset: shrinkwrapped software rather than SaaS. This may not be a bad thing.
So now small businesses and startups are being thrown into crisis because Congress has accidentally implemented policy that they haven't gotten around to fixing.
But if you are a small shop that build software for other companies, it isn't. You write the software, get a one off paiement and you'll not be able to get more revenue from it in the future outside of a possible maintenance contract. You can't resale it to someone else.
To summarise, the work of many software companies is akind to the work of design office : you do R&D for someone else. The amortization will have to be done by your customer, not by you.
After 5 years, the tax impact evens out to be the same as currently expensing R&D salaries.
And generally, software companies have gotten the benefit of the R&D credit even for things would not have qualified for the R&D credit if it had not involved software, so this change was merely seen as correcting a tax loophole that the software industry has been exploiting (and arguably abusing) for several decades.
If you bootstrap your company to the point where you can afford one engineer's salary, you can only deduct 20% of that against your revenue. I.e. you've paid out all the cash and but you still have to pay taxes on the 80% that is not allowed to be expensed this year.
If your business isn't solvent without tax loopholes, your business isn't really a business.
I doubt most grant proposals have a 20-30% haircut built into the budget like that...
EDIT: By "screwed" I mean that I'm facing a $100k personal tax bill because the company is an LLC taxed as an S-Corp. You can say all you want about lack of planning, etc, but the reality is that many times very small business do not have the budget for a high-end business accountant on retainer. If I were to try to "plan better" to avoid this situation, I would have just not written the grant or tried to do any of it and gotten a FT job or something instead. It's an innovation-killer.
Much ado about nothing.
But yes, this law is awful for SBIR companies, because we're forced to give a giant out of pocket interest-free loan back to the gov
Most university research budgets do yes, and actually more than that.
(If your hiring keeps accelerating I guess not, so major scaling of your team would seem to be discouraged by this change.)
This is corporate tax, not income tax, so is not progressive.
Old:
Year 1: 0 Profit
Year 2: 0 Profit
Year 3: 0 Profit
Year 4: 0 Profit
Year 5: 0 Profit
New:
Year 1: 800K Profit
Year 2: 600K Profit
Year 3: 400K Profit
Year 4: 200K Profit
Year 5: 0 Profit
E.g. stack another amortized round of annual salary each time.
Even if revenue stays the same but costs increase, your Year 5 total for each is "X Profit" where X is the amount of revenue delta from Year 1 to Year 5?
If rapid hiring growth followed by layoff scenarios, you are worse off here: you pay the tax on the hiring boom for at least the first year or two before your revenue might drop enough to make it not matter?
If you're further away from profitability, it's maybe still a wash.
Hire up to 10 Million in salaries in 1 year, but your revenue after 2 years is just 4M - you're still under the window. You only get hit by the difference in the bill if your revenue accelerates a lot (which is an OK problem to have)?
So on one hand it seems like it could reduce poorly planned impulse hiring by spreading out the costs, but on the other hand the "run big losses until we make it" plan is less affected anyway because of the "big" in "run big losses"... so it seems to hurt the sustainable folks more in that case.
Old:
Year 6: 1000K profit
Year 7: 1000K profit
Year 8: 1000K profit
Year 9: 1000K profit
Year 10: 1000K profit
New:
Year 6: 200K profit (End of year 1 amortization)
Year 7: 400K profit (End of year 2 amortization)
Year 8: 600K profit (End of year 3 amortization)
Year 9: 800K profit (End of year 4 amortization)
Year 10: 1000K profit (End of year 5 amortization)
Of course this "wind-down" period is unhelpful if you're actually shuttering the business...
Year 2022: $1m revenue, -$1m expenses amortized to $200k: $800k profit, approximately 20% ($160k) is paid to tax.
Year 2023: -$1m expenses amortized to $200k, previous year's $200k: -$400k loss, carryforward. You cannot carryback 2023 losses to 2022 taxes.
The carryback is how Congress will resolve the issue for people who paid the tax.
The dispute is that you paid $160k in tax in year 1. Is that inefficient? In my opinion, it is. You paid $1m in salaries!
edit: never mind, I completely misunderstood. It really only seems to harm "moonshot" companies, big tech and sustainable companies appear to be largely unaffected
1,000,000 Revenue
- 1,000,000 1/5 Salary expense x 5 years rolling
-----------
0 Profit
So really, it's removing (deferring, or peanut buttering) the startup and ramp up "invent new things" subsidy, while not really affecting steady state R&D if you're not growing talent ahead of revenue.So even in year 5, it's an adverse incentive for putting new/more talent to work.
Even big business may not be able to make as many growth project budgets work.
This seems to be penalizing competition and new competitors, for literally no reason.
What's important is that unconstrained growth is meaningfully checked. This at least makes it possible for others to thrive, even if they're asked to adapt to a new paradigm. I don't see how a thorough analysis could ever ignore this.
What I think needs to be adjusted with GR is simple: Just as time dilates, t'=γt, gravity emission itself must time dilate: g'=γg.
In the case of GR, just replace t with g. t'=t√(1−(2GM/rc^2)).
The problem here is solving for gravity self-interaction concerning gravity emission.
Year one: You go broke. Everyone loses their jobs. You file for bankruptcy. Game over. There is no year 5.
A tax credit is usually an incentive, like if you spend 10k on solar panels you get to deduct the 10k and then the government might say "hey thanks for pushing renewable energy, deduct an extra 2k from your tax bill." That's a credit, which we're not discussing here.
I don't think that's what's being discussed here. The question is whether salaries are (completely) expensed immediately (reducing profits) or whether they are (partly) capitalised (which will reduce profits later but not now).
They don't do that well either. Which is perhaps why the biggest ones are all American
>they have 0% tax credit for salaries
At least in some countries I know that's totally wrong, but depends what you mean by "credit". Salaries are expenses, are not counted in profit.
The biggest software companies (Facebook/Meta, Google/Alphabet, Microsoft, Apple) are all American.
The expense of salaries isn’t deductible against income.
You don’t get that back unless you somehow fire everyone so you can offset income and expenses without more amortization.
That's a pretty big assumption.
How is this going to change?
You're talking about deciding whether or not to capitalize a laptop, a piece of equipment, a vehicle, etc, and over what period. There's lots of guidance for that. This is very specifically affecting the salaries you pay software developers.
I know it used to be advantageous due to the R&D amortization period, and I feel this was abused in cases were there was effectively no research or development (in the traditional sense). How is your example materially different from a furniture shop that has similar revenue & salary numbers, but previously wasn't able to amortize salaries as "R&D"?
Just like how "work" in physics has a precise definition which doesn't mean what it colloquially means, or "tree" in computer science.
In this case, software development of any kind is explicitly included:
> For purposes of this section, any amount paid or incurred in connection with the development of any software shall be treated as a research or experimental expenditure.
The debate over whether Excel counts as programming and thus software development just got a lot more heated. The question is how is "software" defined in the context of the tax code, in particular in the phrase "development of any software" from above.
https://www.lawinsider.com/dictionary/software gives a couple definitions.
Even if this risks an IRS judgement against them, a savvy company might want to take such a judgement to court, and let a jury decide.
Yeah, the love the tax write-off - they don't love paying people to actually research anything.
Here's the IRS' guidance on software: https://www.irs.gov/businesses/audit-guidelines-on-the-appli...
Weld stuff?
That's why you have to take into account that it's "research and development", and not "research" and "development". As in research and the development of that research, not separately research and development.
For the "real" world, Research would be studying different compounds to see which ones work well as anode or cathode.
Development would be creating the industrial processes required to scale up manufacturing, or the ancillary infrastructure to support the new battery, or designing a new package for this awesome new cell. All the things that take the new thing from the lab to a marketable product.
So if you come up with a new method for welding ("My new filler alloy reduces argon requirements by half!" or "My new pulsing methodology results in 23% stronger welds between dissimilar alloys.") That's Research. Then the Development of that might be "How do we manufacture these new filler rods to the exacting specs required?" or "We need to have the EE people incorporate my pulsing algo in our welders. Right now it's running on an Arduino in the lab, we need it included in next year's Welder XL4000 model."
Actually doing the weld is just doing the job.
So, back to software. What kind of coding is considered R&D and what is considered "just doing the job"? I guess creating new algorithms, or new features that you expect to be in the product for years to come; those would be R&D. Whereas fixing bugs, working on Kubernetes stuff, writing database backup routines, etc. would not be?
I don't know. This is just my impression of the difference. I'm no economist.
I would still count the later as R&D. It's akin to having an industrial engineer re-design the manufacturing floor to accommodate for the different manufacturing process of the anodes.
As soon as you need to customize something, it becomes R&D (else you would have purchased it). The "just the job" part is invisible because, well, it's the machine who's doing it (applications auto-start, install, send updates).
That is a small % of welding though. Most is just straight production work. The % is open to question - if I ask you to put a winch mount on my trailer how much of that is custom R&D, and how much is production of the one off product?
If you have a clear, standard approach to the installation, then the development is likely to be a small portion of the work.
If neither of those are true then you are in the hard to figure area.
A programmer building a custom abstraction for domain feature x
A plumber laying a new line from the basement to the second floor
All require some surveying and development of a solution, gluing existing parts together in a unique way
Like if the carpenter is installing some shelves, they are most likely picking a shelving system or approach they know how to work with and measuring for fit, not coming up with a brand new way to mount shelves. They might come up with a new way, it just isn't all that likely.
The entirety of the rule seems to exist to punish small players in the market. A barrier to entry to box out competition.
Even if they are not on a line, few welders are designing the bracket, instead they cut it out according to blueprints (this might be a separate person) and then weld it on. Then they look at the next part of the blueprint and put it on.
If you made a million dollar and bought a million in patents, you still would have no money but wouldn't expect to be paying 0 tax, would you ? How RnD should be taxed is up for debate, but at least the logic is that it's not a simple cost (in comparison to paying a janitor to clean the office for instance)
I kinda see many cases where a salary isn't as clear cut as a simple cost...for instance comparing two cases:
- we buy for a million dollar an exclusive right on an innovative system from a freelance guy that developed it on his own
- we contract for 10k a month the same guy to design and develop the same innovative system, he takes a year or two to develop it.
In one case it's a purchase of an asset, in the other case it's a salary. The resulting asset is the same though.
But if you make an employment contract with somebody it is totally unknown what is the value you are or will be getting out of the employee. You are not buying an "asset" because you can not own an employee. They can quit any time.
> you can not own an employee.
You own everything the employee produced during the contract, whenever they quit.
Time spent is NOT an asset, it is consumed, hour by the hour. It is an expense.
It is not an asset also because you can not choose to sell it to someone else and thus recoup the money you have placed on it.
You'd be saying you didn't pay for a house, instead you paid an architect to come up with the blueprint and paid the salaries and purchases of a construction team hour by hour for X months to execute on the design, additional work included, until you got a satisfying product. An accountant looking at it afterwards would still tell you you now have an asset estimated at Y thousands on the market.
> you can not choose to sell it to someone else
You can of course sell a developped product or a service to another company. Or even just the research part if it would cost enough to the buyer to reproduce it.
You didn't pay the architect to work on the blueprint, you paid FOR the blueprint.
The blueprint is an asset, architect's time is not. You are not the employer of the architect, you are their client. The business transaction is money-for-blueprint. Whereas with an inhouse software developer the business-transaction is salary-for-time-spent.
If the software developer does not come up with a working program you can not take away their already earned salary. Whereas if the architect does not give you the blueprint you don't have to pay for it.
And once you get the blueprint you can sell it to someone else, it is an asset. Once the SW-developer-employee goes home you might or might not be able to sell their work-products to somebody else, because maybe the program does not run. If it does not run you can not sue the employee. If the architect's blueprints do not produce a working house you can sue them.
It's never supposed to be about what's "fair" or what they "should" do. It's about the fact that they want to spend $X, and need to raise $X one way or the other.
In this case, though, it was purely a trick. They were required to balance the budget over the long term, so they spent money now and identified a pot of money they could take from later. They just kicked the can down the road, and now we've arrived where the can landed. They actually don't think it's fair, or reasonable, or productive. But changing it does make somebody responsible for a huge increase in the deficit... and it's the people who spent the money 5 years ago.
This change taxes you on profit you never made, and specifically targets software companies.
It’s insane.
Salaries are already taxed as individual income. Taxing them as corporate profits and individual income is not closing a loophole, its double-taxing.
Are you just framing up a mobile app for funzies?
Wouldn't it be a professional service, therefore an expense, therefore fully tax deductible?
It's not "just an expense". Think about an architect designing a house. The tax treatment depends on how the person spending the money "uses" the labor. It might be an ordinary operating expense (fully deductible), but could also be inventory, or a depreciated "capital asset" (closely related to the idea of "capital gains" taxes) whose value is spread over a long period of time, generally related to the asset's usable life.
There is a large body of work around the correct treatment of this stuff, which sits at the core of accounting in the same way data structures sit at the core of CS. It's not the most straightforward thing to explain. The tax code contains a ton of exceptions, but in general, a thing that is long-lived, expensive, not routinely bought or sold, and provide some kind of long-lived economic benefit (e.g. shelter, the ability to produce something, or facilitate some kind of industrial process), is a capital asset. (Sounds a lot like software, doesn't it?) Inventory is something routinely bought and sold, generally for profit. A server is inventory for Dell. For a typical software startup, it's a capital asset.
The whole point of accounting is trying to accurately measure economic activity. It's more complicated than it looks. If you agree to a five-year contract and get paid upfront, not all that money is "earned" (hence taxable) in the first year. If you're in debt and the debt is forgiven, no money changes hands, but that's very much beneficial (and taxable) to you. And if you own a long-lived asset, you don't just get to say, oh, I spent all this money upfront, that's an expense I can use to reduce my taxes. Not how it works.
Just trying to shed some light on this. It is indeed rather complex.
If you are getting paid to build the house because you're in the business of building houses, then yes it is an expense. If you're building a house to keep ownership of and rent out, then no, that cost has to be capitalized and depreciated over the expected lifetime of the improvement.
The general question addressed by this law is "should it be allowed to reinvest profits tax-free and delay paying taxes indefinitely?". There are many places in the tax code where this answer is "no" (eg you pay taxes on bank interest yearly, even on a long term CD), and there are many places where this answer is "yes" (retirement accounts, US savings bonds, stock buybacks, 1031 exchange).
It's ridiculous that software development is getting singled out, given that for most business activity the answer is default yes, with only specific list of things that have to be capitalized. I'm just saying the right answer isn't set in stone, apart from of what the tech industry has gotten used to and how effectively abrupt this change was.
Of course, if anyone had owned real estate, they'd understand things like depreciation, and the fact that you can spend money without it being an 'expense', or that no, just because you 'made $1,000,000 and spent $1,000,000' doing something like building a house, or a piece of code, you could of course show an accounting profit. You created something of value--that's the point. There's something of value left over. Maybe there won't be in five years, but you can't expense the entire thing immediately.
I actually think this treatment (capitalization of software R&D) is more "correct" from a theoretical accounting perspective. Clearly, software companies are creating something that has residual value with all those developer salaries. As for the politics, I'm not sure. I do know that RE has the same problem (accounting profit can run far ahead of cashflow), but has so much crazy advantaged tax treatment (arguably "loopholes")--1031 exchanges, bonus depreciation--and that's on top of stuff like 179 expensing (not specific to RE I know, but still), that maybe software just needs to work more like RE, where the baseline is "many things capitalized", but all sorts of crazy loopholes driven by the whims of short-term politics.
It certainly makes the accountants rich...
FWIW, my wife's architecture practice is dealing with this 174 amortization (on their salaries, some of which were classified as R&D) and it's killing them, too.
When you say some of your wife's architecture practice's salaries "were classified" as R&D, who/what did that classification?
I'm wondering if a lot of the pain is being caused to businesses that were classifying as much as possible as R&D to get the tax credit, and now that classification is a liability and they can't change so quickly. Otherwise it would seem that established companies could call much of their software engineer activity "maintenance" rather than "development" (and the change shouldn't really matter to pre-revenue startups).
https://www.grantthornton.com/insights/articles/tax/2023/sec...
The developers, who are paid rather handsomely, also pay rather large amounts of taxes from their salaries. (If fired and jobless, they stop doing that.)
This is not about tax credits, this is about whether salaries are an expense. If Widget Inc makes and sells a bunch of widgets for $100m, and then they pay $20m in rent, and $30m for materials, and $40m for salaries, with $10m left over, with no other complexities (eg, interest, depreciating factory equipment, etc.), then is their profit this year:
1) $10m (or maybe a bit less, if they got any tax credits)?
2) Some other larger number closer to $50m?
You'd be hard pressed to find many jurisdictionns where the answer isn't option 1. I certainly don't know any offhand.
On the one hand, Section 174 clearly stipulates: "(3)Software development For purposes of this section, any amount paid or incurred in connection with the development of any software shall be treated as a research or experimental expenditure." [1]
Section 174 R&E expenses are much more expansive than what qualifies under the R&D tax credit criteria. This article has a rundown of some of the activities included in 174. It's well beyond software or salaries -- it also includes things like market research. It also includes any expenses in connection with R&E, so for example time using a server for new features or new products would have to be amortized but maintenance (bug fixes) wouldn't. Even if a company files for R&D tax credits, they won't be able to offset this increase. [2]
Lastly, since Congress was widely expected to revert this before it took effect, the IRS didn't issue full guidance on how to implement it. They've never had to define software development before, but the interpretation that Big 4 accounting firms are taking is that it covers new products AND new features on existing commercial products, but not straight maintenance.
[1] https://www.law.cornell.edu/uscode/text/26/174 [2] https://www.forbes.com/sites/lynnmucenskikeck/2023/03/24/fiv...
I am not a tax expert, but it doesn't seem like there's any reason you have to claim software development as R&E.
I wonder what this section and any software means
But AFAIK you don’t need to claim it as R&E. That everyone has to claim all software development as “research and experimental expenditure” seems completely unfounded and a misunderstanding.
Link [2] lists activities related to software development and includes maintenance and debugging.
• Programming
• Tuning and benchmarking of software
• Performing software maintenance and debugging
...
Asnwer: It's not mandatory.
There's been a bit of stink recently in the UK around R&D tax credits and how companies have been taking the tax man for a bit of a ride.
> The amortization period is five years for domestic expenses and 15 years for foreign expenses. Additionally, for the first year of the amortization period, the expenses are “placed in service” at the midpoint of the tax year. Thus, the deduction in year one is only half the amount it will be in subsequent years.
Does anyone know what the situation is in other countries (in particular, in Canada) for the same situation as above?
One option companies have, if this isn't fixed, might be to re-incorporate, or relocate their company to Canada[1].
[1] Assuming Canada taxes sensibly (and allows R&D or developer salaries to be deducted).
Amazon was founded in 1994 and it started to make profits reliably in 2016 : https://www.macrotrends.net/stocks/charts/AMZN/amazon/net-in...
Fine print: this is only available to Canadian-controlled entities. Foreign-controlled entities can claim R&D tax credits as well, but the rate is far less generous.
It sounds like Canada is trying to make it as easy as possible for companies to set up shop in Canada.
Personally, even incorporating in Canada is so much easier. A federal corporation just costs $100 to make, and even less to maintain annually. (In contrast, an LLC through Stripe Atlas costs $500, and you have an annual recurring fee $300 owed to Delaware + registered agent fees.)
1) R&D classification of a single employee should be a percentage. Accountants don't list employees one by one on a tax return, they're grouped together and a percentage of their wages can be allocated to different functions of a business outside of R&D.
2) A lot of things do not qualify as "R&D". For example...
- Fixing bugs
- Maintaining existing features
- Improving existing features (even enhancing functionality)
- Building a feature because sales promised it to a customer
- Refactoring code
- Anything related to devops/infrastructure, upgrading servers, updating dependencies
- Anything related to customer support, onboarding or retention
- Anything related to helping Sales/Marketing close new business or get more leads
- Anything related to supporting day-to-day business operations
I'm not an expert, but I think it will be relatively easy for accountants to do some magic behind the scenes by classifying only a small percent of wages toward R&D.
I think the average engineer spends less than 20% of their time on "true" R&D, and if that's the case, 80% of wages can be deducted as an expense without amortizing.
> ANY amount paid or incurred in connection with the development of ANY software shall be treated as a research or experimental expenditure.
I need a website with some features. Asking a sample of professional software developers how to build it, you get a variety of answers.
If anything, that the basics of software development still requires R&D is an indictment of our fields lack of professionalism.
This is a bit much. "Research" maybe, but not "development". Many things are developed -- land, buildings, etc. Someone still has to do the work.
What are they welding that has four corners to make squares?
Also the parent clause says: "In the case of a taxpayer’s specified research or experimental expenditures for any taxable year—"
So just don't specify the expenditures as research or experimental if you don't want this section to apply.
Based on all of the items in #2, the average software engineer spends close to 0% of their time on R&D - with rare exceptions for those working on cutting edge tech, in research roles or maybe super senior engineers figuring out how to solve complex technical problems
The rest of us just write code and sit in meetings
1,000,000 Revenue
- 1,000,000 Salary expense # this does not magically shrink to 200K
- 200,000 tax on revenue (random percentage out of a hat)
-----------
(200,000) In the red!
If paying salaries isn't an expense you can write off, you still have to pay all those salaries, and then pay tax on the money used for those salaries.What you are showing is cash flow not the income statement and also you don’t understand the tax is based on the income statement and not the salaries being paid or the revenue, but the calculated income for tax purposes.
In the 2nd year it will be 2/5ths, $200K, amortized expense of prior year plus current year, assuming same numbers, and by the 5th year would be full amount.
Your cash flow is correct and yes it becomes -$200K which is really bad. However I wanted to clarify the mechanics.
I've written an accounting system before for business activities and successfully used its reports to win a tax dispute.
I'm not so interested in the details of this, particularly because it's in another country, but I do understand the implications of suddenly not being able to entirely write off the likely most important and large business expense.
I also wrote my own accounting systems based on ledger-cli and regularly deal with amortization of assets.
The change is extremely bad and I’m not trying to say otherwise. Just wanted to clarify the exact calculation and difference between income statement and cash flow calculation.
https://www.nytimes.com/2017/12/19/us/politics/tax-bill-vote...
"the most sweeping rewrite of the tax code in decades"
If they don’t fix it a lot of companies (and their owners) are going to go bankrupt.
For example:
- Your uncle owns a farm for the last 50 years
- Over the 50 years the farm's land value has risen to $1,000,000
- The farm itself only generates $20,000 a year in profit which is spent on living expenses
- Your uncle has no savings
- Your uncle dies
- A 40% federal estate tax is applied onto the farm's current value from your uncle's death (state taxes might also be added)
- Whoever owns the farm is now responsible for coming up with $400,000+ or you're forced to sell the farm to cover the tax bill
I might be butchering this so please correct me if I'm wrong but this feels like a system that helps larger companies because it prevents a smaller business being able to exist multiple generations.If, instead of being $1 million, the farm (assuming it was the whole of the estate) was worth $13.92 million, the actual estate tax would be $345,800. Assuming the same ratio of annual profit to value in your hypothetical, the annual profit would be $278,400; so if you had no other assets to pay the tax, you’d probably need to borrow against the profits, but that shouldn’t be too hard given their magnitude.
The numbers are much, much larger than a simple $1m family farm.
Also, remember, that cap is a exemption from the value. If you have a farm worth $14m, you will have to pay approximately $400,000 in estate tax (NOT 5.6 million like you would naively calculate). At that point, if the farm doesn't generate (effectively) any revenue, and it's not mortgageable or you can't secure a personal loan, it's probably best for everyone that it be sold. You certainly wouldn't be able to e.g. pay property tax on a property that size.
The estate tax is the most widely misrepresented thing in the tax code. It's designed to prevent multimillionaires and billionaires from passing down their entire fortune to the next generation intact. It almost never affects anyone but the top 0.5% wealthiest people in the country, and only then if they do absolutely no estate planning whatsoever.
In addition to what everyone else says, if you have a multi-generational business the owner should be bringing their child(ren) in as executives and part owners of the business. The estate tax would only apply to the part of the business the original owner still owned at their death, not the part of the business owned by the child(ren).
If anything HN should be cheering this law since it incentivizes growing your R&D team quickly and consistently.
But! You get to pay taxes as if you made 800k in profit. So lucky you, you have zero dollars and now you get to pay 240,000 in tax (800k * 30%) to the government.
You're now 240k in the hole. Game over, no year two, three, or four.
This doesn't affect venture funded companies as badly because they have millions in funding and they can ride out the amortization. It does, however, affect bootstrappers trying to start a thing. Perhaps you could call them small, indie hackers?
If anything, HN should not be cheering this law as it doesn't affect large incumbents and those with millions in VC funding, but crushes the little guys.
Like, we agree that’s what depreciation/amortization is, right?
So this most affects companies that have a relatively large R&D org relative to the past few years (aka my point about growing R&D ahead of other functions).
Maybe this will help you.
If (as you imply) SW developers are critical to this year’s revenue (vs. building for future years revenue), then why don’t they go in COGS?
Seems like an easy way to solve the problem…
Ok, so we're on the same page! Salaries should be expensed!
Unfortunately, the page that you and I are on is NOT the page that United States Government is on. Which... is the point.
You said in a parent comment
> So this most affects companies that have a relatively large R&D org
This has nothing to do with R&D orgs. We're talking about software developer salaries, not R&D. According to the new change, all software developer expenses must be amortized over 5 years, which you and I both agree seems like a silly idea.
I think you're arguing for a common sense approach of not categorizing them as R&D, which I would highly encourage you to run past your CPA before you accidentally commit tax evasion.
You think that all sw devs now are in R&D and not COGS?
Golly! Plenty of SW devs who work on this years revenue are COGS throughout the industry. The game is putting sw devs who work on future years’ revenue in opex.
Since you’re so attuned to cash accounting let’s change up your example.
I prepay $1mn in advertising cost for ads that will run over 5 years. I spent that cash now, but should I be able to expense that whole $1mn this year?
EDIT: Don't believe me, here's Airbnb:
Cost of revenue includes payment processing costs, including merchant fees and chargebacks, costs associated with third-party data centers used to host our platform, and amortization of internally developed software and acquired technology.
Huh? I don't think that, that's literally what this law is doing. Moving all software developer expenses out of COGS and into R&D that must be amortized.
You're arguing what should be, and I agree with you. It should be COGS. If you go read the law (or... even the article) you'll realize that what should be the case, is not the case.
It has nothing to do with what I think!
> Since you’re so attuned to cash accounting let’s change up your example.
> I prepay $1mn in advertising cost for ads that will run over 5 years. I spent that cash now, but should I be able to expense that whole $1mn this year?
Umm if you're doing cash accounting, yeah. Haha. That's not the point you were trying to make though. If you're doing accrual accounting, no. That's a prepaid expense (asset) which changes to an expense over time as you incur it.
If you want to learn more about accounting, I have a website where I teach introduction to financial accounting topics at https://acct229.com. You might enjoy it!
My earnest advice to you is sometimes slow down and really think about what other people are saying.
That note is financial accounting, we're talking about tax accounting. Entirely different worlds with entirely different rules.
EDIT: Just my final reply - this law has nothing to do with COGS. I'm saying R&D is usually a category with multi-year amortization, it's only recently that an exception was made for political reasons.
You are arguing that R&D expense should always be expensed in year, which I assume is a product of not having seen what the normal world was like.
This isn't even a new law fwiw, it's not extending the exception to the existing law.
You said:
> If the developers worked on this years revenue, they should go into COGS,
That's no longer legal.
So they were not really 'researchers', working out on unknown with high risk probabilities, instead they were building an asset that made you money the same year.
You would deduct the payment to these consultants as expense. they pay their own taxes on their salaries.
You are left with an asset that you can make money on, year after year.
That's, I think what they are thinking.
But a) you were not prepared to turn your salaried employees into consultants b) the asset requires extensive up-keep, that costs as much as money as it was to 'create it' c) the asset value without the up-keep can become zero in year d) the asset itself is very risky and may not have value later on.
So I overall agree with your sentiment.
The gov does not want to classify software dev as 'research', but yet -- they have not established how to fairly classify it.
This is a clustferfuck.
Also operating losses can be carried forward and used for 20 years, so recognizing a big loss in a single year isn't really that bad.
0 Revenue
- 1,000,000 Salary expense
-----------
- 1,000,000 Profit
So doesnt really make much differenceIf you were running a small software company that make 2m in revenue and puts 200k to the bottom line, your business no longer works.
I have a favor to ask HN: is there anyone going through this that would be willing to share a redacted version of their accounting change statement[0] required to comply with this law by Rev. Proc. 2023-11? It's not at all clear to me (not a CPA or tax lawyer, but normally perfectly capable of doing bookkeeping/accounting for my single-member LLC) how specific "(D) a description of the type of expenditures included as specified research or experimental expenditures" is supposed to be. I filed an extension today because I'm now second-guessing what I wrote; my Google-fu has thus far turned up zero examples of a CPA-blessed version of this statement. (Probably because one of the other statutory requirements is that it includes the taxpayer's identification number.)
[0] Rev. Proc 2023-11: https://www.irs.gov/pub/irs-drop/rp-23-11.pdf [PDF]
I don't have a strong enough understanding of the change to really have an opinion, but that seems to be the clearer description, the R&D spending is being treated as an investment in the business (which it probably is) that results in capital (who knows if that is true).
I'm actually surprised people are freaking out about this. Of course software is R&D. And of course you don't just get to expense it all at once. It's long-lived, like you said.
Maybe we could have some tax breaks like our friends over in real estate, but I very much think the base assumption should be that software dev is capitalized.
People are freaking out because it's a gigantic change that there wasn't any awareness around.
However, the "asset" associated with software development seems pretty uniquely hard to transfer. Almost every other intangible asset has a strong marketable component (eg a patent on a widget, a copyright on a song), whereas software just doesn't have one. Licensing doesn't count here - that's not a transfer of the asset.
For sure, lots of software is pretty tied up with the day to day operations of a particular company, but so are things like a specialized manufacturing line or whatever.
Not really trying to argue how that should impact the accounting, just arguing the specific point.
When you build a manufacturing line, you usually buy your equipment off-the-shelf (capex, with good resale value) and hook it up in a semi-custom way with cheap, movable conveyors (also capex, with resale value). This means that you can make a "stuff" company with practically no R&D. In that world, you only do significant R&D of any kind once you are big enough that your chance of going bankrupt before the end of even a 15-year amortization period is pretty small.
Even in those companies, the work product of R&D groups is often relatively modularizable and transferable. For example, your R&D group may modify a machine to produce coke cans 10% faster. That improvement is likely transferable to pepsi. You may also patent the improvement, but that's not required for it to transfer well. Your R&D can also be hard to transfer, like specific factory layouts to make $widget that only you would ever want to make, but you're only doing that research when you are an established manufacturer, which makes the depreciation not a big deal (you probably prefer to capitalize that expense anyway).
The fact that the work product of R&D is somewhat transferable at a price near how much it cost to produce is what allows you to get loans backed by R&D work (technologies, patents). Without the secondary market value, you don't really have an asset.
In contrast, companies whose primary work product is technology (software companies and some digital hardware companies) do significant R&D from day one, both before proving the value of the R&D work and in a way that it usually isn't sellable or modularizable.
Like the coke cans, there's probably a market of people who would buy the product "patch that makes redis 10% faster," but the tech transfer mechanisms we have today don't support that market well (if at all), and most startups don't waste time improving redis. There is almost certainly no market that would buy "efficient database schema for a SaaS for gravediggers," which actually is what occupies your time if you're building a SaaS for gravediggers.
That suggests, using the "capitalized R&D" and "software development is R&D" ideas, that the first few years of a software company will pretty much always involve vastly overpaying for an asset with likely no real resale value. That is very different than how a traditional capex works: usually the vast majority of the price you pay on a capex goes into the value of the asset.
So that leaves us in a weird sort of void. I assume the very-long-term solution is to figure out how to make an IP rights system that actually works for software (eg a new kind of patent), so you can finance your software R&D the way you do a house.
Isn't it what's happening when a company gets acquired? Buyer pays for a software and a team (more for the latter usually, including business process as a whole), not for laptops or servers. It's not "equal" to salaries but you can't create the former without the latter. So in a sense when you pay salaries your create the above-mentioned "asset".
Office Manager: 100% expense.
Software Engineer: 20% over 5 years (actually only 10% for the first year).
If they’re international then 6.67% over 15 years.
Not only that, but the effect “stacks” over the years.
So year 1:
1,000,000
- 100,000
————————-
900,000 Profit
Year 2:
1,000,000
- 200,000
- 200,000
- 100,000
————————-
500,000 Profit
Year 3:
1,000,000
- 200,000
- 200,000
- 200,000
————————-
400,000 Profit
Year 4:
1,000,000
- 200,000
- 200,000
- 200,000
- 200,000
————————-
200,000 Profit
Year 5+:
1,000,000
- 200,000
- 200,000
- 200,000
- 200,000
- 200,000
————————-
0 Profit
By the time you get to year 5, you’ve paid tax on $2,000,000 of phantom profits you never had.If you’re a C Corp that’s $420,000 in extra federal taxes (plus whatever state tax).
If you’re a smaller company you’re probably a S Corp and federal and state tax could be ~50% passed through to your personal return.
How any owner survives that, I’m not sure.
Year 5 is just a steady state of no more phantom profit taxes, but you never really get that extra tax you paid back if you want to keep operating at the same level or grow.
So Musk was following a playbook after all...
After 5 years the first years salaries are considered to be a "finished" R&D project, which means there's nothing left to amortize.
The only thing like that is that if, after a few years, you fire all your devs (or at least, all devs working on adding new features and building new products), then you can keep amortizing the last 4 years of salaries for your now-fired workers over the next few years, which reduces your tax base. But I mean, by that point, who cares? Any software business that has fired all its devs is over.
If you spend is going up, you're pre-paying more and more tax on profits you haven't earned yet. If your spend is constant, you'll stay the same amount behind. If your spend declines you'll start to catch up, and if it drops to 0 and stays there for ~4 years you'll catch up to where you would have been without the law change...but if you start spending again you have to start pre-paying again.
If you buy a building, you can’t depreciate the whole thing instantly, you do it over the life of the building.
The same should hold of course if you buy software.
But if you ask your employee to perform a task like writing a program you are not buying anything. You are paying the employee's salary whether the software they are writing ever gets out of the compiler or not.
So wouldn't there be a way around this by changing the titles of software developers to "software janitors" for instance ?
Feels like this is just a move to stop companies from gaming expenses to avoid profiting. Piercing the corporate veil, if you will.
Thinking about it more, perhaps it's a mistake to assume that the software being written has a service lifespan of five years.
If they spent a million, made a million, and are now back to square one, it would make more sense to not amortize the investment because it's not an investment.
It's also pretty harsh on a business that's just plain unprofitable. The laws should be arranged so that if you start a business and it's a flop, but you have no debts, you can walk away pretty much unscathed.
In theory, but good luck getting a loan secured against IP for a reasonable rate.
Honestly this is a bit like SVB all over again - poor management, in this case not knowing or understanding critical tax laws. And if you did know, shame on you for not contingency planning for Congressional ineptitude.
EDIT: Nevermind, you had it the right way.
This way, they are an expense to the corporation, and each one of the consultants pay their own income tax.
In that way the corporation building software for sale/SaaS is treated the same way that a corporation that's buying and then renting out real-estate, for example.
I’m missing why software salaries are amortized against just straight expenses?
Forcing sofware dev salaries to be considered R&D then forcing all R&D expenses to be amortized over five years? There's a name for that kind of behavior.
It's theft.
Also, if you classify the employee differently, does that change situation?
Really perceptive comment.
Until 2022, companies had the choice between expensing and amortizing software development under Section 174. (Section 174 specifically calls out all software development as falling under that section.) So they would only time track when they wanted to get the R&D tax credit, which only covers a portion of software development activities. R&D tax credit software development is a much narrower scope than R&E software development. So it didn't matter until now.
Seems pretty obvious to me that the section only applies to what is claimed as R&E. Software development doesn’t have to be claimed as R&E, but if it is, now it unambiguously qualifies.
Nothing forces you to classify engineering salaries or even contract expenses under the provisions of section 174 which describe “research and experimental expenditure”. There are some reasons historically why people elected to do that, but that may be a bad idea moving forward and honestly seems rather dishonest to me. No, your Jira clone is not “research and experimental expenditure”, it’s just a fucking database with a UI… just like 97% of all other startups. It’s more like: if you can use section 174 because you spun up a project to research curing diabetes with nano bots, then your software development allocated towards the project also counts as R&E, cheers.
Repeat after me: “my core business is not a research and experimental expenditure, it’s just a normal mundane boring operating expense”.
" “specified research or experimental expenditures” means, with respect to any taxable year, research or experimental expenditures which are paid or incurred by the taxpayer during such taxable year in connection with the taxpayer’s trade or business."
and
"For purposes of this section, any amount paid or incurred in connection with the development of any software shall be treated as a research or experimental expenditure."
And yet that's the letter of the law. R&D expenses must be amortized over 5 years. Software development must be counted as R&D.
There is no consideration in the law as written for categorizing software development differently.
That's the reason this whole scenario is a problem in the first place.
It says “For the purposes of this section…”, so it doesn’t apply if you’re not claiming R&E credit.
> For purposes of this section, any amount paid or incurred in connection with the development of any software shall be treated as a research or experimental expenditure.
Where "this section" is "§174. Amortization of research and experimental expenditures"
Tax credit is separate from amortization afaict.
Yes, if some of your expenditure falls under R&E, then you use section 174 which says any portion thereof involving software development must be amortized.
What’s described is a cause and effect relationship, not a global mutation of all expenses.
> Where does it say that all your business expenditure must be considered R&E and consequently are subject to the provisions of section 174?
It doesn't, and neither did I. It states that all software development is seen as R&E
> Yes, if some of your expenditure falls under R&E, then you use section 174 which says any portion thereof involving software development must be amortized.
> What’s described is a cause and effect relationship, not a global mutation of all expenses.
That's not how I interpret it. Section 174 states that all sw dev will fall under R&E. By your logic, you could rule out any "Special rules and definitions" of all sections. Again, it's not about "all expenses". It's about "any amount paid or incurred in connection with the development of any software". Basically payroll, contractors, and even outsourced companies.
To prevent massive outsourcing, the amortization rate is 7% (15 years) instead of 20%.
Look at it this way:
A "machine" must be amortized. In its lifespan it wil generate some sort of income (almost by itself). Software can be seen as a "machine". Makes total sense.
Here in NL, if you mine bitcoin. You'll have to pay income tax over it, as it's seen similar as "labor".
> In general
> In the case of a taxpayer’s specified research or experimental expenditures for any taxable year—
Note specified.
Then the special rule says
> For purposes of this section, any amount paid or incurred in connection with the development of any software shall be treated as a research or experimental expenditure.
So the section says its purpose is to govern specified R&E expenditure. And the special rule regarding software is caveated to make it clear that it is subject to the general purpose of the section.
To your analogy, if I pay an employee to build a machine rather than buy a machine, that’s opex not capex. I don't amortize the labor cost of the machine out over 5 years and pay taxes on the 80% of the employees salary that now doesn’t count as an expense because they made a machine. I also don't get to add the value of the machine as an asset and record losses as it depreciates over the years, either.
> For purposes of this section, the term "specified research or experimental expenditures" means, with respect to any taxable year, research or experimental expenditures which are paid or incurred by the taxpayer during such taxable year in connection with the taxpayer's trade or business.
So that's R&E expenditures. It's further specified that all swdev is R&E.
My interpretation would be that sw dev = R&E. And R&E = specified R&E, UNLESS it's not in connection to the trade or business. (Not sure when that would happen though).
Afaik, it works like that when activating any piece of IP using an expenses based valuation method.
I'm gonna let it rest now. I'm not affected anyway. At least not directly.
In the UK the relevant document is CIRD81900[0] which sets out what conditions must be satisfied to qualify for R&D tax relief. It's lengthy, but worth the read.
One section that stands out is:
"A process, material, device, product, service or source of knowledge does not become an advance in science or technology simply because science or technology is used in its creation"
[0] https://www.gov.uk/hmrc-internal-manuals/corporate-intangibl...
Disclaimer: Not an accountant, not your accountant, get professional advice.
[0] https://www.att.org.uk/tax-treatment-software-and-website-co...
Indeed. Although:
"If businesses develop their own software, the classification of expenditure relating to this (including salaries of in-house IT staff) should be assessed following the same principles. The fact that expenses such as salaries may be recurring does not on its own prevent them from being capital in nature. However, it should be noted that:
The salaries of IT staff will not normally be capital expenditure unless some major new project can be identified. If staff are making only piecemeal changes or minor improvements to software, their salaries are likely to be revenue costs."
Yet from the [US-based] contibutions in the thread it sounds as though _all_ in-house software developers' salaries may _have_ to be treated as capital expenditure for tax purposes in the US.
This seems, frankly, bonkers. I appreciate that portions of the US tax code might well be exactly that(!)
> For purposes of this section, any amount paid or incurred in connection with the development of any software shall be treated as a research or experimental expenditure.
I'm just "parroting" from house.gov
This section describes how to handle expenses you consider to honestly be research and experimental expenditure. It does not supersede all other sections of the tax code and magically cause all software expenses to get sucked under this section. It simply instructs you how to proceed when evaluating your R&E expenditure, of which software development unambiguously qualifies.
Why is it so hard to believe? The US has a credit problem. There's a ton of money going to software dev. It gives the government some easy access to capital. It's essentially a loan from tech companies
"For purposes of this section, any amount paid or incurred in connection with the development of any software shall be treated as a research or experimental expenditure."
PS: if the reply button doesn't show up click the timestamp (X minutes|hours ago) on the comment you’re wanting to reply to and you’ll get a reply option.
Was clarification given? If so, it would be rather strange to see these posts pop up on cnbc and other big sites, as it was already known and discussed some time ago.
I think that's up to the judicial branch to see if the new law/regulations are unconstitutional.
Whil I do agree it's messed up, but they're not really stealing, they're just borrowing from companies. Timing is pretty shitty though; a year or two ago, it would've made less of an impact, as capital was cheaper and easier to get.
That’s what is really fucked up as others are pointing out. If I don’t grow or grow slowly The gov’t is flat out robbing me. If I start a venture that I don’t expect will start generating revenue for 5 years, then the government has taken 5 * 1/5(sw-expenses)(tax-rate). Thats not a loan, it’s larceny.
You certainly have a choice to claim it as such or not.
More importantly, why TF has the government been paying software engineers salary all these years? That's the real question. Also, has it occurred to anyone that this may be why the big tech companies are laying off engineers in droves?
> The salaries of the team responsible for keeping the production instance of the software up and running should also be included in COGS. All other R&D expenses should not be in COGS.
https://www.saas-capital.com/blog-posts/what-should-be-inclu...
> Amortized software development costs (we discourage capitalizing these costs in the first place)
Emphasis mine. They're saying if you amortize your other software dev as R&E (stuff that isn't ops/infra/etc. and thus considered COGS) then it doesn't count towards your COGS. But then what they're pretty clearly saying in the parenthetical is that they don't recommend doing that in the first place, which implies that you have a choice.
My understanding is the problem is the phrase "any amount paid or incurred in connection with". It is unambiguous and provides no leeway. Any costs related to software development are R&D. Period.
Software development
For purposes of this section, any amount paid or incurred in connection with the development of any software shall be treated as a research or experimental expenditure.
https://www.law.cornell.edu/uscode/text/26/174To me it doesn't sound like classification is discretionary to me, or that splitting semantic hairs will prove effective (IANAL).
(Additionally, the R&E classification is different from R&D)
> In computing taxable income under section 63, there shall be allowed as deductions the items specified in this part,
Generally, these sections explaining deductions, including 174, are things you adopt. From the beginning of the section
> (a) In general
> In the case of a taxpayer’s specified research or experimental expenditures for any taxable year—
Everything that follows is subject your specified R&E. Which is all part of the itemized deductions framework which is all completely elective.
For instance, here’s section 162
> a) In general
> There shall be allowed as a deduction all the ordinary and necessary expenses paid or incurred during the taxable year in carrying on any trade or business, including—
> (1) a reasonable allowance for salaries or other compensation for personal services actually rendered;
You are simply carrying on business ordinarily. People don’t operate businesses on R&E expenditure. It’s just not a rational interpretation of the tax code and you don't even need to be a lawyer to read this document or form that conclusion.
https://news.bloombergtax.com/tax-insights-and-commentary/ch...
> Research or experimental expenditures paid or incurred in tax years beginning after December 31, 2021, must be charged to a separate specified research or experimental capital account and amortized ratably over a 5-year period ... The expenses cannot be deducted in full in the current year.
> Research or experimental expenditures, as used in section 174, are research and development costs ... you incur in connection with your trade or business [..] The costs related to developing software are treated as research and experimental expenditures.
Nothing contradicts this plain meaning. Rev Proc 2023-11 [5] just reiterates that yes, all software development is included in R&E expenses:
> 2.02 (5) Section 174(c)(3) provides that for purposes of § 174, any amount paid or incurred in connection with the development of any software is treated as a research or experimental expenditure accounted for under the required § 174 method.
And yes, no deduction is allowed:
> 2.02 (1) As amended by § 13206(a) of the TCJA, § 174(a)(1) provides that in the case of a taxpayer’s specified research or experimental expenditures for any taxable year, except as provided in § 174(a)(2), no deduction is allowed for such expenditures.
The sad part is that it's not even that much money. The Joint Committee estimates [4] that it will gain about 12 billion per year on average, but most of that is front-loaded into TY22 and 23. So they force larger companies like Google to hand over their cash so they can collect the float on it or whatever, and they don't care it will fuck over all these startups. They probably modeled it in.
[1] https://www.law.cornell.edu/uscode/text/26/174 [2] https://www.jct.gov/publications/2018/jcs-1-18/ [3] https://www.irs.gov/publications/p535 [4] https://www.jct.gov/publications/2017/jcx-67-17/ [5] https://www.irs.gov/pub/irs-drop/rp-23-11.pdf
1,000,000 Revenue
- 1,000,000 Salary expense
-----------
0 Profit
We are talking about an extremely lucky company if it's the first year. How many startups are able to get revenue equal to salary expenses in the first year? While they might exists, it's not very common. For all others and if it's not the first year you already have losses carried forward which will offset those 800,000 (since you didn't amortize them in the previous years, right?), so in your example if it's the first year you get any revenue you would have (years since founding) * $1,000,000 in losses. What do I miss here?1. Your landlord decides that you needs to pay 5 years rent in advance. Each year you have paid off one year, however you need to pay another year to keep up. When you leave, the landlord will pay you back 1 year rent every year for 4 years. [landlord == government]
2. You develop an exact Facebook clone. The business tanks. How much was the software worth? Facebook’s value is only minimally in the software itself. Facebooks value is mostly in daily user eyeballs and advertising contracts and network effects.
3. You get some VC funding and spend 5 years developing software. You start making a profit, so you can claim the prior losses. However, the losses are not inflation adjusted (nor risk adjusted, nor discount adjusted). Your taxes are not adjusted for inflation.
4. You sell your business. Now you need to decide on the a valuation of the software, since it affects taxable income in the future. Leads to valuation games that have no benefit to anyone.
5. You go bankrupt - software valued at zero. Now do you need to claim those R&E taxes back from the IRS? Does that cause a lump in your personal income that puts you into a higher tax bracket?
I understand the rest and I'm not saying it's a good law. It's just not as bad as in the example with $1,000,000 above as IMO most companies won't be in that position, especially newly founded startups. The worst part is that it happens without a ramp up and with high interest rates.
I much prefer Estonia's system of taxation. Flat 20% on share dividends. Any money that stays within the business (or gets spent on wages, other expenses) isn't taxed (aside: there are social and income taxes on wages).
Coming from Australia's system it's just so simple to be compliant. Feels designed to help businesses grow.
So my salary is taxed; my dividends are taxed; my purchases are taxed with VAT, that sort of thing.
Stop making companies employ armies of accountants to figure out all the tax credits/implications/corporate structures etc so the government doesn't take too much.
However, the rule isn't that the firm can only ever expense 1/5th of the expense, but that they expense 1/5th for 5 years. Assuming steady expenses, they'll be expensing 100% in year 5.
Year One:
0 Revenue
-200,000 Salary expense A: 1/5
----------
-200,000 Profit (loss)
Year Two:
250,000 Revenue
-200,000 Salary expense A: 2/5
-200,000 Salary expense B: 1/5
----------
-150,000 Profit (loss)
Year Three:
500,000 Revenue
-200,000 Salary expense A: 3/5
-200,000 Salary expense B: 2/5
-200,000 Salary expense C: 1/5
----------
-100,000 Profit (loss)
Year Four:
1,000,000 Revenue
-200,000 Salary expense A: 4/5
-200,000 Salary expense B: 3/5
-200,000 Salary expense C: 2/5
-200,000 Salary expense D: 1/5
----------
200,000 Profit
Year Five:
2,000,000 Revenue
-200,000 Salary expense A: 5/5
-200,000 Salary expense B: 4/5
-200,000 Salary expense C: 3/5
-200,000 Salary expense D: 2/5
-200,000 Salary expense E: 1/5
----------
1,000,000 ProfitOTOH, I'm not a biz guy but I was under the impression that paying employees was an expense anyway and would be deducted from revenue and not taxed. How is R&D different?
No. The terminology is confusing. Section 174, specifically point 3, classifies software development as R&E as of 2022 and requires amortization over 5-15 years. This prevents software engineering salaries as a standard business tax deduction. This has nothing to do with the R&D tax credit (section 41).
No, it is not.
OK, so what is it?
So stop claiming software development as R&E and just say they're regular salaried employees. The government never should have been paying them in the first place!
https://www.grantthornton.com/insights/alerts/tax/2022/flash...
Previously if a company has a million dollars in revenue and spends a million dollars on the salaries of software developers, this is how their taxable income might look:
The new law would instead work like this: Now the company must pay taxes on 800,000 of profit because "R&D salaries," which includes software devs, must be amortized over five years. Obviously the company has no wherewithal to pay, given that they made a million and spent a million. That's the problem.