I’ve also used .local but .local could imply a local neighborhood. The word itself is based on “location”. Maybe a campus could be .local but the smaller networks would be .internal
Or, maybe they want to not confuse it with link-local or unique local addresses. Though, maybe all .internal networks should be using local (private) addresses?
I just recently started working with ImGui. Rewrite compiled game engines to add support for HDR into games that never supported it? Sure, easy. I can mod most games in an hour if not minutes.
Make the UI respond like any modern flexible-width UI in the past 15 years? It’s still taking me days. All of the ImGui documentation is hidden behind closed GitHub issues. Like, the expected user experience is to bash your head against something for hours, then submit your very specific issue and wait for the author to tell you what to do if you’re lucky, or link to another issue that vaguely resembles your issue.
I know some projects, WhatWG for one, follow the convention of, if something is unclear in the documentation, the issue does not get closed until that documentation gets updated so there’s no longer any ambiguity or lack of clarity.
My open-source, zero dependency JS library for requesting and generating certs with dns01: https://github.com/clshortfuse/acmejs
I only coded for name.com but it is compatible with anything really. Also can run in the browser, which could be useful in a pinch.
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.
Wow, you think Teslas are “Chinese EVs”. You’re literally the first person I’ve encountered to think so. Also why lead into an article with a graphic of the least selling vehicle?
Doesn’t stop it from being misleading.
It’s called “burying the lede”.
In China. But the majority of Teslas are manufactured are in China, and no one really considers Teslas “Chinese cars” or “Chinese EVs”.
Well, I feel misled. The graphic shows a Volvo as a Chinese manufactured vehicle.
Sales of Chinese made EVs in Australia
- Tesla - 46,116
- BYD - 12,438
- MG - 5,928
- Volvo - 3,949
They’re counting Tesla as a Chinese EV.
Of course they have milk! With vodka and some Kalua/Bailey’s!
Show me potato salad!
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.
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.
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.
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.
NodeJS’s IO and fetch are just promises. (And NodeJS used to use callback(err, response) before adding promises.).
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.)
Years (decades) ago it wasn’t uncommon to create self-signed/local CAs for active directory, but it’s really uncommon today since everything is internet facing and we have things like Let’s Encrypt.
It’s so old, the “What’s New” article from Microsoft references Windows Server 2012 which is around when I stopped working on Windows Server. I kinda remember it, and you needing to add the server’s cert to your trusted roots. (I don’t know about Linux, but the concept is the same, I’m sure. I never tried generating certificates, but know all the other client -side stuff. Basically you need a way to fulfill CSRs.)
https://learn.microsoft.com/en-us/windows-server/identity/ad-cs/
What you’d want to do it in Windows is all there, and Microsoft made that pretty easy back then to integrate with all their platforms and services, but I’d caution, do you really want to implement 10+ year old tech?
DuckDNS has long enough latency (over 2000ms) where Google Assistant can’t connect. I moved to FreeDDNS and my Home Assistant issues went away.
Reference: https://community.home-assistant.io/t/google-assistant-keeps-losing-connection-with-home-assistant/468062/140?page=7