Big Boobs could mean Big trouble at Microsoft ( . Y . )


Recommended Posts

Some chucklehead working for Microsoft thought it would be funny to slip a thinly camouflaged sexist remark -- "big boobs" -- into software code that connects the Linux kernel to Microsoft's HyperV virtualization product.

Naturally, someone noticed -- that was the intent (snicker, snicker) - and, as should surprise no one, criticism has ensued, since the vast majority of grownups have come to recognize that this kind of juvenile nonsense has no place in the business world.

And, just as predictably, there are critics of the critics -- apologists and enablers for this chucklehead and others like him -- who insist on defending the non-existent right to be just a little bit sexist, even at work, as long as it's just a little bit and as long as not too many people notice or are offended. Lighten up, you nags, is the operative message from these folks.

Yes, still, in the year 2012.

Yesterday I asked Microsoft for comment and a public relations representative said she would seek one. (Update: It arrived 45 minutes after this posted and reads: "We thank the community for reporting this issue and apologize for the offensive string. We have submitted a patch to fix this issue and the change will be published in a future release of the kernel.") Here are the particulars of what happened.

Linux developer Matthew Garrett writes on his blog:

Paolo Bonzini
a little awkward in the Linux kernel support code for Microsoft's HyperV virtualisation environment - specifically, that the magic constant passed through to the hypervisor was "0xB16B00B5", or, in English, "BIG BOOBS". It turns out that this isn't an exception - when the code was originally submitted it also contained "0x0B00B135". That one got removed when the Xen support code was ripped out.

At the most basic level it's just straightforward childish humour, and the use of vaguely-English strings in magic hex constants is hardly uncommon. But it's also specifically male childish humour. Puerile sniggering at breasts contributes to the continuing impression that software development is a boys club where girls aren't welcome.

Piffle, harrumph the apologists, a number of whom contributed their tired rationalizations - "even my wife thinks it's funny" - in the comments on Garrett's post

Network World

Big Boobs by itself shouldn't even be deemed 'sexist'

  • Like 2

I don't quite see how this is offensive, it's not like he commented about a co-worker having big boobs or made an insuation that persons with big boobs are "insert some remark about people with big boobs". It's pathetic how easily people get offended.

*facepalm* Some people are just hypersensitive. It is not a big deal, just a little Easter egg.

Calling it sexist is not accurate either as it was not used in a statement, only by itself. It is like saying "Rainbow!" and then saying that it is derogative to LGBT people.

  • Like 2

#define HV_XENLINUX_GUEST_ID_LO 0x00000000
#define HV_XENLINUX_GUEST_ID_HI 0x0B00B135 /* #1 */
#define HV_XENLINUX_GUEST_ID (((UINT64)HV_XENLINUX_GUEST_ID_HI << 32) | HV_XENLINUX_GUEST_ID_LO)
#define HV_LINUX_GUEST_ID_LO 0x00000000
#define HV_LINUX_GUEST_ID_HI 0xB16B00B5 /* #2 */

This isn't an "easter egg", but it sure as hell it's stupid as one. Just another microagression.

Didn't Microsoft introduce a "no Easter eggs" policy about 5 years ago, because it technically represented undocumented code? I'm sure I read that...

Update: That was the OS division, as part of their "Trustworthy Computing" exercise.

  • Like 1

if women are offended by the word Big Boobs, then why do women get or want them

its along same lines of

" Stop Looking At My A**....... THEN STOP PUTTING WORDS ON THEM "

or

" Stop Looking At My Chest /My Eyes Are Up Here.... Then stop wearing your shirts open down to your Belly Button "

It's not an Easter Egg. It's just a pattern to determine if memory has been disturbed. Programmers have been doing this since the inception of hex.... 0xDEADBEEF, 0x0BADF00D, 0xEFEFEFEF... Whether you choose to be offended by it is up to you.

Here is a whole list of them if you wish to be angry for nothing: http://en.wikipedia.org/wiki/Hexspeak

  • Like 1

This was my response on the comment thread:

I like how "Mr. Big Boobs" , as the author puts it, is assumed to be a big pervert who has sex on the brain.

When I was in elementary school, we used to type out things like "5318008" ("boobies") on our calculator all the time. We didn't even really care what the word referred to, we just thought it was funny that we could spell it out in numbers on the calculator and thought the word "boobies" was funny. I don't think I'd ever put it in code, but if I did it would be out of nostalgia of my childhood and would have nothing to do with me thinking of a particular female body part.

If you really, really think this is a serious issue, go ahead and press on with it. Just don't be judgmental and form all sorts of prejudices about the guy who did it, all while decrying 'sexism.'

Stupid? Yes.

Sexist? No.

Stupid? No.

Sexist? No.

Corrected. I mean this is just ridiculous. Some of the open source code I've written has a lot worse and more offensive stuff in it. But "Big Boobs"? How the f*ck is that offensive in the slightest? :/

Clearly the author of the article is being homophobic by generalising that only men can be attracted or amused by such forms of humour. Where is the equal representation for lesbians?

Outrage! Fire the author! Make him homeless by not being able to get a job ever again!

Not angry or offended, just considered it an Easter Egg which reminded me of the no-eggs policy,,,

The ones you posted are all using 0-9A-F (Hex?), Does bigboobs conform?

It's not an easter egg in the relevant sense of the term. Someone just chose a very specific magic number, it's not code per se.

Would it be sexist if the code had B16BA115?

Maybe the code should have been written like this to keep it balanced:

#define HV_XENLINUX_GUEST_ID_LO 0x002B411S
#define HV_XENLINUX_GUEST_ID_HI 0x0B00B135 /* #1 */
#define HV_XENLINUX_GUEST_ID (((UINT64)HV_XENLINUX_GUEST_ID_HI << 32) | HV_XENLINUX_GUEST_ID_LO)
#define HV_LINUX_GUEST_ID_LO 0xB16BA115
#define HV_LINUX_GUEST_ID_HI 0xB16B00B5 /* #2 */[/CODE]

But then again, maybe that is derogatory to Transgendered people?

This topic is now closed to further replies.
  • Recently Browsing   0 members

    • No registered users viewing this page.
  • Posts

    • The fact that memory in general is so high I have to take a loan out to build a computer now is just beyond stupid. Who's really to blame here? Low supply or high demand?
    • Display Driver Uninstaller (DDU) 18.1.5.5 by Razvan Serea Display Driver Uninstaller (DDU) is a utility for completely removing AMD/NVIDIA/INTEL graphics drivers and related packages from your system, attempting to eliminate all leftovers (including registry entries, folders and files, driver store). Though AMD/NVIDIA/INTEL drivers can usually be removed via the Windows Control Panel, this uninstaller tool was created for situations where standard uninstall fails, or when you need to fully remove NVIDIA or ATI graphics card drivers. After using this driver cleaner, your system will behave as though it’s the first time you’re installing a new driver—similar to a fresh Windows installation. As with all such tools, we recommend creating a restore point beforehand, allowing you to undo changes if issues arise. If you're having trouble installing an older or newer driver, try it—there are reports that it resolves such problems. Recommended usage: The tool can be used in Normal mode but for absolute stability when using DDU, Safemode is always the best. Make a backup or a system restore (but it should normally be pretty safe). It is best to exclude the DDU folder completely from any security software to avoid issues. You do NOT need to uninstall the driver prior using DDU. Requirements: .NET Framework 4.8 Compatible with Windows 7, 8, 8.1, 10, and 11 (32-bit or 64-bit) Note: Using on Insider Preview builds is at your own risk. Display Driver Uninstaller (DDU) 18.1.5.5 changelog: Added 'Reset to recommended' button for the Options. General fixes and improvements. Download: Display Driver Uninstaller (DDU) 18.1.5.5 | 1.7 MB (Freeware) Download: DDU Portable | 1.2 MB Links: Display Driver Uninstaller Home Page | Screenshot Get alerted to all of our Software updates on Twitter at @NeowinSoftware
    • WACUP 1.99.51.24568 Preview by Razvan Serea WACUP (WinAmp Community Update Project) is a modern, enhanced version of the classic Winamp music player, designed for better stability, performance, and compatibility. Built for Windows, WACUP retains the familiar Winamp interface while adding 64-bit support, bug fixes, and new features like improved audio format support, customizable skins, and optimized playlist management. Unlike bloated alternatives, WACUP focuses on lightweight performance and regular updates, making it the best choice for fans of the classic Winamp experience. Basically, if you miss the good old days of Winamp and want a modern upgrade that doesn’t mess things up, WACUP is for you! WACUP key features: Classic Winamp Feel – Keeps the familiar interface and functionality. Bug Fixes & Stability – Fixes old Winamp issues and improves performance. 64-Bit Support – Works better on modern systems. More Formats & Plugins – Supports additional audio formats and third-party plugins. Customizable UI – Skins and tweaks for a personalized look. Better Library Management – Improved playlists, media organization, and search. No Bloat – Focuses on performance without unnecessary extras. Regular Updates – Community-driven development with new features and fixes. WACUP 1.99.51.24568 Preview changelog: Fixed a deadlock seen from the recent crash reports when doing some of the drag + drop actions within the media library window Fixed a loading crash seen related to a problem with some of the artwork cache image files being restored which should now be better handled allowing for the bad image to be removed without it failing Fixed a deadlock seen from the recent crash reports when the internal metadata cache clearing is triggered which could block the main ui thread for too long with this now being moved to a background thread Fixed some performance issues with some of the methods related to determining artwork support which mainly affected the local library import / refresh (this is still slower for some compared to other players because there's more data & artwork aspects being checked for which means doing more processing on a single file despite the best of attempts to reduce duplicate / heavy processing where possible) Fixed a crash with the JTFE based missing files hotkey which no one seems to have used for an age for this to appear (maybe it's time to seriously consider stripping out features that aren't being used) Fixed how some of the file types which use extra information to reference their sub-songs is handled which was preventing some from being correctly resolved back to their base file (noticed fixing above) Fixed an issue with the handling of files with underscores in their filepath which wasn't being correctly handled causing some of the filename to be lost when shown as the title if title reading is delayed Fixed a few things that might be behind NotSoDirect not being stable for some setups though am still not certain that the changes done for this are going to fully resolve the problem from the crash reports Fixed the OS toast handling when there's no prior shortcut in the OS start menu to now create the shortcut (needed to allow the yes/no buttons for the new build / post-release toast) to be done as a hidden one so it's less likely to cause annoyance for those not wanting to see it whilst still allowing this less than ideal OS api implementation requirement to be met to avoid toasts without the needed buttons Fixed a regression when moving from taglib1 to taglib2 which broke some of the handling in place to allow for external programs to still access files when wacup has a held open cached instance of the file Everything else Updated cppwinrt (gen_win10shell.dll) to 3.0.260520.1 (26 May 2026) Updated libcurl (libcurl.dll) to 8.2.1 (24 Jun 2026) Updated Monkey's Audio (in_ape.dll) to 13.15 (28 Jun 2026) Updated mpg123 (mpg123.dll) to 1.33.6 (6 Jun 2026) Updated OpenSSL (libcurl.dll) to 3.5.7 (9 Jun 2026) Updated pugixml to 1.16 (16 Jun 2026) Updated taglib (tag2.dll) to 2.3.0 (11 May 2026) Updated vgmstream (in_vgmstream.dll) to the latest Git commit from 28 Jun 2026 Download: WACUP 64-bit | 9.6 MB (Freeware) Download: WACUP 32-bit View: WACUP Website | Screenshots Get alerted to all of our Software updates on Twitter at @NeowinSoftware
    • "over a thousand engineering hours" and started selling it but could not take a couple of minuets to send an AI email to ask permission. What an expensive lesson.
    • just tested it yesterday, a simple page with autoloading ADS takes 60mb....just 1 page for 60 megabytes.   poor people with a limited internet never will visit neolose
  • Recent Achievements

    • Week One Done
      Collagen Project earned a badge
      Week One Done
    • Reacting Well
      Wakeen1966 earned a badge
      Reacting Well
    • Rookie
      Almohandis went up a rank
      Rookie
    • Apprentice
      jahara21 went up a rank
      Apprentice
    • Reacting Well
      NovaEdgeX earned a badge
      Reacting Well
  • Popular Contributors

    1. 1
      +primortal
      526
    2. 2
      +Edouard
      265
    3. 3
      PsYcHoKiLLa
      146
    4. 4
      Steven P.
      99
    5. 5
      macoman
      55
  • Tell a friend

    Love Neowin? Tell a friend!