types in C are pretty weird

int *a can be read as

1. *a is a int
2. since dereferencing is a operator on pointers, a is a pointer to int

int *a, b is read as

1. *a and b are int
2. so a is a pointer to int and b is a int

bool getofmylawn(Lawn lawn)

1. getoffmylawn(Lawn lawn) is a bool
2. since calling is done on functions, getoffmylawn is a function that takes a Lawn and returns a bool

And then you have function pointers

bool (*foo(int a))(float b)

1. (*foo(int a))(float b) is a bool
2. *foo(int a) is a function from float to bool
3. foo(int a) is a function pointer from float to bool
4. foo is a function that takes a int and returns a function pointer from float to bool

really weird in my opinion.

To be honest, I think, they both have their place. In Rust, you typically wouldn't return just a bool, but rather the element that you removed, so like this:

fn getofmylawn(lawn: Lawn) -> Option<Teenager> {
    lawn.remove()
}

And then with such a more complex return-type, C-style means that you can't see the function name right away:

Option<Teenager> getofmylawn(Lawn lawn) {
    return lawn.remove();
}

I also really don't think, it's a big deal to move your eyes to the ->...

I really don't agree with saving keypresses being a useful metric, since auto-completion is a thing and code is read significantly more often than it is written. I am also a staunch opponent of abbreviations being used for variable names.

But I will say that I don't mind abbreviations in keywords, since well, you need to learn the meaning either way.
And yeah, I've come to somewhat like them being used for keywords, since it reduces visual noise where it really isn't useful, and it distinguishes keywords from actual code.
Ultimately, keywords are just syntax where letters were used instead of a symbol. You do read them like a symbol, so if they don't look like a real word, that seems to work quite well for my brain.

To be fair, in C/C++ you can include stdint.h which defines type aliases such as uint64_t.

Ooh yeah, overall coding culture is definitely not affected by the preferred nomenclature for identifiers. The person who's habituated to fn over function will absolutely never name their functions in the vein of chkdsk. The two are completely disconnected in the brain of the programmer who read too much K&R in their childhood and was irretrievably traumatized by it for life.