I dunno, I know it was a thing on Reddit, I don’t think I’ve ever seen it over here. Maybe Google bonked them.
I dunno, I know it was a thing on Reddit, I don’t think I’ve ever seen it over here. Maybe Google bonked them.
That tracks, thanks!
I’m no weather expert, but because you’ve got a regular pattern around the radar (the circle) that really shouldn’t appear in a normal weather condition, the beam may be getting grounded due to local conditions - see beam ducting.
The lil notch on the right is looks like it might be showing incomplete, conflicting, or out of bounds data. The site’s map legend may have a decoder for that pattern.
https://www.noaa.gov/jetstream/radar-beams
Or it could be the apocalypse, who am I to judge /j
Biblically accurate roadrunner wasn’t on the list of things I was expecting to see today
Looks like the video/image got over compressed or over enhanced. There’s probably not enough data in that file to reconstruct what happened here.
Linear or AI interpolation may make the image appear clearer, but it’s at the cost of creating new data that wasn’t already present.
Before anyone gets too deep I’d like to point out that this is just about hosting vector tiles, the actual tile gen is a separate project. Not to say that hosting large sets of files is trivial, just that there’s more to the picture than one repo.
Thanks! I learned something new today, and that makes today a good day. I’ll strike out a few relevant parts of my answer when I get a minute to open the beast.
I mean… DX 9, 10, and 11 were all released prior to Nadella being CEO/chairman.
But in software, it’s very commonplace for library versions not to be backwards compatible without recompiling the software. This isn’t the same thing as being able to open a word doc last saved on a floppy disk in 1997 on Word 365 2024 version, this is about loading executable code. Even core libraries in Linux (like OpenSSL and ncurses) respect this same schema, and more strongly than MS.
Using OpenSSL as an example, RHEL 7 provides an interface to OpenSSL 1.0. But 1.1 is not available in the core OS, you’d have to install it separately. 1.1 was introduced to the core in RHEL 8, with a compatibility library on a separate package to support 1.0 packages that hadn’t been recompiled against 1.1 yet. In RHEL 9, the same was true of OpenSSL 3 - a compatibility library for 1.1, and 1.0 support fully dropped from core. So no matter which version you use, you still have to install the right library package. That library package will then also have to work on your version of libc - which is often reasonably wide, but it has it limits just the same.
Edit because I forgot a sentence in the last paragraph - like DirectX, VC++, and OpenGL, you have to match the version of ncurses, OpenSSL, etc exactly to the major (and often the minor) version or else the executable won’t load up and will generate a linking error. Even if you did mangle the binary code to link it, you’d still end up with data corruption or crashes because the library versions are too different to operate.
DirectX 12 was released in 2015 with Windows 10, so it’s unlikely to have been ported back to 8.1 and lower.
MS usually only does current+ with compatibility - so for example FF11 (DirectX 8.1 I think) still works (mostly) on Windows 11, but DX12 won’t work on W7
DirectX, OpenGL, Visual C++ Redist and many other support libraries in software programs typically require the same major version of the support libraries that they were shipped with.
For DirectX, that major version is 9, 10, 11, 12. Any major library change has to be recompiled into the game by the original developer. (Or a very VERY dedicated modder with solid low level knowledge)
Same goes for OpenGL, except I think they draw the line at the second number as well - 2.0, 3.0, 4.0, 4.1, 4.2, 4.3, 4.4.
For VC++, these versions come in years - typically you’ll see 2008, 2010, 2013, and the last version 2015-2022 is special. Programs written in the 2013 version or lower only require the latest version of that year to run. For the 2015-2022 library, they didn’t change the major version spec so any program requiring 2015+ can (usually) just use the latest version installed.
The one library that does weird things to this rule is DXVK and Intel’s older DX9-on-12. These are translation shim libraries that allow the application to speak DX9 etc and translate it on the fly to the commands of a much more modern library - Vulkan in the case of DXVK or DX12 in Intel’s case.
Edited to remove a reference to 9-on-12 that I think I had backwards.
My pre caffeine brain though this was chocolate
Tbh this is a programming community. While yes, a quick summary would not have gone amiss, I don’t fault OP for not including it. RFCs are often pretty dry but this one is reasonably straightforward as a subset of JSON to reduce some ambiguity.
Might be your client, the image shows up on Voyager
Who let out 426?? I thought I was supposed to be in a windowless room!
(/j)
ICYMI, the joke is about SCP-426
Ok. Can you back that up with a source?
Fast pace tiktok style videos aren’t really great to analyze on a phone, and your clip doesn’t seem to contain any outbound links.
Oh totally. I have a pile of RS-232 adapters that you still need to program just about every modern Ethernet switch, and they’re all type-A ports.
No we’re not OK
I remember in grade school my district had a system where everyone who bought anything at the cafeteria went through an internal “type in your ID to the pin pad” system. Internally, the computer would decide whether the student was charged against their account or if it did a discount/free. This was how they dealt with that.
Not on all vendors tho - coloring was an optional part of the standard. Dell often uses grey for USB3
So this is the choose your own ending in the comments section from last week. I can follow the plot line of the RIAA sueing for copyright on the whistling song, but there’s a lot more else going on here I haven’t sorted yet.
Link back to last week in the description.