@LauraFlowD@AdamRackis It's not a question of easy to read. With each ternary you nest, that's 2โฟ cases you're attempting to cover. It's unlikely you've really considered them all. More likely you're modeling the problem wrong.
@GiftVincy@denicmarko That also (sort of!) justifies why NaN != NaN. If a calculation produces a result that's outside the
universe of things we can represent, then we can't even say if it's equivalent to another such result.
@GiftVincy@denicmarko When you see "not a number" think "not a number you can represent with floating point math" instead. sqrt(-1) *is* a number, it has a definition in complex math, but floating point calculations can't represent it so they turn it into NaN.
@NameNick90@TheMarz77@PicturesFoIder That makes perfect sense once you understand the concept of project but I can't help but feel the animation would've been more approachable if they just used a sphere ยฏ\_(ใ)_/ยฏ
@BenKingNTU That's a fair point, you could just return `response.json()`, no await needed. But assigning a promise to a variable called `data` is certainly misleading. And often you'll want to do something with `data` before returning it and that would not work without the `await`.
Life Universe https://t.co/DLCTLNTqII
Explore the infinitely recursive universe of Game of Life! Works in real-time and is perfectly consistent, never fails to remember where you are and where you came from.
็ก้ใซๅๅธฐใใใฉใคใใฒใผใ ใฎๅฎๅฎใๆข็ดขใงใใไฝๅใไฝใใพใใ #indiedev
@ericbureltech Those keys suggest you use vim, in which case I'd like to inform you that vim actually has an undo tree. g- and g+ move through it. You won't lose your changes.
https://t.co/MWoc4YLP4T
@joelnet Promises were originally implemented in userland. When native support was added, it was desirable to maintain compatibility with libraries like Q and Bluebird. Therefore, any object with a `then` property is considered a "thenable."
https://t.co/qIElqivGZc