Date: | August 8, 2003 / year-entry #17 |
Tags: | history |
Orig Link: | https://blogs.msdn.microsoft.com/oldnewthing/20030808-00/?p=42943 |
Comments: | 9 |
Summary: | Useless trivia day. Why is a registry file called a "hive"? Because one of the original developers of Windows NT hated bees. So the developer who was responsible for the registry snuck in as many bee references as he could. A registry file is called a "hive", and registry data are stored in "cells", which... |
Useless trivia day. Why is a registry file called a "hive"? Because one of the original developers of Windows NT hated bees. So the developer who was responsible for the registry snuck in as many bee references as he could. A registry file is called a "hive", and registry data are stored in "cells", which is what honeycombs are made of. |
Comments (9)
Comments are closed. |
I guess a bad pun would be to talk about honeypots…
Hmm, I thought it had to do with that fact that the data was structured using B-trees?
So, do you know the deal with MZ of MZ header fame? Is that really someone’s initials? If so, whatever became of the real MZ?
MZ is indeed Mark Zbikowski. He still works at Microsoft and is one of the nicest guys it’s been my pleasure to have met.
And here I thought the analogy was meant to refer to the notion that if you mess around (with the registry) and do not know what you are doing – you will get stung (or additional practice in reinstallation).
Ok, so I’m coming to this 8 months late :) Mark actually interviewed me, it was absolutely the most pleasant of my on-campus interviews :).
Commenting on this article has been closed.
An edge case that can result in a buffer overrun.
It didn’t do quite as much back then.