The meme format is awesome, but JSON differentiates strings with ".

{ "key": 1337 } vs { "key": "1337" }.

You might be thinking yaml? (Though it supports ' and " for explicit string types, technically)

But integer vs float? Good luck.

Phone material stopped mattering the moment camera bumps became a thing. Now, nearly everyone slaps a case to balance out the bump.

That said, I miss my completely mirrored-back Sony Xperia Z5 Premium.

Pravo

I didn’t really care about this thread until I read this comment.

The Who were kinda silly (eg: Boris the Spider) in their early years.

I have a PS5. Got FF7:Remake the minute it came out. Now I’m in a position where I want to play Rebirth so much I want to experience it on my best device, my PC.

While I disagree that the game was unplayable, I first played the game emulated at 4K@60K with AutoHDR (surprisingly decent) and it’s almost criminal how poor it looks on native hardware by comparison. The game scales really well.

Maybe with a new Nvidia kit we’ll get DLSS and Frame Gen. And I expect ToTK to get a new port.

It’s an Nvidia chip, so Switch Super.

Who am I kidding, if they followed Nvidia it’d be Switch AI.

AmazFit BIP series watches are pretty good. It’s amazing how horrible the Android OS is for watches but Apple set the tone saying 18 hours is enough.

It appears as though they did not like to gamble.

Somebody face-swap them all.

Judkins said that after the finger test, a lead cybertruck engineer at Tesla said he did the video wrong.

Timestamp in UTC

But for time of day, use local time and store separate column with the timezone name. Don’t use timezone offsets since that doesn’t work with DST. You’re better off with something like America/New_York because God knows what 2030 will look like.

And if timezone are abolished, or DST, that’s even more reason to store the timezone name.

Your dad is right. On desktop, navigation is on the left. On tablet, you shrink it to a rail. On mobile it should be a dismissible nav drawer.

The top menus, especially the flyover(on mouse hover), are bad for accessibility because they convert a non-committal action (hover) to a context changing one (focus). It’s a uniquely web-only invention and thankfully falling out of usage. (Unless you mean menubar/toolbar. Those are fine but extremely rare on Web.)

The entire Material Design framework in JS and Web Components in 80kb

https://clshortfuse.github.io/materialdesignweb/components/buttons.html

JS and Web Components are not the problem. Poor design is.

Yeah, that’s a big simplification and I get it. But the async syntax itself syntax “sugar” for Promises. It’s not like C# or Java/Android where it will spawn a thread. If you take a JSON of 1000 rows and attach a promise/await to each of them, you won’t hit the next event loop until they all run to completion.

It’s a common misconception that asynchronous means “run in background”. It doesn’t. It means run at end of current call stack.

Prior to that, the browser had window.setTimeout and its callback for delays and animation and such - but that’s it.

And you STILL have to call setTimeout in your async executions or else you will stall your UI.

Again async is NOT background. It’s run later. async wraps Promise which wraps queueMicrotask.

Here is a stack overflow that explains it more in detail.

Preventing the ui thread from waiting on native IO is what async was created for.

Citation needed. async just a wrapper for Promises. IO isn’t related, just commonly used with it.

https://tc39.es/ecma262/multipage/control-abstraction-objects.html#sec-async-functions-abstract-operations-async-function-start

NodeJS’s IO and fetch are just promises. (And NodeJS used to use callback(err, response) before adding promises.).

I don’t code much C++, but then I’d lose alignment with: x = *p; and I feel that would bug me.

I’m looking at Google Style Guide for my next project and it says either is fine, just don’t declare more than one per line.

Async prevents locking a thread during this wait.

That’s a very common misconception. async is just a scheduling tool that runs at the end of event loop (microtask queue). It still runs on the main thread and you can still lock up your UI. You’d need Web Workers for actual multi-threading.

async/await is just callback() and queueMicrotask wrapped up into a neat package. It’s not supposed to replace multi-threading and confusing it for such is dangerous since you can still stall your main/UI thread with Promises (which async also wraps).

(async and await are also technically different things, but for the sake of simplicity here, consider them a pair.)