I was digging around the internet, and I stumbled across a page for something called "Command Shell for Windows".

Alternate Windows shells are now a thing of the past, originally made for Windows 2 and Windows 3. Microsoft forbade OEMs from preloading shells on their systems with the release of 95. And no one cared because the Explorer was all they needed. And they're right.

It is now 2013. The command line (except in the case of Linux) is long dead. Windows 9x was shot down in the early 2000s. No one cares about DOS, despite it still existing in Windows to this day. In fact, try asking a young kid what DOS is. They probably don't even know.
However, apparently a few people (probably also those who support Windows 8 as it works on the same principles) still like the command line.

Cue GCT Enterprises, and their new (yes, that's right, NEW for 2013) Windows shell, Command Shell for Windows. It is made for Vista and 7, reportedly it runs on XP as well. It would be perfect for Windows 8, however I have no machine to test it on, nor is it recommended (why?).
Apparently they are working on a version for Linux as well, but I don't know how valid that claim is

Took some digging to find a working copy, but here it is for your viewing pleasure!

This is the installer. All it is, is a batch-file that copies crap into a folder. Simple enough, get's the job done.

It's supposed to restart your computer automatically, but fails miserably to do this. Pretty pathetic when you can't even code your own batch files correctly. And this is a company making this!

This is the main screen.

As you can see, Command Shell is exactly what it says it is. A command-line shell that starts up with Windows.
Disappointingly it does not replace the desktop entirely. However it does run in a maximized window.

Something like this, as I've said, would be perfect for Windows 8 since Windows 8 requires users to memorize many keyboard commands. Just like the command line.

Adding a program is done entirely manually. You must know the directory the program installed to, and you must know the executable name.
Straightforward for someone who knows what they're doing, unfortunately much of today's modern folk would look at this and be completely dumbfounded.

Should you mistype anything, it rejects the input and asks again.
It is also pretty picky. The end of the directory CANNOT contain a \ character and the exe name MUST contain .exe, or it will fail to find the file and you have to start again.

Adding a program without having installed it first adds another layer of complexity as you must make note of the directory you installed the program to, and then use that to find the executable name.
It is really easy to mistakenly add the wrong executable and then have the program not work or worse.

Ironically this complexity would be great for the young kids these days (my generation and those to come), but they won't touch it because "it's too hard to use".