working on the windows program compatibility team must be hell on earth
if you want to understand true hell, become a windows application compatibility programmer
all of these are sourced from here: http://ptgmedia.pearsoncmg.com/images/9780321440303/samplechapter/Chen_bonus_ch01.pdf
For example, one
useful shim is known as HeapPadAllocation; it is applied to programs that
have heap buffer overrun bugs. The shim intercepts calls to the
HeapAllocate function and adds a specified amount to the requested size.
That way, when the program overruns a buffer, it merely corrupts the padding
rather than corrupting the next heap block.
q. why does windows do [bizarre action]
a. for compatibility. to answer in more detail, we'll need to discuss a flaw in
earlier versions of windows NT
pre-NT windows versions
MS-DOS before networking support had been added
the discovery of electricity
this seems like a good time to drop another reminder that a windows registry file is called a hive because someone on the windows team had a fear of bees and the person developing the registry was being a jerk
@lynnesbian I highly recommend checking out the new old thing blog
@SwooshyCueb i read it a lot actually
@lynnesbian msdn blogs have saved my ass so many times. Really a shame MS deleted most of them recently
@SwooshyCueb they did? :c
@lynnesbian yup :c
@lynnesbian I've tracked down a copy of that PDF for later perusal.
@lynnesbian it is my professional opinion as an electrical engineer that the discovery of electricity was itself a mistake
(i would sign and seal a statement to that effect, but my PE stamp still has my retired name on it)
lewd, kink, silly
@lynnesbian abdl glitchin'
Make sure you get the right Raymond Chen.
There's more than one at Microsoft.
@lynnesbian that's hilarious tbh
@lynnesbian at this point he could just be making these up and who would ever guess
@lynnesbian the registry hives story seems pretty par for the course from my own experiences TBH.
Also thank you for this thread, it is pure gold (and I needed something to take my mind off more depressing stuff).
@lynnesbian Every part of this thread reminds me of all the fancy Windows exploits that have been retained purely for compatibility.
@lynnesbian or lotus 1-2-3
@lynnesbian or classic mac os versions of our own product
@lynnesbian o hai there 1904 dating system
@lynnesbian it is unfortunate that the last point is actually not a joke, and there was in fact a flaw in the discovery of electricity that makes the workings of modern electronics confusing
@lynnesbian and that for legacy reasons the flaw is not going to be corrected
@lynnesbian This reminds me of an article I read about an AI designing audio software, or something of the sort. It eventually came up with something incredibly efficient, but which couldn't be used on any hardware except the exact chip it had been given, because it was dependent on specific faults and features of that one chip to function.
I wish I could find the article so I know I'm not making it up or remembering it wrong...!
"we considered that the inventor of the wheel was probably the origin of the problem, and asked them to come to our lab to start again from the ground up."
love 2 think about how the rowhammer vulnerability isn't solveable unless we stop using electricity
@lynnesbian because Altair 8800 BASIC used to have a
@lynnesbian a reminder that clocks in ovens, microwaves and various similar appliances were running slow in Europe recently because the ancient political fight between Serbia and Kosovo means Serbia was unwilling to balance its grid for lack of capacity in Kosovo, which rippled out and caused a Europe-wide minor reduction in AC frequency
and many appliances without computer-powered clocks just count a second for every 50 AC alternations
@lynnesbian electronics were a mistake
@theoutrider thanks for posting this, I was talking about this a few weeks ago with someone but forgot the exact countries it involved!
@firstname.lastname@example.org's anti-chud pro-skub instance for funtimes