Skip to main content

From 1781 to 1789, did the Articles of Confederation provide the United States with an effective government?

I would say the Articles of Confederation provided the United States with a government that was effective enough to keep the country functioning in the short term, but not one that was effective enough to last in the long term.


In the time from 1781 to 1789, it was not clear that the United States would be able to stay together.  The country was made up of thirteen different states that did not necessarily feel as if they were connected to one another.  The Articles of Confederation created a government that the various states could accept.  This kept the country together, which was very important.


In addition, the government was effective enough to take care of at least one important issue.  It was able to bring about a consensus on the issue of the Northwest Territory.  The various states were in conflict with one another as to who should control this area.  The government was effective enough to create the Northwest Ordinance, which settled the issue of the territory and allowed the states to stay together.


However, the government that the Articles created was not effective in the long term.  The Articles created a national government that was too weak to keep the country united.  The Articles allowed the various states to do things like engaging in trade wars against one another.  The Articles did not give the national government enough power to require the states to do anything, including basic things like funding a military.  Because the Articles did not do these things, they created a country that was not strong enough to last in the long term.  The Articles created a government that was effective enough in the short term, but not effective for the long term.

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...

What warning does Chuchundra issue to Rikki?

Chuchundra, the sniveling, fearful muskrat who creeps around walls because he is too terrified to go into the center of a room, meets Rikki in the middle of the night. He insults Rikki by begging him not to kill him. He then insults him by suggesting that Nag might mistake Chuchundra for Rikki. He says, "Those who kill snakes get killed by snakes."  He issues this warning to Rikki not to help keep Rikki safe but as a way of explaining why Rikki's presence gives him, Chuchundra, more reason to fear.  Chuchundra starts to tell Rikki what Chua the rat told him--but breaks it off when he realizes he might be overheard by Nag. He says, "Nag is everywhere, Rikki-Tikki." Rikki threatens to bite Chuchundra to get him to talk. Even then, Chuchundra won't overtly reveal any information. But he does say, "Can't you hear, Rikki-Tikki?" This is enough of a clue for the clever mongoose. He listens carefully and can just make out the "faintest scratch-s...