EitherOwnedOrBorrowed and AtomicReferenceCountedPointer, but that'd be annoying to type once you know them.
code is read more than it is written, so having those longer terms helps with reducing mental load and providing self-documenting code
and with most modern ide or even text editors providing autocompletion, (imho) i think abbreviations not really neccessary (though they can be fun in the case of kotlin ^^)
I disagree. Code should optimize for the things you want to look for being relatively the most prominent. This is why I think go is harder to review: the bits you actually care about are overwhelmed.
well, i think we can at least say, there is a balance for sure, so there is a limit to verbosity where it get overwhelming, ill defintely agree to that
and with most modern ide or even text editors providing autocompletion, (imho) i think abbreviations not really neccessary (though they can be fun in the case of kotlin ^^)