hckrnws

Lol. The website has some wonderful info:

What about security?

If you can't trust public visitors from the internet, who can you trust? Executing user input as commands inside the operating system is the most direct way to get things done, and that's what matters most.

Does it scale?

So far I haven't run into any performance problems. Whenever I've opened up a DoD website to several users, my hard drive tends to get wiped long before I discover performance issues.

https://secretgeek.net/dod_intro is a better link on this. Also (2010)

The author of this appears to be afflicted with the common confusion that the Windows CLI environment (console subsystem, CMD.EXE, etc) is “DOS”.

When I saw that some of the glue code is in C#, I was momentarily excited to learn more about compiling C# to be able to run on DOS.

That's a thing, too: https://hackaday.com/2020/02/09/c-the-language-for-all-platf...

Because Does on Dope is catchier than CMD.exe on Coke?

Or, keeping with the RoR theme, "The Trainwreck also known as CMD.exe off the Rails" (TTakaCotR)?

CMD.exe on coke is pretty dope ngl

Play Commander Coke against the aliens

Bingo

Or posh on poke I guess.

It makes sense considering that in non-NT Windows, it was a full DOS virtual machine, and while NT's cmd.exe is not DOS, 32-bit versions could still run DOS apps via NTVDM (also a virtual machine).

He sure knows better, and tbh, today this is the apparent ""relict"" remaining from the MS-DOS times so it can be well called like this for a project title, but thanks for the nitpick!

Even without opening the command prompt, the mere presence of drive letters are a particularly embarrassing relict from MS-DOS.

Holding out for GEM on GHB

Batch scripts are really bad for web dev. IFL your company would go broke if they used this.

It's a joke. Don't overthink it.

Definitely still better than code I've seen in production.