Saying you want to learn when all question posed have clearly been answered multiple times shows a clear disconnect between what you're saying you want to do, and what you actually want to do.
You're still displaying a fundamental lack of understanding about most things here. You're trying to explain MSAA and using that as an obscure argument that in some cases an estimated pixel is blurring, and in others it's not. This makes no sense - blurring occurs when you have an approximation of a set of pixels, rather than the actual pixels. An approximation of 4 pixels downscaled to 1, is still an approximation, as is 1 pixel upscaled into 4 approximated pixels. Have a look at the font example here:
http://www.geforce.co.uk/whats...
What do you think those intermediate pixels between the black and the white when anti-aliased are if not a literal blurring of the lines to make a jagged edge look smoother?
You're reaching for a single very specific algorithm, and using very arbitrary (and hypocritical) definitions to try and argue your point. This tells me that you've already decided what's what, which again shows what a farce your claim to want to learn is- if you've already decided you know best (whilst admitting you're wholly unqualified on the subject) then why are you pretending you care? why are you even discussing? don't say you're doing so because you want to learn whilst simultaneously proving that you do not.
You're arguing as someone whose taken their knowledge from a "my graphics card is better than your graphics card" type website or forum discussion with maybe a bit of Googling thrown in to try and mask the most embarrassing elements of your lack of knowledge. What you're not showing is an understanding of the visual impact these algorithms and techniques have on a finalised scene and it's that that makes it clear that you're out of your depth.
If you want to lecture on discussion etiquette whilst complaining about not getting detailed answers - consider this, don't enter a discussion posting in a manner where it's clear you're looking for a fight, continue on with "I've no idea about any of this but here's a logical fallacy" and then persist with "I want to learn but I can't be arsed to think so you're wrong". I don't owe you anything, much less am I willing to put any effort into providing more detailed an in depth explanations with examples when you act like an ass from the very outset and persist through the duration.
You strike me as someone that could actually get into this in a bit more detail and could, if you wanted to, learn to write your own rendering engine. But before you do that you need to sort your attitude out and actually want to learn rather than pretend to want to learn but actually just be looking for a fight. You're so nearly there, you recognise that learning is important, and that wanting to learn is important, but you've not quite crossed the line yet where you're willing to put self-pride aside to actually do it.
If you're not going to do that and finally cross that line you may want to consider that there's a reason you're the sort of person that ended up working in a fast food joint as you mentioned in another post. It's your choice, but I think you probably do have the potential to actually get into this stuff properly and actually do it, rather than skirt about on the edges with half-arsed third hand knowledge learnt from the second hand knowledge of some bottom of the rung gaming website faux-journalist.
If you want to do that I can tell you exactly what you need to do to get going, and how to avoid or deal with the inevitable roadblocks that learning this stuff creates because whilst being a game developer is easy, being a graphics developer isn't - anyone can chuck something together with Unity, Unreal Engine and so forth, but far fewer people can write those engines in the first place. Don't look upto game developers as rockstars, they're not. The days where every development house is building it's own engine and has it's own engine development team are long gone. Most are little more than glorified mod teams nowadays using pre-built engines- if you want to be a game developer you can be one. If you want to be an engine developer? that's going to take a lot more work, but either way you sound like your worship the profession and what it does, and if so then why aren't you aspiring to it? it's within your reach.
Ultimately it depends how much you really care. But don't pretend you want to learn if you actually just want to always be right, even when you're not. I'm not asking you to listen to me, if you're still skeptical of the idea that an upscale can still create a sharper scene than a lower resolution non-upscaled scene, that blurring is sometimes a good thing and so on and so forth then that's your prerogative, but rather than telling me I haven't explained something when I have and just assuming I'm wrong, or bad at teaching just accept that maybe you've got a bit more learning to do first and go learn or experiment, or figure it out yourself from another source.