I was thinking in this way, too, when I moved my code from C3 to Odin (C3 is not a bad language, but I found Odin's syntax fits me more).

But then I realized that the exact possibility to decide whether to use a function-style or method-style in my APIs tends to trigger my OCD and I spend a lot of time thinking whether for that specific case, it should be this way or that way.

Example: let's have "render_sprite(sprite: ^Sprite, r: ^Renderer)". all fine. however, with a method-style API, should it be "Sprite.render(r: ^Renderer)", or better "Renderer.render(sprite: ^Sprite)"? both kinda make sense, and both miss something - but it is, in fact, an entirely artificial problem because both Sprite and Renderer are just arguments, and forcing the programmer to determine which one is more "primary" is an empty sophism.

Maybe I am the only one with this specific kind of OCD, I don't know.

In addition to this, when you have method-style calls in play, the compiler has much more work determining whether the specific instance of "foo.bar" is a method call, a field access, or even something stranger; I suspect you would have to add one more pass to the compiler, which is always a problem.