Thank you, senior programmer, for sharing your valuable perspective. I'm Korean, so I've mostly studied Western culture through the curation of specific figures, which means I only knew broadly that there was a conflict between Postgres and MongoDB but I never knew the details like you do. In other words, for me it feels like reading a history book, whereas for you it feels like lived experience, so I imagine our perceptions are quite different.

'The heart lusts after Rust on the promise that it will solve all problems, but the mind knows it won't solve all problems.' I really like that sentence.

Personally, combining your thoughts with mine, I think this is also a matter of community belonging. In other words, I don't think the issue with Rust is that it's a solved problem. Rather, I think it's a process of burying anxiety about careers and professional uncertainty into community voices, as a way to project that unease. Learning a new language and all the libraries and frameworks tied to it is very demanding, and internalizing the conventions of a language takes time. So it becomes a question like, 'What if the skills I've invested so much in are suddenly no longer relevant?'

And while Rust's approach to problem-solving is attractive, as both you and I know, no single language can solve every problem. After all, every language has its own trade-offs and subsets. As you go lower-level, cognitive load increases significantly, which is why high-level programs are often written in low-level engines and scripts in high-level languages.

Anyway, I thought this place, where the world's best programmers gather, would be different, but I'm realizing that most programmers are quite similar.

Thanks for your thoughtful input. I hope I haven't taken up too much of your time. After all, this kind of question isn't usually encouraged in communities, and it's a difficult one to answer. Everyone thinks differently. But your explanation made the most sense to me. Have a great day.