Folder naming errors- But Why? | But Why?

dot_tom

OK. System.Exception is not abstract. Why?

exoteric
I : Next<I>

I don't think this is targetted at programmers as such, more like end-users of Windows and maybe Office. Laura, clarification? Smiley

(Having System.Exception not be abstract sounds kind of handy, if anti-FX cop - but why not an interface instead - well, may make catch block behavior a bit "interesting" due to multiple inheritance.)

dneomatrix

Interesting and short video, but I was craving a little more in depth information... Maybe it's just me.

Laura10

In reply to exoteric

#Sep 30th @ 9:59 AM

This particular episode isn't targetted at programmers but there will be tons of these- we will definitely hit a few for programmers specifically in the future! Thanks Smiley

Zeo
Channel 9 :)

I'm digging this new content. Keep it coming...I may just have to visit channel9 more often...(is that even possible?)

Minh
WOOH! WOOH!

In reply to dot_tom

#Sep 30th @ 9:01 AM

no audio in Silverlight 3...

I can play the "Dare to Dream" video just fine

Charles
Welcome Change

But why are we still maintaining MS-DOS era naming restrictions when MS-DOS has not been a part of at least 3 iterations of Windows (beginning with Windows 2000, I believe, so now 4 iterations....)?

C

wkempf

In reply to Charles

#Sep 30th @ 10:53 AM

These are "device" names, and they are still in use even if DOS has been erradicated. Use CMD to test for yourself. Now, we can ask why Windows doesn't evolve into a more POSIX like scheme here (/dev/null and other such pseudo files), but that's a much more complicated discussion.

ChrisStepaniuk

In reply to Charles

#Sep 30th @ 10:53 AM

I'm sure there are many oddities in Windows which would garner the same response, "but why" from most people. LPT1 is the most humorous example. How many of us have parallell printers anymore? They might be an obsecure one here and there, but for the most part, it's all USB.

What amazes me more is that people get frustrated that you can't use "?" in a file name. I'm sure there is also a perfectly good explaniation.

The one thing I always wondered was why MFC has the prefix AFX (I know the answer, but why?) and why Word has the executable name "winword.exe" and Excel has the executable "EXCEL", there really isn't any consistency there.

Thanks Laura for the factiod Smiley

Cheers!