Vote Up
-5
Votes
Vote Down
Dec 9, 2011 9:16 PM
12 comments

Basically a mathematical inverse of WorksForMe™. When a Winbred using WinbredHardware™ fails with GNU/Linux, the obvious conclusion is it must fail for everyone, and if anyone claims WorksForMe™ they are obviously lying or being a F$F $hill.

Posted from my Linux desktop that CantPossiblyWork™ but … does.

Related Trademarks

#1 Posted by garegin on Dec 9, 2011 11:58 PM

i just had the text line framebuffer fail on me on two different computers at work in the same day. the problem is not that there is no driver support. its the utter lack of standardization which causes “works here, but not there”. i also had the effing keyboard layout not working right in single user mode.
moreover linux utterly lacks the ability to do on fly fallback.instead of recognizing that I have a black screen because of broken KMS it just sits there. if i put windows and i have NO DRIVER SUPPORT i virtually always get (i’ve never seen it fail) graphics page.

#2 Posted by Gesh on Dec 10, 2011 5:17 AM

No, no, this is posted from your ass, which surely works. I mean look at all your logorrhea at this site. If you don’t know what this is, I think Kurkos can shed some light for you.

#3 Posted by administrator on Dec 10, 2011 6:08 AM

If it isn’t failing for everyone else, why the ridiculously low market share numbers? Oh, did Microsoft somehow trick everyone?

Good software speaks for itself. Desktop Linux is like a drunken uncle giving a speech at a wedding; It’s bombing!

#4 Posted by administrator on Dec 10, 2011 6:08 AM

Also, I didn’t realize your Linux desktop was running IE9, Adam.

#5 Posted by DrLoser on Dec 10, 2011 6:10 AM

See? He’s even got Wine to work! With apt-get-vista-service-pack, no less!

#6 Posted by DrLoser on Dec 10, 2011 6:11 AM

@Gesh:

Logorrhea? Isn’t that Calculus of the Semi-colons?

People can die from that, you know.

#7 Posted by administrator on Dec 10, 2011 6:13 AM

If you don’t check your semi-colons regularly you could terminate your life, er, line prematurely.

#8 Posted by Ian on Dec 10, 2011 10:25 AM

Wow, how did you get a DirectX fully hardware accelerated browser to work in Wine?

Did you do some LongPHPCodez?

#9 Posted by garegin on Dec 10, 2011 10:35 AM

i wish the kernel devs could see the light and understand that the problem is not the actual lack of drivers. its lack of standardization. the reason ALL hda sound chips work in vista and up is not because MS is a genious but because they implemelt the generic driver. the same generic hda implementation in linux fails ass.
the same reason why the fscing VESA driver throws scrambled garbage on many computers. i swear this is like children writing software.

#10 Posted by Adam_King on Dec 10, 2011 11:02 AM

Administrator,

Not even close. You might want to recheck your browser sniffing code.

#11 Posted by DrLoser on Dec 10, 2011 11:59 AM

@Adam:

Oh, that’s right: it was Big Sis’ IE8, wasn’t it? Admin has corrected me on this very significant point in the past.

Very commendable, kid. Go suck a lollipop.

#12 Posted by Gesh on Dec 10, 2011 3:48 PM

@DrLoser

You are damn right, people can die from that. :)

You must be signed in to leave comments.