Re:Ladybird: Closing this as we are no longer pursuing Swift...
by PaulDavisThe1st on Wednesday February 18, 2026 @09:59PM
(#47069350)
I don't really want to defend method swizzling (it's grotesque from some entirely reasonable perspectives). However, it does work on external/3rd party code (e.g. audio plugins) even when you don't have control over their source code. I'm not sure you can pull that off with "better" approaches ...
[ Parent
| on HN ]
Re:Ladybird: Closing this as we are no longer pursuing Swift...
by alwaysbeconsing on Thursday February 19, 2026 @01:32PM
(#47077258)
Problem come when a third-party code do that swizzling, looking at you every iOS analytics framework to this day.
Re:Ladybird: Closing this as we are no longer pursuing Swift...
by bunderbunder on Thursday February 19, 2026 @02:33PM
(#47078079)
That’s the main use case I can think of. It’s possible with other languages but may require more hacking.
I like monkey patching for testing legacy code. I like it less as a thing in production code because it can become a security and reliability problem.