Should we replace all references to "legacy" linker with "slow" linker, and similarly use "fast" instead of "surgical"?
This just makes things easy for the user. Slow and fast immediately reveal important properties that are not clear when you see "legacy" or "surgical".
I think this is a way of dumbing down the user unnecessarily. That also assumes that one or the other will always be faster than the other which might not be true. I believe the user to be capable to understand that less milliseconds next to what ever it is called means faster and more means slower.
if anything I would like to see details to understands why it is faster, instead of just the "faster", as well as the trade offs associated with it, for example, is it a good idea to use the surgical linker for release builds of the app?
probably "release linker" and "dev linker" instead of legacy and surgical.
the main thing I wanted to communicate with "legacy" was "going to be deprecated in the future"
("deprecated linker" would be a fine replacement name once we actually have full surgical linker coverage :big_smile:)
Last updated: Jun 16 2026 at 16:19 UTC