The tenacity of Doom players to make the game run on everything is amazing
It’s not just about being DOOM players. It’s a long running joke in the programming and engineering world. Wether it’s a fridge, a toaster, a decommissioned 1970s super computer… can it run DOOM?
It’s the computing world’s version of a shitpost.
The main reasons why it’s Doom specifically are also because:
-
The game is open-source: https://github.com/id-Software/DOOM/pulls?q=is%3Aopen+is%3Apr This makes it much more doable to port it to other platforms (and to strip out anything not absolutely required to get the first level to run when you run into technological limitations) than when you have to rely on unofficial modding tools.
-
It’s nearly 30 years old and designed for computers with only a few megabytes of memory and for processors of well under 100MHz, which are specs which the majority of modern systems have, even embedded systems. It also renders fully on the CPU and doesn’t require specific hardware like a GPU or a specific graphics chip.
-
Being a first person shooter with 3D-ish visuals it looks a lot more impressive than if you show off a simple game like Pong orTetris or something like that. It has the right balance between performance requirements and impressiveness, and it’s also a game that was very popular in its time and it’s instantly recognisable to a lot of people.
-
But can it run Crysis?
Heretic
That’s a different game. Built on a modified Doom engine.
Your scientists were so preoccupied with whether or not they could, they didn’t stop to think if they should.
I really want to see someone get Doom running in Emacs. I’ve tried to figure out if anyone has but of course what actually comes up is “Doom Emacs” which is a specifically customized version of it.
I am pretty sure that your goal qualifies as evil chaotic. Not because the game is evil, but because the platform is Emacs. I mean, everyone knows it’s Vim.
Emacs literally calls it’s Vim emulation Evil mode :)
In all seriousness though, I say Emacs mostly because being a Lisp machine, it’s turing-complete. There’s web browsers in Emacs, PDF readers, email clients, EXWM is literally Emacs as your window manager.
Also what I’ve realized recently is… Vim keybindings aren’t even that great beyond being modal, anyways. Some dude made an Emacs plugin called Xah-Fly-Keys that makes it modal, but works off of what commands are used often rather than how Vim does stuff like making the “go to the end of the line” key $ for some reason. With Emacs being something you can sort of just live in, I can bring my workflow into it rather than praying that what I’m using has vim key support.(Fuck I’m participating in the editor wars, fuck my life)
I’m ignorant, but what does this means? I mean, what’s the difference running it “in the kernel” and running it normally on windows?
It means that all the code is running in privileged kernel mode instead of user mode. Kernel mode is usually reserved for the operating system and device drivers only. If code running in kernel mode has an unhandled exception or error, the entire system will crash. This creates the BSOD or “blue screen of death” on Windows.
User mode is less privileged and where all your typical applications run. If something crashes in user mode, it only crashes that process, not the whole system.
It’s a crazy thing that they did. Very impressive technically, but not really useful.
Forgive me if this is a stupid question but why is it technically impressive? Is it not just the same as running it in usermode but with higher privileges?
The API is much more limited for kernel mode, because Microsoft doesn’t want to make it easy to crash the kernel. So it’s not just a matter of taking old DOS code and making Windows run it in an old compatibility layer, but actually requires translating the whole thing into a much more limited set of commands to properly draw the graphics and respond to user input.
It’s impressive like being able to play the French horn without using the valves, or painting beautiful pictures using only a mechanical typewriter. It’s being able to do something that is trivially easy with normal tools, but with such a limited toolset that the accomplishment itself is impressive.
