The funny thing is, I saw this title and though, maybe I should just write a blog post stating how I think of these words, because I find myself always linking to my HN comments defining them. It's a nice surprise when someone beats me to it.
I never look at MSDN links because they always use video. Video is a medium for toddlers. I see the title and I'm like "oh, neat, new GC in CLR 4.5 . . . oh video, pass." Give me a transcript I can skim through.
IMHO, Channel9.msdn is the best source of videos out there for developers. I've spent many an hour watching videos on there. My favourite are the C++ ones by this guy:
Concurrency is a property of the problem - no dependencies between tasks. Parallelism is a solution which uses that property.
This definition doesn't require (erroneous) distinctions between single and multicore systems. If I use a single core system to emulate a multicore system complete with emulated clock cycles and what not, are the emulated programs running concurrently or in parallel? From which point of view? The definition shouldn't dictate an implementation.
Edit: I miss-read, I read it as a question and a statement that it didn't work and as a request for a direct video link that you can wget. I'll keep the links here for anyone that might want them.
I must have miss-read, or was the original edited? Reading it again now it's clear that the person means "Wow this works without hoping through 15 things. I'll leave my links for anyone else that might be interested.
