WP can multitask and we know that. All MS native apps can multitask otherwise we will not be able to listen to music while surfing on the browser. But when comes to 3rd party apps, things are totally differently!! Most they can do is updating the respective tiles in the background and nothing else...
Seriously, you have no idea what you are talking about. Every single point you made in the post I quoted from is incorrect. I just don't understand how you (and one or two others) can essentially make up a problem, and then start pointing fingers and placing blame, particularly when those points are so easily disproven... no skills or developer knowledge required.
A)
That MS' own apps can play music in the background while 3rd party apps can't is BS. Download pretty much any music app from the store to prove yourself wrong. It's astounding that you think live tiles are the only background capability WP has..
B)
I doubt multiple developers told you that it's impossible to download files in the background due to an OS limitation. If they did then they were just not interested in providing the feature you requested, and wanted to shut you up, by sending you off to complain about MS and WP rather than their own app. It's more likely that you just didn't understand what they were saying however.
Either way, I already provided an example of a 3rd party app that CAN download files in the background. Download UC Browser and easily prove yourself wrong again, but no...
C)
All your other opinions are derived from your incorrect understanding of the above.
Conclusion:
At this point, continuing to complain about multitasking on WP, a topic you've shown to have no understanding of, just makes you look silly.
WP obviously has problems in the multitasking department, but with few exceptions (no, the feature-based multitasking on WP is not perfect) they are not a consequence of OS limitations.
We all know that WP has an app quality and feature gap, but as soon as "multitasking" is thrown into the debate, developers have no responsibilities and it's all WP's fault... somehow, on this specific issue, a sizable portion of the WP community is still stuck in 2011 and using WP7.