By John Q. Hosedrinker 
House Speaker Mike Johnson stated that the United States is not currently at war with Iran, despite President Donald Trump and Defense Secretary Pete Hegseth having described the U.S. operations as such. Johnson characterized the recent strikes as a specific, clear mission rather than an act of war, asserting that Iran had initiated hostilities. He expressed confidence that the House would reject a War Powers Act resolution, arguing its passage would jeopardize U.S. forces and hinder mission objectives.
Read the original article here
House Speaker Mike Johnson’s assertion that “we’re not at war right now” has landed with a thud, particularly in the wake of Donald Trump’s forceful rhetoric regarding Iran. This statement, intended to clarify the current status of U.S. military engagement, appears to have fallen flat for many, who feel it clashes directly with ongoing actions and public pronouncements from prominent figures. The disconnect between Johnson’s official stance and what some perceive as a de facto state of conflict is stark, highlighting a broader debate about the definition of war in the modern era.
The argument that the U.S. is not officially at war hinges on a technicality: Congress has not formally declared war. However, this legalistic distinction seems to be lost on those who point to tangible military actions. When the U.S. is engaged in naval combat, conducting bombing campaigns, and responding to provocations that could reasonably be interpreted as acts of aggression, the label of “war” feels intuitively accurate, regardless of congressional authorization. It raises questions about whether the formal definition of war adequately captures the reality of contemporary military engagements.
Moreover, the discourse surrounding these events is further complicated by differing interpretations. While Speaker Johnson emphasizes the lack of a formal declaration, others, including former President Trump and commentators like David Hegseth, have been more explicit in framing the situation as a conflict, even a war. This divergence in language creates a confusing narrative for the public, making it difficult to ascertain the true nature and scale of U.S. involvement. The very act of denying being at war while simultaneously engaging in significant military operations leads some to believe that official statements are merely attempts at obfuscation.
The historical context of U.S. military intervention adds another layer to this discussion. It’s often pointed out that the United States has a long history of engaging in military actions abroad, with relatively few periods of complete peace. This historical pattern suggests a tendency to become involved in conflicts without always resorting to formal declarations of war. The current situation, therefore, might be seen not as an anomaly, but as a continuation of a long-standing practice, albeit with evolving justifications and terminology.
Critics argue that the current administration, and indeed many before it, has become adept at using euphemisms to downplay military involvement. Terms like “security action,” “targeting bombing campaigns,” or “major military operation” are employed to avoid the loaded implications of the word “war.” This linguistic strategy, some believe, is designed to circumvent public scrutiny and congressional oversight, allowing for military action without the political ramifications of a formal declaration of war. The Sri Lankan naval incident, cited as an example of unintended consequences and environmental damage, further fuels the argument that military actions, even if not formally declared wars, carry significant real-world implications.
The perception that these actions are being undertaken to appease specific political figures, such as Donald Trump, or to distract from domestic issues, like the Epstein files, also contributes to the skepticism surrounding official statements. When political motivations are perceived to be driving military decisions, the credibility of pronouncements about the absence of war is significantly diminished. The idea that Iran has declared war on the United States, as suggested by Johnson, only adds to the contradiction, as being declared war upon by another nation would inherently imply that a state of war exists.
Ultimately, the debate boils down to how one defines “war” in the 21st century. If it requires a formal declaration by Congress, then Johnson’s statement holds a certain technical validity. However, if “war” is understood as any significant, sustained, and potentially lethal engagement between nations, then the ongoing military operations against Iran, regardless of their formal designation, certainly seem to fit the bill. The persistent use of language that attempts to distance current actions from the concept of war leaves many feeling that they are being asked to disregard their own senses and the evident reality of ongoing conflict.