The "adopting a tech with minimal thought" bit was about high level decision making.
I have no particular thoughts on Vue's newness or oldness because front-end JS is a frantic treadmill that I'm glad to not be involved in.
As for "would I hire a Rails guy for Zend?"
As I said, unless I'm desperately patching holes in a sinking boat, where I need you to jump right in and man the bilges with your indepth $framework knowledge, I hire first and foremost for a proven ability and willingness to learn and an attitude that makes you a good team fit.
You could be Rasmus Lerdorf and I'd reject you if you weren't interested in learning new things, and I'd reject you if you were an asshat, even if you're the best Zend developer ever, because if you're an asshat, you're going to lower the productivity of my team.
So would I hire a "Rails guy" for Zend? Yes. It's not like a Ruby framework is so massively different to a PHP framework that you need 10 years of Zend to make the transition.
But then, I'm biased,I self-taught in Python, focused on Django 1.0, got hired by a Java shop, started in Tapestry, then Wicket, then focused on backend, then went to RH to work on an K8s operator built on Vert.x, then ended up working at a Python shop 15 years after my previous in-depth usage of Python, working on a Django 4.0 app, and then FastAPI apps, even though I'm not a "FastAPI guy" nor a "Django guy".
Funnily enough though, I am a "Kafka guy", but now so are a bunch of my colleagues because I focus on sharing the knowledge.
To be clear, I wasn't hired to be a Django guru, or a FastAPI one, I was hired to implement code that satisfies business needs, in a manner that involves Django or FastAPI.
And yep, I've learned a shit ton about modern Django, but I've been productive since day 1. Because I enjoy learning and want to learn.
So yeah, I'm totally hiring that Rails person for Zend work if they've got the right mindset and the right fit.