It was used extensively, including in time-critical places such as during render operations. While there was a performance hit that could be measured with dev-tools, it was nothing compared to the usual day-to-day bottlenecks that were encountered.
The point is to say that sure, worry about performance, but perhaps rest/spread/destructuring isn't the first place you need to look these days.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
We're discussing named parameters and the performance hit they would be on JavaScript's runtime.
And TypeScript does a whole lot more than type checking nowadays.
I must chime-in with a report from experience.
Some years ago I worked on a fairly large (~700k lines) JavaScript codebase that implemented a 200-line helper that permitted the following:
It was used extensively, including in time-critical places such as during render operations. While there was a performance hit that could be measured with dev-tools, it was nothing compared to the usual day-to-day bottlenecks that were encountered.
The point is to say that sure, worry about performance, but perhaps rest/spread/destructuring isn't the first place you need to look these days.