Skip to main content

What would happen in a perfectly competitive market for apples in the short-run to the market and to individual producers if the price for pears...

If the price of pears goes up, the demand for apples will rise.  This will mean that the market for apples will see an increase in price and an increase in quantity demanded.  The individual farmer will see an increase in price.


This answer assumes that many people will see pears and apples as substitute goods.  That is, people are more or less willing to buy either pears or apples, depending on the price.  If the price of pears goes up, people will, ceteris paribus, buy more apples.  They will buy fewer pears because of the price increase and will go buy apples instead.


In perfect competition, the entire market faces a demand curve that has a negative slope.  When the price of pears goes up, the demand for apples rises.  The market demand curve retains its negative slope, but moves to the right.  This means that, ceteris paribus, the price of apples rises as does the quantity demanded.


In perfect competition, the individual producer does not face a sloped demand curve. Instead, the individual producer’s demand curve is perfectly horizontal.  The producer can sell as much as they can produce at the market price.  When the market price changes, the individual producer can sell at the new, higher market price.  However, because their demand curve is flat, they do not get to sell any more than they could before.  Even before, they could sell as much as they wanted.  This has not changed.


Thus, an increase in the price of pears will lead to an increase in the market price and market quantity demanded of apples.  Individual producers will see an increase in price but not in quantity demanded.  Please follow the link below and scroll down to “Section 02: Pure Competition in the Short Run” to find graphs that show these changes.

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