Re:Ladybird: Closing this as we are no longer pursuing Swift...
by polliog on Wednesday February 18, 2026 @06:42PM
(#47067976)
The task list with possible workarounds was there, so I imagine there was also the possibility of continuing with the integration. I understand that after two years it may be inconvenient, but they had already started, so why throw away all that time? As for the “AI” issue, I think we need to start being less paranoid about it
[ Parent
| on HN ]
Re:Ladybird: Closing this as we are no longer pursuing Swift...
by tomovo on Wednesday February 18, 2026 @06:58PM
(#47068108)
Sunk cost fallacy. It didn't work out, the decision was made, they move on. I like that.
Re:Ladybird: Closing this as we are no longer pursuing Swift...
by manbash on Wednesday February 18, 2026 @07:39PM
(#47068451)
Chiming in: indeed, the response is very dry, and raises suspicion. It states the obvious facts and then makes a boring statement, lacking any nuance of the conversation. It is not argumentative in the very least.
Time has been spend, yes. But the topic at hand is after so much time the conclusion to abandon this path is justified.