Hello? Hello, hello? Uh, I wanted to record a message for you to help you get settled in on your first night day. Um, I actually worked in that office before you. I'm finishing up my last week now, as a matter of fact. So, I know it can be a bit overwhelming, but I'm here to tell you there's nothing to worry about. Uh, you'll do fine. So, let's just focus on getting you through your first week day.
In case you are unfamiliar with this phenomenon and think it's a cherry-picked example:
to this day, uninitialized-data sections in object files and binaries - both on the Unix and Windows sides, as well as most other most "none of the above" targets - are called "bss"
"bss", of course, stands for "block started by symbol".
It was a pseudo-operation in UA-SAP, the United Aircraft Symbolic Assembly Program for the IBM 704.
In 1956.
"SysWoW64" stands for "System Windows-on-Windows-64", meaning it implements the "Windows" (Win32) API on top of 64-bit Windows. The name is cryptic because at the time it was chosen, Windows still supported being installed to a no-long-filename 8.3 FAT root file system. That the 32-bit compat subsystem has a "64" but not "32" in it, while the 64-bit system folder has a "32" but not "64" in it is unfortunate, but there you go.
In order:
- "System32" the original (16-bit) Windows system dir was "System", so the 32-bit Win32 version was called System32, presumably to keep 16- and 32-bit components separated to avoid confusion
- "user32" is the "user" (window manager, mostly, nothing to do with actual users) subsystem for Win32... because again the 16-bit ver was just "user". But it will probably never change names again
I just did this bit elsewhere but I like it, so, on a 64-bit x86 Windows machine:
- Windows\System32\user32.dll has a 32 in the directory and base name, file type PE32+, machine type "x64" (official spelling, aka IMAGE_FILE_MACHINE_AMD64), and is 64-bit
- Windows\SysWoW64\user32.dll has a 64 in the directory name, a 32 in the base name, file type PE32, machine type "x86" (aka IMAGE_FILE_MACHINE_I386) and is 32-bit
@Vague
GDPR violation any% speedrun
stop making the conversation about work-at-home about productivity
eliminating non-essential worker commutes means less fossil fuels wasted
remote policies increase access for disabled people, especially with chronic illness that flares
LGBT folks and PoC experience less bigotry and it's easier to report bigotry when they do
do some people want hybrid? do some people want on-site? sure
but stop pretending the discussion was about productivity or what employees want
it's about real estate portfolios
the learning curve is a little steep and the preview rendering performance is horrifyingly bad, but oh my god, why have i never used blender for video editing before. it's frame-precise, i can composite all the stuff i want, and it has keyframe-based animation. in an open-source package i'm already somewhat familiar with!!
So I'm sitting here trying to figure out how to tell if a particular app is running in Wayland or XWayland.
This is the answer I get off Stack Overflow. I'm thinking… No. No, that's too silly. It can't be the best way.
I keep researching. It's the best way.
You run xeyes.
Wayland has security that keeps windows from knowing about mouse events in other windows. XWayland doesn't.
Xeyes will track your cursor whenever you're over an XWayland window, then stop if you pass over anything else.
Well it had to happen eventually. #Scripps is retiring FLIP (FLoating Instrument Platform). This is an amazing piece of engineering (and soooo weird on the inside - everything pivots, so walls become floors). The #ship to be towed out to a location, and it would literally flip, sinking most of the ship directly down to give a *very stable platform for #oceanography research. Launched in 1962.
https://maritime-executive.com/article/world-s-strangest-research-vessel-heads-for-scrapyard-after-51-years
Trans woman, bisexual, someone's fiancée, forever a programmer, poly, and former total mess