Re:Ladybird: Closing this as we are no longer pursuing Swift...
by mvdtnz on Thursday February 19, 2026 @02:42AM
(#47071022)
You're re-stating his exact problem while trying to refute him.
[ Parent
| on HN ]
Re:Ladybird: Closing this as we are no longer pursuing Swift...
by fingerlocks on Thursday February 19, 2026 @04:06PM
(#47079388)
No, I’m not. OP is conflating multiple guidelines for different purposes and attempting to use them all simultaneously.
Re:Ladybird: Closing this as we are no longer pursuing Swift...
by zephen on Friday February 20, 2026 @04:03AM
(#47085493)
> OP is ... attempting to use [multiple guidelines] simultaneously.
No, he's literally explaining why the guidelines can't be used simultaneously.
Re:Ladybird: Closing this as we are no longer pursuing Swift...
by fingerlocks on Saturday February 21, 2026 @07:24AM
(#47100126)
They aren't supposed to be used simultaneously, which is literally what my comment was explaining. Different guidelines to solve different problems.
Re:Ladybird: Closing this as we are no longer pursuing Swift...
by zephen on Saturday February 21, 2026 @11:34AM
(#47102275)
Have one source of truth is a universal guideline.
Prefer structs over classes is a universal, if weak, guideline.
It's funny how people can be all hung up on composability of things like type systems, and then completely blow off the desire for composability of guidelines.