When I'm evaluating a product, the language it's written in gives me some insight into what areas I need to investigate further, what questions to ask the vendor, etc.
So, if something's written with, say PERL, I'm going to be concerned about maintenance and reliability. If it's written in Python, I'm going to drill into the runtime performance and reliability more. If it's in C++, I might be looking at their development velocity.
Everything's a tradeoff, and so long as those tradeoffs are addressed then it's fine. The language just gives me a better idea about where to delve more attentively.
And of course, we also must consider if the language is a good candidate for specific problem being solved.
We wrote mobile logic in C++, primarily so we could easily port it between iOS and a different Linux device.
On MVP stage you can use whatever cheapest options you have: e.g. low/no code tools, manual updates. The tech matters at the scaling stage, here you have to select the tech that proven to scale and for which you can (relatively) easily find engineers.
So, yes -- I care.