News for hackers. Stuff that matters.
Re:Why FastDoom Is Fast by fabiensanglard on Tuesday March 04, 2025 @05:55PM (#43260648)
What tools did you have in 1993? From what I understood, id Software used NeXT because the tooling was not up to the task.
Re:Why FastDoom Is Fast by qingcharles on Tuesday March 04, 2025 @06:41PM (#43260951)
Yikes. Now you're pushing my memory. I believe there was a profiler built into Visual Studio and we had some external tool, too. We had some sort of system set up with serial cable to debug and profile. The EXE would download onto our test PC next to us.

Problem for id is that you have no sane way of profiling the DOS port on NeXT.

Re:Why FastDoom Is Fast by fabiensanglard on Tuesday March 04, 2025 @06:47PM (#43260991)
Visual Studio? The first released Visual Studio (Boston) was released in 1997. Doom was developed during 1993 :P !
Re:Why FastDoom Is Fast by masfuerte on Tuesday March 04, 2025 @08:11PM (#43261489)
He may well be thinking of Microsoft Visual C++, which dates back to 1993 and evolved into Visual Studio. It had a profiler.

https://en.wikipedia.org/wiki/Microsoft_Visual_C%2B%2B

Re:Why FastDoom Is Fast by Narishma on Tuesday March 04, 2025 @09:38PM (#43261962)
Doom was developed on NeXT machines, not Windows.
Re:Why FastDoom Is Fast by fredoralive on Wednesday March 05, 2025 @04:16AM (#43264550)
Although the DOS version was compiled using Watcom C, so presumably they'd use Watcom's debugger for testing the DOS version.
Re:Why FastDoom Is Fast by qingcharles on Tuesday March 04, 2025 @11:20PM (#43262733)
This. Thank you. I thought it was Visual Studio. It's been a while...! The games were a wretched mixture of C++, C and x86.
Re:Why FastDoom Is Fast by aqueueaqueue on Wednesday March 05, 2025 @04:12AM (#43264533)
I use VC++ in 96. Just trying to learn a bit of C++!