Different use cases than QEMU, honestly, to the point that there's not much overlap. QEMU is extremely good at running modern operating systems, and not so much at older ones (DOS and Win9x are pretty sore points in QEMU). 86Box is extremely good at running old operating systems (including DOS and Win9x!), but modern operating systems are mostly out of the question (you can run WinXP, but https://86box.readthedocs.io/en/latest/usage/faq.html#can-i-...).
The simulators for running old operating systems must simulate correctly the entire IBM PC, with all its peripherals, not only the CPU.
QEMU simulates some peripherals, e.g. a certain video card, for which it hopes that any operating system that you install includes device drivers. This assumption is no longer true for very old operating systems, which may either lack device drivers or their device drivers may rely on some hardware behavior of the peripherals that is not implemented in QEMU.
Simulators like 86Box simulate an IBM PC clone at a much greater detail, but that is paid by being much slower, so they are not suitable for recent operating systems, which need faster CPUs.
Funny part is, that NFSv4 supports SIDs for user authentication, but the Linux implementation leaves it out (among all the other ACL features) simply on the basis that Linux doesn't support them at all.
The FreeBSD, Solaris, Mac OS X, and Windows (yes, even Windows) implementations of NFSv4 are fully featured with this stuff.
I considered Fossil several years ago and while it's really cool (everything being integrated is awesome), I don't like Fossil from a philosophical perspective. There's no way to clean up history, it preserves everything as is. If that's what you want, great, but as part of my git workflow I like to mess around and then go back and clean up and organize my commits before pushing them.
I love fossil. Something about it's opinionated workflow that matches what I think. But
network effects. I just can not bring my team to use fossil. They have to share code with others. Other departments. And everyone (99%+) uses git. It just feels like a disservice to force them to use fossil. It is a catch-22.
It is similar to so many other things in the tech space. Trying to get fellow developers to use functional style idioms. Trying to enforce immutability. It is like something big (like a facebook or google project) has to force the community to get on board.
It was actually part of Microsoft Plus! for Windows 95. It wasn't directly available for Windows 98 at all, but the Windows 98 install disc does include an INF file so you can install it, provided you have a copy of Plus! for Windows 95.
It was also included with Windows NT 4.0, Windows 2000, Windows Me, and Windows XP (both the original and x64 versions). Finally removed in Vista to never return.
Raymond Chen has two blog posts that first describes why Space Cadet was removed because of a 64-bit rounding mode bug and then a follow-up post a decade later clarifying that that might not be the full story.
Delphi and Lazarus are still kicking, the latter is free and open source.
I know you asked for "the language", but Object Pascal really ain't that bad to get around. If you were proficient in VB6, you should be fine adapting. :-)
reply