Is the FN call overhead really that horrible in lodash? I didn't see any side by side comps.
Also, the transformed code (like all transformed babel) is most likely ugly and more verbose than using lodash's get, no?
Also, the transformed code (like all transformed babel) is most likely ugly and more verbose than using lodash's get, no?
The overall size overhead is what is horrible.
> Also, the transformed code (like all transformed babel) is most likely ugly and more verbose than using lodash's get, no?
Yes, but it also performs at what is probably as-close-to-optimal as possible. The resulting ternaries are extremely easy to work with for even the most basic of JS compilers. Source maps work well - I don't see this as a downside at all.
However, I wonder why lodash doesn't use a lambda. Parsing that path seems silly. It could just be a try on a lambda https://github.com/lodash/lodash/blob/master/.internal/baseG...