It's very weird to realise that this isn't long enough to remember a time when extending native prototypes was en vogue. Source: over 1 year ago

The parent is referring to the Prototype framework (http://prototypejs.org/), not the JS language concept of a prototype. Source: almost 2 years ago

Let's not forget about http://prototypejs.org/ & http://script.aculo.us/ for modern Web 2.O. - Source: Hacker News / over 2 years ago

Overriding prototypes used to be state-of-the-art, and indeed it was one of the things that made me fall in love with JS. Frameworks like PrototypeJS and MooTools were built around this and it was of very limited convenience and unlimited headaches. Source: about 3 years ago

GZDoom for Doom and many other games running on the same engine. Source: over 1 year ago

For modern source port check GZDoom https://zdoom.org/index or Chocolate Doom (for higher framerates and stuff) - https://www.chocolate-doom.org/wiki/index.php/Chocolate_Doom. Source: about 2 years ago

Also, if you want to make a shooter like those, you don't really want the original Build engine. What you want is a modern open source implementation of those engines. For Duke-like games you can try https://www.eduke32.com/ (Ion Fury was made on this) , for Doom try https://zdoom.org/index or https://dengine.net/. Source: over 2 years ago

I don't know, but if you want a retro game you might as well use a retro-engine. Ion Fury (2019) used the EDuke32 engine and there are also modern versions of the original Doom engine, like GZDoom - with modern games like Brutal Doom or SIGIL (2019). Source: over 2 years ago

Because zDoom and GTA anniversary releases are a thing. Source: over 2 years ago