A space to discuss and keep up software development and manage your software career
An inclusive community for gaming enthusiasts
News and discussion of science and technology such as AI, VR, cryptocurrency, quantum computing, and more.
From composing and gigging to gear, hot music takes, and everything in between.
Discussing AI software development, and showing off what we're building.
A general discussion space for the Forem community. If it doesn't have a home elsewhere, it belongs here
Movie and TV enthusiasm, criticism and everything in-between.
Memes and software development shitposting
Web design, graphic design and everything in-between
A community of golfers and golfing enthusiasts
Your central hub for all things security. From ethical hacking and CTFs to GRC and career development, for beginners and pros alike
For engineers building software at scale. We discuss architecture, cloud-native, and SRE—the hard-won lessons you can't just Google
Discussing the core forem open source software project — features, bugs, performance, self-hosting.
A place for parents to the share the joys, challenges, and wisdom that come from raising kids. We're here for them and for each other.
A collaborative community for all things Crypto—from Bitcoin to protocol development and DeFi to NFTs and market analysis.
A community for makers, hobbyists, and professionals to discuss Arduino, Raspberry Pi, 3D printing, and much more.
This is incredible feedback and so good to learn!
Yeah I've watched some videos on the topic where it's best practice to use undefined over null but I love your explanation!
undefined
null
Thank you!
One caveat about undefined:
const obj = { nil: null, nothing: undefined, }; console.log(obj.nil == undefined); // true (non-strict equality) console.log(obj.nothing === undefined); // true console.log(obj.zilch === undefined); // true console.log(obj.hasOwnProperty('nil')); // true console.log(obj.hasOwnProperty('nothing')); // true console.log(obj.hasOwnProperty('zilch')); // false const array = [null, ,undefined]; console.log(array[0] == undefined); // true (non-strict equality) console.log(array[1] === undefined); // true console.log(array[2] === undefined); // true console.log(array[3] === undefined); // true console.log(array.hasOwnProperty(0)); // true (value `null`) console.log(array.hasOwnProperty(1)); // false (hole, empty) console.log(array.hasOwnProperty(2)); // true (value `undefined`) console.log(array.hasOwnProperty(3)); // false (out of bounds)
An undefined value is inconclusive with regards to the existence of the property/element within an object/array.
Also note that browser developer tools will mark "holes" in arrays with empty.
empty
Chromium:
> console.log([0,,2]); (3) [0, empty, 2]
Firefox:
> console.log([0,,2]); Array(3) [ 0, <1 empty slot>, 2 ]
ECMAScript 6: holes in Arrays
The void operator returns undefined.
let count = 0; const result = void(count += 1); console.log(count); // 1 console.log(result); // undefined
Are you sure you want to hide this comment? It will become hidden in your post, but will still be visible via the comment's permalink.
Hide child comments as well
Confirm
For further actions, you may consider blocking this person and/or reporting abuse
We're a blogging-forward open source social network where we learn from one another
This is incredible feedback and so good to learn!
Yeah I've watched some videos on the topic where it's best practice to use
undefined
overnull
but I love your explanation!Thank you!
One caveat about
undefined
:An
undefined
value is inconclusive with regards to the existence of the property/element within an object/array.Also note that browser developer tools will mark "holes" in arrays with
empty
.Chromium:
Firefox:
ECMAScript 6: holes in Arrays
The void operator returns
undefined
.