I find listening to (already listened to—this part is important) stuff is like a sleeping pill. Rip YouTube videos and put just the audio on your phone. Play it at bed time—I use earbuds and throw it under my pillow.
Right now, I’m listening to Kings & Generals and Operations Room audio. In the past, I’ve done Futurama audio.
There is no way the virus functioned. Seriously. The guy had no tech background.
WMI was introduced in XP (I think? Was it later?) and asking WMI for the version string was pretty common.
The reason there isn’t a Windows 9 is because there was a common test for windows versions that went something like this:
std::string winVer = getWinVerStr();
if (winVer.find(“Windows 9”) != -1)
{
// This is windows 95 or 98
}
A good chunk of older programs would likely have issues.
There was no need to produce the items in question, so we lost the expertise and the underlying manufacturing facilities/experience/etc. Stuff like: The company that made the windows no longer exists. The company that made the panels still exists, but they can no longer source the strictly defined % alloys as that company no longer exists. Stuff like that.
It makes more sense when I dug into it more deeply, but still—gave me a chuckle.
This is unrelated to this topic exactly, but I don’t know what OpenTofu is nor what it is for, so I looked at the FAQ.
What is OpenTofu?
OpenTofu is a Terraform fork, created as an initiative of Gruntwork, Spacelift, Harness, Env0, Scalr, and others, in response to HashiCorp’s switch from an open-source license to the BUSL. The initiative has many supporters, all of whom are listed here.
This is practically a meme…I have no idea what all of these are (coming from my area of expertise).
Similar experience. I doubled down by playing volleyball afterwards. The bruise was practically from wrist to shoulder.
He was most certainly being sarcastic.
It’s not that simple. Let’s say you have 100 revisions of an asset and the change happens on revision 42. Multiple people work on the same assets. If the engine in question (I admittedly don’t know what they use) stores each asset on a per-file basis, it’s a little easier. If not and the environment itself is stored in a monolithic file, it’s far worse.
You’ll need to (at best) binary search for the asset. You pull latest, see the bad content is there, try again with revision 50. See it’s there, try again with 25. It’s not there, okay, 37. Etc etc.
Not only that, it’s very often not as simple as just pulling that revision. “Oh. The asset format changed slightly on revision 40?” Time to pull the entire codebase down. “Asset A is referenced by this asset and won’t work because it differs?” Time to sync the entire codebase & assets back.
Etc, etc.
It most definitely takes a lot longer than one minute to check asset files for changes. That’s like saying you can just pop open 200 revisions of a 300MiB PSD file in notepad and see what change it happened in quickly. I don’t imagine somebody will write in their changelist description “submitting Nazi flag, lol” either.
Definitely a long arduous process to determine it.
Code monkey like Fritos….