> Optimizing for worker fungibility, in a vacuum, seems like a -EV "playing not to lose" strategy. That's why you don't optimise for it in a vacuum. You weigh

> Optimizing for worker fungibility, in a vacuum, seems like a -EV "playing not to lose" strategy. That's why you don't optimise for it in a vacuum. You weigh the potential benefits of switching to Haskell versus the additional cost of maintaining/growing a Haskell team.