Given that this article is 6 years old, and the upcoming vNext is being touted as practically a rewritten v1.0 product... will this constraint still hold for the new ASP.NET coming next year?
Microsoft fixed this awhile ago; the constraint definitely is dead in vNext. You do, however, still need to set a flag explicitly to disable the behavior described in this post. http://haacked.com/archive/2010/04/29/allowing-reserved-file... has instructions on how this worked in ASP.NET 4, and I believe the situation is similar in 5.
Also, just to get this out of the way since it comes up every time this is posted, my description of CP/M is slightly incorrect; it turns out to have had a much saner COM/LPT/etc. situation than DOS had. The rest of the article was however correct.
Because the article is six years old and the fact you can now circumvent the error is irrelevant to its point. Besides, the linked SO question does indeed have the new information, and has for five years.
So? Readers of that post obviously are interested in whether it was ever fixed, as this HN discussion proves, and they aren't going to randomly click on a SO link just in case it might cover that topic.
