As long as it is still running you should be fine, but it’s better to keep your battery around 80%. There are tools that block the charge until you ask for a full charge when needed

Nice!

Now I need T.A.R.S

Why nobody is doing T.A.R.S? I would if I could but I can’t…

PL setups are the best.

Yes

Oh thanks. That makes (more) sense now!

More like max-width: 8000px;

Good thing we got flexboxes and grids and container queries now.

I have 2 24" displays side by side. At some point I unified the desktops (or Spaces if you’re on Linux) to make it act “as if” it was a single ultra wide monitor. This was absolutely awful to use, especially during Google meetings where I had to share my screen.

Besides, I like being able to rotate 90° one of my screen because sometimes it’s just the best way to work.

This thing is stupid. Appealing maybe, but stupid.

What the heck, is this real?

Interesting article, but why on Programmer Humor?

In the case of a non-existing property, the value would be undefined rather than null.

And while == and != exist in JavaScript, most linters will throw an error and require a === and !== instead as they should be avoided.

null == undefined // true
null === undefined // false

Besides, null is a perfectly valid value for a property, just as 0. Working with API Platform, I couldn’t tell the number of times I used this kind of statement:

if (property || property === null) {
  // do some stuff
}

Probably just as much as

if (property || property === 0) {
  // do some stuff
}

in javascript a property is truthy if it exists

myThing.property = "some string"

if (myThing.property) { // true
  // do something
}

It works with everything except of course for falsy values

myThing.number = someNumberThatShouldNotBeEqualToZero

if (myThing.number) {
  // do something very important with that number that should not be equal to zero
}

// This can fail at anytime without warning

So you’ve got to be extra careful with that logic when you’re dealing with numbers.

I am not saying it’s wrong though. I’m saying it’s often annoying.

When my console throws a NaN I kinda think of it as an Halloween kid receiving a fruit instead of a candy. They won’t say “That’s a fruit”. They’ll say “That’s not a treat”.

I’m personally pissed more often by a falsy 0.

Did you know that early analog computers would literally explode when asked to divide by 0?

Now computers just say “Hey stupid, that shit is not even a Number in a mathematical sense, but sure I’ll add one to it.” instead of “Why would you kill me like this?”

You can’t really define Infinity as a number, yet it is part of their world.

So typeof NaN === ‘number’ totally makes sense in that regard.

If you ever worked with arrays of dates, don’t judge NaN too harshly.