doom3do: DOOM for the 3DO

Re:doom3do: DOOM for the 3DO by hd4 on Wednesday November 02, 2022 @05:46PM (#33443338)

Try actually reading, it's the original port.

[ Parent | on HN ]

Re:doom3do: DOOM for the 3DO by brianbreslin on Wednesday November 02, 2022 @05:53PM (#33443424)

When one sees the last commit as 29 days ago, or the previous commit as 8 years ago, one can easily assume it wasn't code from 1995. So again. Why is this even interesting?

[ Parent | on HN ]

Re:doom3do: DOOM for the 3DO by IntelMiner on Wednesday November 02, 2022 @06:07PM (#33443576)

Read the readme instead of arguing on HN about it

[ Parent | on HN ]

Re:doom3do: DOOM for the 3DO by tappdarden on Wednesday November 02, 2022 @06:08PM (#33443595)

github (and git) wasn't around in 1995

One should read the readme's.

let people enjoy things.

[ Parent | on HN ]

Re:doom3do: DOOM for the 3DO by helf on Wednesday November 02, 2022 @08:38PM (#33445057)

Seriously.

Different strikes for different folks.

I love stuff like this. It’s computer history. It’s interesting from a technical perspective as well as being a snapshot of culture.

[ Parent | on HN ]

Re:doom3do: DOOM for the 3DO by b1ue64 on Wednesday November 02, 2022 @07:59PM (#33444669)

> The complete archive for DOOM for the 3DO

It's funny how you bother to look at the commit dates, but not the README and repository description

[ Parent | on HN ]

Re:doom3do: DOOM for the 3DO by helf on Wednesday November 02, 2022 @08:37PM (#33445046)

Man you must be a hoot at parties.

[ Parent | on HN ]

Re:doom3do: DOOM for the 3DO by bstar77 on Wednesday November 02, 2022 @11:25PM (#33446608)

The responses you are seeing is what happens when you lack self awareness and humility.

[ Parent | on HN ]