[devadvance]

My primary hesitation with posts like this is that it mixes engineering points (performance, developer experience, code sharing) with a more general business point: hiring.

Hiring is a cost. There are costs to any decision. Opportunity cost, risk, business continuity, operational costs, etc. Hiring is generalizable so it makes for an easy example here.

I would hope that experienced folks making decisions like "React Native or Flutter" would weigh the full gamut of costs in their specific business context.

[clintonb]

Your first and last paragraphs seem contradictory. You Hope experienced folks weigh all costs, but a post mentioning the cost of hiring gives you hesitancy?

[devadvance]

The fact that the post mentions hiring (cost) isn't my hesitation. It's that bringing cost into a conversation about the technical merits of a given technology can be a heavy-handed way of shutting down the conversation. In some cases, technical merits very much do justify the cost, but that can only happen by creating the space to find out.

Said differently: I believe it's often worthwhile to discuss the deeper technical merits of options without hastily jumping to a cost discussion.