Run results for: Lodash get vs. native solutions

Run details:

User agent: Mozilla/5.0 (Linux; Android 12; SM-G996B) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/100.0.4896.79 Mobile Safari/537.36

Browser: Chrome Mobile 100

Operating system: Android

Device Platform: Mobile

Date tested: 2 years ago

HTML Preparation code:

<script src='https://cdnjs.cloudflare.com/ajax/libs/lodash.js/4.17.5/lodash.min.js'></script>

Tests:

_,get, sloppy
const props = { stops: [ { location: { address: '123 Main Street', }, }, ], }; for (let i = 0; i < 50; i++) { const address = _.get(props, 'stops[0].location.address'); }
_.get, smarter
const props = { stops: [ { location: { address: '123 Main Street', }, }, ], }; for (let i = 0; i < 50; i++) { const address = _.get(props.stops[0].location, 'address'); }
native, no protection
const props = { stops: [ { location: { address: '123 Main Street', }, }, ], }; for (let i = 0; i < 50; i++) { const address = props.stops[0].location.address; }
native, some protection
const props = { stops: [ { location: { address: '123 Main Street', }, }, ], }; for (let i = 0; i < 50; i++) { const address = props.stops && props.stops[0].location.address; }