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.

I will start calling my JSON Web Tokens impregnated goblins.

standard keyboard

That’s easy: Alt+130

But for a tenkeyless one, that’s what Wikipedia highlighting is for.

People can beat this game with their eyes closed.

Of course they have milk! With vodka and some Kalua/Bailey’s!

VSCode will add a yellow box around the character and tell you it’s an uncommon glyph.

https://code.visualstudio.com/updates/v1_63#_unicode-highlighting

To note, this came about because it could be valid code and it’s a security risk from copy/pasting malicious code. See:

https://certitude.consulting/blog/en/invisible-backdoor/

2.54cm is easier for me because I do 2.04x + ½x.

8 inches? 16.32 + 4 = 20.32

12? 24.48 + 6 = 30.48

30? 61.20 + 15 = 76.20

60? 122.40 + 30 = 152.40

I don’t know why, but I find this easier. Maybe because it’s 4x, 2x, and ½ and my brain doesn’t like adding 32 and working in 1.8.

Show me potato salad!

Somebody face-swap them all.

Steam has limited rollback support from the command line which we had to do plenty of times for Starfield when working on Luma. Sometimes updates are small. Sometimes the entire exe gets reshuffled so you have to find where to patch the exe all over again.

All the versions are apparently there. You just need to download the “depot” and it’ll dump into a folder. From there you copy that folder over your game directly.

It also works the other way around. I can download the depot for the latest version and stay on the version I’m at. It’s useful to pick apart and diff what was actually changed.

Why they can’t add that as an option I’m not sure. That seems more of a UX/UI issue rather than a technical one (like avoiding people using old versions on the web server).

I was about to mod the game for HDR and then found out news of FO4 getting updated.

Updates break mods. Just how it is. Though, after seeing the work needed for modding Starfield after each exe change, I’m doing shader replacement now. As long as they don’t change from DirectX, I should be good.

Edit: Nevermind. Somebody asked me for help and got roped in. Got HDR working. Let’s see if it actually lasts.

Edit2: Just gotta fix TAA. Source

Exactly. Hence the filter.

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.

Also you’re supporting modders through Donation Points. Creators get real money proportional to mod download count. The mods are still free, to clarify.

I’m enjoying my Plex one and Nexus Mods. The latter one was in 2013 and cost me $40. Today the yearly subscription is $70.

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.

Maybe because you meant Jennifer Coolidge.

I’m sorry = I am sorrowful (sympathy or empathy)

I apologize = I am to explain my action (defense)

Consider:

• “I’m sorry you feel that way.”
• “I owe you an apology.”
• “What a sorry excuse for a ___ .”

Meaning, “I apologize” at a funeral is the same as “In my defense…”

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.).