ulterno

I am having difficulty understanding whether it broke its own cycle and is now crying, or broke someone else's cycle and is now being intimidating.

Damn reasonable people pushing back the Nuclear Apocalypse, the Global Heating Armageddon, return to Dark Ages and all such major fun events/s.

The wall of text was the error message.

I just prefer using the parsed outputs from IDEs which also take you to the line of code on click.

It becomes increasingly difficult to add a subconscious actions with age. And I didn't consider it worth the effort.

I could still drive on a highway with low traffic. And I have never seen an automatic transmission yet.

Yeah, I did driving lessons once and realised it was too late for me to start learning driving.
So I decided to be the stupid people with their bicycle and I'm much happier.

I feel much more in control when I am the motor and tend to get much better reaction times. On top of that, the lack of vision blocking, making it easier on my low situational awareness.

It's way cheaper too.

And finally I will be able to use eye protectors when cycling at night.
Right now, it just increases the lens flare and even getting expensive ones will, at most, not increase lens flare.

Doesn’t even startup on my box,

It needs to startup and then go to that point (after you select the projection) to cause the crash.
It definitely caused something other than the application to get into an invalid state. Which is why I am apprehensive about trying it out again to answer your comment. Probably was the display driver, which is why it didn't just turn off after that.

Also, make sure that all reflectors are turning the polarisation by 90°

That requires the driver to actually care

There's this game "HyperRougue". Run it on Arch.

hyperrogue-git version 13.0d.r60.g27fb2d92-1

Go to settings -> 3D configuration -> projection -> projection type -> . Cycle through the projection types. One of them causes something good enough to call a crash.

I don't remember anymore if it was just a display driver crash or a kernel crash and I haven't updated to a newer version (which might have fixed it).

What language were you using?
Python maybe? I don't know of any other interpreted language, that you may be calling system commands from, without saving to disk

I use C and C++ and my IDEs save to disk before compiling. Makes sense to not try compiling when there are potentially 2 versions (one on RAM or /tmp and one on Disk) and the build system might be running multiple commands, which the IDE may/may not know of, in my case.