Code written this way is often smaller and tighter. But that doesn’t make it unmaintainable. Is Haskell unmaintainable because of its dense, clever use of the type system? No way. But I’d personally struggle to maintain something like that because I don’t have enough familiarity with Haskell to do so. Likewise I wouldn’t trust most programmers to maintain the rust code I’ve been writing lately - not because it’s bad rust, but because I’m making heavy use of the language’s features. That raises the skill floor. In comparison, if you gave me some crashing Go code I could probably debug it even though I don’t know much go.

I find most Java code bases awful to maintain because there’s always so much code. Simple changes take a long time to make because there’s so much code to understand and modify. Give me the tight rust any day.