That's fair. If it's 90s and it's part of a developer workflow that is triggered more than a few times a day, it matters. I haven't worked with Swift in particular, but in general you might be able to do incremental compilations to avoid that problem rather than "rebuild the entire project" with every change.

My real point is that I care about everything more than speed until I have a specific reason to care about speed. Then I'll care about speed.

In contrast, many programmers fetishize speed and efficiency as a quasi-religious value, even when they have no practical consequences.