Pry VS Quake-III-Arena

that's surprising considering `pry`[1] is such an amazing debugger IMO.

[1] https://github.com/pry/pry

All of my recent tutorials and projects were primarily managed using the default Ruby REPL, irb, and I must say it's been nothing short of amazing. However, what ultimately prompted me to switch to Pry was its offering of better defaults. But what exactly does that mean? Let me demonstrate:

For older versions: Pry Gem

To do that, I would install `pry` into your rails project and then use it look around right before your test fails.https://github.com/pry/pry

This means I can be editing a shell script and easily inject arbitrary regions into a shell buffer for immediate testing (point never leaves the window where I am editing, and I can view the shell output in an adjacent window). This is similar to what Robe does with Pry within an inferior Ruby process using comint.

https://pry.github.io/ - also a lot of features from Pry have made it into the default IRB these days, but I still use pry. I don't know the equivalent commands in IRB.

For debugging, while not multi-threaded, to my knowledge, is the pry gem for debugging. There are a few different flavors, for instance, my favorite is pry-byebug.

Github Link : https://github.com/pry/pry

Quake III Arena

If you know C, you can check this out by comparing the different player movement code of Quake 3 and Quake 1.

You mean this code?

https://archive.softwareheritage.org/browse/content/sha1_git...

Do you see that notice at the top of the file? It says:

==

This file is part of Quake III Arena source code.

Quake III Arena source code is free software; you can redistribute it

The error messages comes from this file in the source code. It looks like the client is trying to parse entities from the server but the readcount is greater than the cursize in the messages. I am not an expert but I believe there could be a mismatch between the versions of your client and the servers you are trying to connect to.

After learning C, one of the first projects I came into contact with, was the ID Tech 3 game engine [1]

On the one hand, it taught me how professional C programmers structure their code (extra functions to remove platform differences, specific code which is being shared between server and client to allow smooth predictions) and how incredible fast computers can be (thousands of operations within milliseconds), but it also showed me, how the same code can result in different executions due to compiler differences (tests pass, production crashes) and how important good debugging tools are (e.g. backtraces).

To this day I am very grateful for the experience and that ID decided to release the code as open source.

[1] https://github.com/id-Software/Quake-III-Arena