Skip to main content

How did militarism in Italy and Japan cause the Second World War?

Militarism is often a cause of wars and it certainly did help to bring about WWII.  Militarism can be defined in two parts.  First, it is the belief that a country should have a large military and should aggressively use that military to pursue its interests.  Second, it is the belief that the military is somehow superior to civilians, which leads to the military being respected excessively and even glorified.  Militarism was clearly present in all of the Axis powers, helping to bring about WWII.


In Japan, militarism drove Japanese foreign policy.  The military dominated the government and pushed hard for foreign expansion.  For example, it was the military that forced the government to invade China, not the other way around.  It was the military that pushed for the Pearl Harbor attack.  No other institution in society had anywhere near the prestige that the military had, which made it easy for the military to get its way.  Thus, militarism drove Japan to take aggressive actions that helped cause WWII.


In Italy, militarism was part of Mussolini’s drive to make Italy great again.  He wanted to increase Italy’s military strength to make it a major power in Europe.  A major step that Mussolini took due to militarism was his invasion of Ethiopia in 1935.  This did not lead directly to WWII in the way that Japanese militarism did, but it weakened the League of Nations and emboldened Germany.  Because Italy could get away with invading weaker countries, the Nazis felt it was more likely that they could use their own military power to get what they wanted as well.


Militarism often leads to wars because militarism encourages countries to use military force to get what they want.  Germany, Japan, and Italy all did this, causing WWII to begin.

Comments

Popular posts from this blog

Is there a word/phrase for "unperformant"?

As a software engineer, I need to sometimes describe a piece of code as something that lacks performance or was not written with performance in mind. Example: This kind of coding style leads to unmaintainable and unperformant code. Based on my Google searches, this isn't a real word. What is the correct way to describe this? EDIT My usage of "performance" here is in regard to speed and efficiency. For example, the better the performance of code the faster the application runs. My question and example target the negative definition, which is in reference to preventing inefficient coding practices. Answer This kind of coding style leads to unmaintainable and unperformant code. In my opinion, reads more easily as: This coding style leads to unmaintainable and poorly performing code. The key to well-written documentation and reports lies in ease of understanding. Adding poorly understood words such as performant decreases that ease. In addressing the use of such a poorly ...

A man has a garden measuring 84 meters by 56 meters. He divides it into the minimum number of square plots. What is the length of the square plots?

We wish to divide this man's garden into the minimum number of square plots possible. A square has all four sides with the same length.Our garden is a rectangle, so the answer is clearly not 1 square plot. If we choose the wrong length for our squares, we may end up with missing holes or we may not be able to fit our squares inside the garden. So we have 84 meters in one direction and 56 meters in the other direction. When we start dividing the garden in square plots, we are "filling" those lengths in their respective directions. At each direction, there must be an integer number of squares (otherwise, we get holes or we leave the garden), so that all the square plots fill up the garden nicely. Thus, our job here is to find the greatest common divisor of 84 and 56. For this, we prime factor both of them: `56 = 2*2*2*7` `84 = 2*2*3*7` We can see that the prime factors and multiplicities in common are `2*2*7 = 28` . This is the desired length of the square plots. If you wi...