It's better to not have such people working for you in the first place.
Maintaining existing software to focus on real business is just the kind of founders I'd want to work with. It's a part of being a part of a startup, and those who jump the ship too often do not leave any legacy behind.
Developers who jump because they'd rather build from scratch instead of helping maintain and improve an existing solution is irritating.
More power to them, but I respect developers a lot more who stay, fight through legacy code battles, make steps/headway to shift the application to a newer platform that makes practical sense than those who leave.
If your employer refuses to move to a stack you feel is justifiably better, in both business and technical aspects, then I totally understand leaving. If you're leaving because you don't want to maintain a system that's "older" and don't want to take on the challenge of improving it then I agree with your post. I'd rather not have those developers to begin with.
Personally, I've developed Ionic apps that integrate with Firebase, PushWoosh, Back& among others... You are free to choose. No lock in necessary.
Key point - for hybrid development. There are a lot of use cases where hybrid mobile apps are appropriate (CRUD). With ever more powerful devices, the argument for hybrid increases.
Devs are migrating en masse to react native. I have friends in several startups leaving their jobs because they've been tasked with maintaining legacy Ionic 1.x/Angular projects, while the codebases are migrated to react native...
For hacking quick MVPs is not bad, it was even cool 2 years ago, but for serious projects starting from zero, react native is a smarter choice.
[0] https://github.com/driftyco/ionic-cloud/issues