← Back to Female Bashing Jokes

Female Bashing Collection 3

Smartest Hair Color

Three dumb blondes were shipwrecked on a desert island. They came across a magic lamp and a genie came out. The genie said that he would grant them each a wish.The first blonde asked to be made smart, the genie turned her into a brunette and she swam off the island. The second blonde asked to be even more smarter, so the genie turned her red hair and she built a boat and sailed off the island. The third blonde asked to be made the smartest, so the genie turned her into a man and he walked onto the bridge, and off the island.

What Men Should Never Say After Sex

1) "I was kidding about being sterile, you know." 2) "Do you always fart like that when someone shoves it in?" 3) "How come it's so BIG in there?" 4) "You've done this with a lotta guys before---right?" 5) "Next time I come over, don't bother with the underwear, OK?" 6) (Sniff, sniff) "Is that CAT food?" 7) (Yelling) "OK guys, it's a wrap, cut, and print it!!" 8) "You are great in bed, but your sister gives better head!" 9) "My first wife was prettier, but you can screw a lot better." 10) "Do you know what a 'douche' is ?" 11) "Maybe if you did some pushups, your boobs would grow. 12) "I want you to try some of MY deodorant." 13) "I'm not into relationships. Can't we just screw, like every Tuesday night or something?" 14) "Maybe if you lost some weight, I could get it all the way in!" 15) "I never saw a girl with hairy tits before !" 16) "I've been getting these little blisters lately-------" 17) "You wanna do those dishes before you leave ?" 18) "You should go wash that, the cabbie will think something DIED in there!"

Girlfriend 5.0

Desperately seeking technical support! I'm currently running the latest version of Girlfriend 5.0 and having some problems. I've been running the same version of DrinkingBuddies 1.0 for years as my primary application, and all the Girlfriend releases have always conflicted with it. I hear that DrinkingBuddies won't crash if you minimize Girlfriend with the sound off, but since I can't find the switch to turn it off, I just run them separately and it works OK. Girlfriend also seems to have a problem coexisting with Golfware, often trying to abort my Golf program with some sort of timing incompatibility. I probably should have stayed with Girlfriend 1.0, but I thought I might see better performance with Girlfriend 2.0. After months of conflicts, I consulted a friend who has experience with Girlfriend 2.0. He said I probably didn't have enough cache to run Girlfriend 2.0 and eventually it would require a Token Ring upgrade to run properly. He was right. As soon as I purged my cache, Girlfriend 2.0 uninstalled itself. Shortly after that, I installed a Girlfriend 3.0 beta. All the bugs were supposed to be gone, but the first time I used it, it gave me a virus. After a hard drive clean up and thorough virus scan I very cautiously upgraded to Girlfriend 4.0. This time using a SCSI probe and virus protection. It worked OK for a while until I discovered Girlfriend 1.0 wasn't completely uninstalled! I tried to run Girlfriend 1.0 again with Girlfriend 4.0 still installed, but Girlfriend 4.0 has an unadvertised feature that automatically senses the presence of Girlfriend 1.0 and communicates with it in some way, resulting in the immediate removal of both versions! The version I have now works pretty well, but, like all versions, there are still some problems. The Girlfriend package is written in some obscure language that I can't understand, much less reprogram. And I've never liked how Girlfriend is totally 'object-oriented.' A year ago, a friend upgraded his version to GirlfriendPlus 1.0, which is a Terminate-and-Stay resident version. He discovered GirlfriendPlus 1.0 expires within a year if you don't upgrade to Fiance9e 1.0. So he did. But soon after that, you have to upgrade to Wife 1.0, which he describes as a 'huge resource hog.' It has taken up all his space, so he can't load anything else. One of the primary reasons that he upgraded to Wife is because it came bundled with FreeSex 1.0. Well, it turns out that the resource allocation module of Wife 1.0 sometimes prohibits access to FreeSex (particularly the new Plug and Play items he wanted to try). On top of that, Wife 1.0 must be running on a well warmed-up system before he can do anything. And, although he did not ask for it, Wife 1.0 came with MotherInLaw 1.0, which has an automatic popup feature he can't turn off. I told him to install Mistress 1.0, but he said that he heard that if you try to run it without first uninstalling Wife, that Wife 1.0 will delete MSMoney files before uninstalling itself. Then Mistress 1.0 won't install anyway, due to insufficient resources. If anybody out there is able to offer technical advice...

Upgrade Girlfriend

Last year, my friend upgraded his GirlFriend 3.1 to GirlFriendPlus1.0 (marketing name: Fiancee1.0). Recently he upgraded Fiancee1.0 to Wife1.0 and it's a memory hogger, has taken all his space; and Wife1.0 must be running before he can do anything. Although he didn't ask for them, Wife1.0 came with Plug-Ins such as MotherInLaw and BrotherInLaw. Some features I'd like to see in the upcoming GirlFriend4.0. - A "Don't remind me again" button - Minimize button - Shutdown feature - An install shield feature so that Girlfriend4.0 can be completely uninstalled if so desired (so you don't lose cache and other objects) I tried running Girlfriend 2.0 with Girlfriend 1.0 still installed, they tried using the same I/O port and conflicted. Then I tried to uninstall Girlfriend 1.0 but it didn't have an uninstall program. I tried to uninstall it by hand, but it put files in my system directory. Another thing that sucks -- in all versions of Girlfriend that I've used is that it is totally "object orientated" and only supports hardware with gold plated contacts. ***** BUG WARNING ******** Wife 1.0 has an undocumented bug. If you try to install Mistress 1.1 before uninstalling Wife 1.0, Wife 1.0 will delete MSMoney files before doing the uninstall itself. Then Mistress 1.1 will refuse to install, claiming insufficient resources.