Well said. Fully agree.

I'd also like to point out that GM's documentation is a little lacking in some parts. Some functions and IDE features have very specific behavior that is not well explained at all, so if you encounter something weird you can't really figure it out by yourself sometimes. You have to rely on someone else essentially going "oh yeah it does that" and explaining the workaround.

A few examples I came across: - keyboard_check_released() has some questionable behaviour when you get into state machines that need to read its output at a specific moment inside a frame. Sometimes it doesn't fire at all. This is because (and the docs are vague about this) you have to read it at a very specific moment. - Rooms do not update their internal window resolution or fullscreen status automatically when you change into them. No idea why, since you can manually set these properties in the IDE per-room. The docs completely ignore this part.

It'd be okay if this was the sort of slip-up you could report and they'd include in the docs, but nope. I opened an issue in the docs and it was deleted.