For many things, it's much quicker to fire up a test program running under an instance of DosBox than it is to re-assemble something, put it into a disk-image and then fire up Bochs, VirtualBox or the other virtual machine of ones choice.
You still get bare-bones access and the option of a much nicer debugger than a full virtual machine offers. Naturally, debugging boot-loaders and real-mode -> protected mode switches gets a little more interesting, but DOS is still a great test environment for some stuff.
Government can give you nothing but what it takes from somebody else. A government big enough to give you everything you want is big enough to take everything you've got, including your freedom.-Ezra Taft Benson
You must accept 1 of 2 basic premises: Either we are alone in the universe or we are not alone. Either way, the implications are staggering!-Wernher von Braun
MacOS - iOS/Swift/Xamarin
Ubuntu - ASP.NET Core/Xamarin/Bash
Windows - ASP.NET/SQL
Ah, I see you have the machine that goes ping. This is my favorite. You see we lease it back from the company we sold it to and that way it comes under the monthly current budget and not the capital account.
I have a VM that boots MS-DOS 6.22. My 'development environment' is Microsoft C 6.0.
I use it to build an app that controls a fluid system in one of our commercial ink-jet printing systems. The app started out running on an industrial PC in a rack cabinet 20 years ago. Now it runs on a little board the size of a credit card, mounted inside the fluid system cabinet.
Well that's quite well justified then, but you could probably even use VS Code as 'dev environment' on Windows and just compile and test on the DOS vm. VS Code can easily be customised to do that all on its own.
It's even quite sad that people are still using the Windows Command Prompt when PowerShell 2.0 was already around in 2008, nine years ago. 2.0 was really the first practically useful version after a very experimental 1.8 as far back as 2006. PowerShell 5.0, extremely highly evolved, has already been out for one year today, Feb 14.
I was always jealous of the *nix scripting shells that were powers of magnitude more powerful that the old command prompt, with hardly any programmability, but now PowerShell 5.0 makes all of those *nix shells look a Fischer-Price product compared to .NET framework object oriented scripting.
And now that PowerShell is available on all common platforms, we're bound to see lots of awakenings in the non-Windows world.
I still use the command prompt every single day and it is a part of my development. Although if I need to script I do that in linux via PuTTY to one of our linux servers or on a locally using a cygwin terminal.
I have at least two PS windows open all day for dev purposes, and about once a month open a legacy command prompt because I'm too rushed or too lazy to find out how to achieve a certain "DOS" command in PS.
t's even quite sad that people are still using the ...
I only say... VB6 and IE8
If something has a solution... Why do we have to worry about?. If it has no solution... For what reason do we have to worry about?
Help me to understand what I'm saying, and I'll explain it better to you
Rating helpful answers is nice, but saying thanks can be even nicer.