Fucking Open Sores BAWWWWWWWWing

http://tech.slashdot.org/article.pl?sid=08/04/30/1822237

Linking to Shitdot since Pidgin's ticket system is currently experiencing raep up the anus.

I swear, Pidgin has some of the biggest assholes in open sores I've ever seen.

The fun part is that both sides are wrong.

libpurple is fucking shit. I wish the Adium guys didn't use that, they actually have a decent client, that gets ruined with bugs that come from libpurpose.

Don't worry, IM will be replaced by twitter anyway, and desktop applications by Javascript.

Couldn't aggree more OP. The Gaim/Pidgin are total assholes. Hopefully this fork can survive, this popularity is a good start.

FACT: Almost all the open-sores developers with a serious attitude problem hang around the GNU/Gnome/GTK/Gimp world.

This gets to the heart of why open source is shit.

These apps get forked all the time. Resources are split and hardly shared.

So you end up with less people in different little groups tackling the same problem different ways with disparate management of the resources.

The end result, many apps with vast similarities approaching the same problem. But none of the apps do it well.

What's the news? A project makes a technical decision. Many users become vocally opposed to it. Fork of the project ensues. I don't see what's the problem here.


                                     ,--------------------------------------,
                                   /                                         `-,
                                 |           THEY COULD HAVE FUCKING            \
                                |              ASKEDME ABOUT IT FIRST           |
               `,``         |````..                                              |
            ,,````          |       ``\,FUQIN RAGE                   |
             _..-'',        |'`'`'`'`'``-`\,                                     |
          ,-/      |        |               `-,                                  |
       ,-/         |        |                  -,                                |
      /       __.. |        |                    `,                              |
     /     ,'     `|        |-,               ,-'`-,                             |
     |    |        |        |  |             |      |                            |
     \    |    P   |        | /              `, P   |                           ,/
     |     `,     ,|        |,                 `---'                          ,/
     |       ```'' |        |     ,___/\___,       /----------,     ,,/------'
     |            .|        |,____`_/    \_'___,  /           | ,,/'
     |             |        | `__            _/  /            |/
     |             |        |     `-_______-'    |
    /              |        |                    |
   /               |        |                    \,
  /                |        |                      `\,,
 /                 |        |                          `--,
,                  |        |                             ``,
`,                 |        |                                 \
  `----------------'        `--------------------------------/'

>>9
I _L^O_L'^d.

>>9
M-x artist-mode

>>10
I don't get it, but at lease I invented that^[1] meme.


^[1]>>11

>>1
insipid /g/ cliches?  in my /prog/?

hax my anus

open sores
go back to /g/

Seriously. We are /prog/grammers. Most of us use either linux or bsd. Most of the time we release the sources naturally, to allow other people to compile them in their own obscure architecture. The only exceptions are ENTERPRISE and faggots are here just for the memes.

>>13,15
lol wut?

OP here.  I don't even go to /g/; I just call it "open sores" to agitate FAGGOTS like you who suck GNU/Dick.  I'm pro-open source, albeit anti-open sores control-freak "we-know-what's-best-for-our-users" faggots like Pidgin's developers.  I think >>6 is probably right.

>>1,16
3/10
If you wanted to troll those that align with the FSF, you would have confused gratis with liberty. Ergo your wrong bitch.

>>6,16
I like gtk, motherfuckers.

>>18
GTK hates you.

Wow, what the fuck. If the source is so goddamn open why don't you just fix the bloody thing yourself!

>>20
That's exactly why I questioned the newsworth of this story.

>>20
I hate that fucking argument. If a crappy open source program breaks, it's the developer's fault, not mine. Just because the source is available it doesn't make it my problem, in the same way terrible food isn Now, if it's shit, why the fuck would I want to touch crap?

Also, open sores is a /g/ meme? How shitty. It used to be popular among troll circles a few years ago.

>>8
The issue here is that this whole thing can be fixed by adding an option to the preferences pan. You know, I'm fucking sick and tired of developers removing options from preferences because they claim too many option confuse users. No, you dumbfuck shits, it doesn't make it any more “usable”. IT'S A FUCKING PREFERENCES PANE, no one goes there unless they're specifically looking on how to turn on/off something! Now in order to use your shit software, I have to weed through cryptic variables in about:config. How the fuck is that any more “usable”?

in the same way terrible food at someone's else house isn't my problem just because I happen to have the recipe.

How the fuck did I forget to finish that sentence?

>>23
But in this case, you can actually fix it yourself. I am assuming you know programming... or know enough to add the relevant lines of code that were removed.

>>24
It was fixed by the guy who started the “funpidgin” fork. It's a trivial change in only one of the files.

I don't even use Pidgin because I'm not an homosexual, so I really don't care.

>>22
You know, I'm fucking sick and tired of developers removing options from preferences because they claim too many option confuse users

It's weird, but particularly pidgin developers have strong opinions againist "preferences". Adding the crappyness of libpurple (I can hear some butthurt patch submissions in this thread...) is enough to justify a fork. Because forks are that: the result of incompetent project managers.

Too bad the reason to fork is shitty and who did it is a fucking noob. There's no future for libpurple. They'll die slowly with telepathy.

>>26
I wish Adium developers stopped focusing on code testing industry best practices and forked libpurple. All the Adium bugs I care about are stuck waiting on libpurpose to get fixed.

if a crappy open source program breaks, it's the developer's fault, not mine.
PROTIP: Any computer program designed to be distributed to the general public is likely to be inadequate/broken to somebody.
PROTIP: If a free program does not work how you want it, it is up to you to get it fixed.

>>28
YHBT

>>22
if it's open source and you're using it, you're the developer.

Can anyone explain why libpurple is shit?

>>28
Go back to bed, Linus. It's like 4 am sweden time.

>>32
he lives in cali

>>28
>>30
No, it's not. I hate it when free software developers give me this shit. Just because I use it for free it doesn't mean I have to fix it. What if I'm not proficient with the methods they used? What if I don't have the time? What if I simply don't want to because I have better stuff to do?

Free software, in the end, is just fucking software. Having access to the source is a BONUS, it means that you're able to modify and extend the program if you want, it's not a contract saying that you're also responsible for the development of said program. Using a piece of open source software doesn't mean I'm required to take responsibility for the developer's stupidity or endorse the software's code and frankly, you're stupid if you think that way. Sure, I cannot demand anything from the developers or sue them if the software formats my hard drive, I'm perfectly aware I'm using it on my own risk, but if the software misbehaves it's still their "fault" in the moral sense.

I don't know about you, but when I develop something, I feel responsible if the software misbehaves and try to listen to whoever is using the software even if I give out the source for free. Exceptions, of course, are when I write a hack and give it out to someone with the explicit notice that "I don't give a shit if this breaks, YMMV." Are you telling me most open source projects work on this basis?

I'm not arguing that open source developers should do whatever I ask them to. If software doesn't do what I want, I can either file an enchantment bug and be patient or extend it myself. When WAHa tells me to fuck off when I suggest a new feature in Xee? That's perfectly fine, I'm asking about something new, his software is fine, it just doesn't do something I wanted it to.

What it does piss me off are some attitudes open source developers have toward bugs and regressions. Some examples include:
- Software breaks spectacularly, and by that I mean that is completely rendered unusable. Or maybe it was never usable in the first place. Developer cries "Fix it yourself!" At this point, anyone sane just forgets about it and goes use something else, since it's obvious it's never going to get usable anytime soon. Examples include GNU HURD.
- Software has a small bug that is trivial for the developer to fix, but he chooses not to out of stubbornness and cries out the standard "It's open source, fix it yourself!", forcing people who are not familiar with the code waste hours reading source while it would have taken the developer several minutes to fix it. Sure, it's great you're letting us play with your ball for free, but do you really have to be an asshole about it? Examples include >>1.
- Software breaks spectacularly (rendered unusable). The developers fix it, commit to svn and then just sit on it for extended periods of time. They refuse to release beta or unstable builds or let users update. Oh sure, I can compile it myself, but you know the friend I recommended your software to? I'll just tell him to use something else. I am fucking looking at you, Perian. When QuickTime updates break your shit, you insta-fix it but then you take months to release a build. If it's too unstable to release, it really that hard to backport a somewhat simple fix to $STABLE_VERSION and release a quick update for your users?

Don't get me wrong, I love open source and free software and I contribute to some projects occasionally, but the number of people on /prog/ that suck RMS's cock to the point of sounding like RMS himself is appalling.

QuickTime
comments rendered useless

>>35
Perian is a Quicktime component for OS X. A shitty one, but still. It's only somewhat useful because MrVacBob-sama himself bothered to implement ASS support for it, but MKV import loading times and shit breaking with each Quicktime update, there's no reason for anyone to not use mplayer instead.

>>34
Who says you have to personally eyeball any line of free code? Nobody! The thing about free software is that the user has the right to help themselves! Any computer program designed to be distributed to the general public is likely to be inadequate/broken to somebody. What we're saying is that you (the user) should take control of your own computing by identifying requirements that is currently unfulfilled by your software then initating action to get that program fixed.

Computer code is not going to change itself; you need to find a programmer to fix it for you. If you can change it yourself, then so be it, go tinker with that code. If you can find a community willing to cooperate (with the common goal of moving towards a certain direction), then so be it, go join that community. If you are unable/unwilling to actually study and tinker with the code the last option you have is hire a professional programmer.

If you can find a community willing to cooperate (with the common goal of moving towards a certain direction), then so be it, go join that community.
I forgot to add that nobody in that community is obligated to fulfill your requirements. It would be fine if the community does fulfill your request. However, there is zero guarantee for this to happen so you should not expect any guarantee to be helped by your community. Instead, you should invest your own resources to get any inadequacies fixed.

>>38
Correct, sir. I love these guys expecting developers to be ENTERPRISE as if they give a crap. The developers got into working on the project because they like to code and work on something that interests them; not pander to the needs of people who they happen to share it with. ``I won't use your product!!!!'' -- oh, shit, now I don't get paid? OH WAIT-

I can't imagine how rewarding it must be to write free software for obsessive nerds with entitlement problems.

As rewarding as haxing an old anus.

>>37
Free as in you have to hire a personal developer to keep your copy running.

>>42
or just learn programming

>>43
and just memorize every piece of code you use anywhere

>>43
lol societal advancement through specialization in different trades so that we can be more than an agrarian society

>>45
computers are getting more and more common. maybe in the future programming will become a required course for everyone to take like math is today.

Well, that's, just, like, your opinion, man.

>>42,43,46
Economically equivalent.

>>42
That's exactly right, you are free to remain autonomous. Autonomy is not possible without freedom 0 and freedom 1. Without both those freedoms, the user has to obtain permission to the master for help - and here is the major protip: There is no guarantee for any master to permit users to help themselves. Thus, the user loses autonomy over their own life whenever they depend upon proprietary software.

>>49
Exactly.  I'm free to be forced to remain autonomous.  Forced autonomy is not possible without smug open-source assholes refusing to make their code work right.

>>50
I don't understand what your trying to say.

Has someone called me?

　　 ___　　　　○(ﾟ∀ﾟ；)
　／◎＼……C｜　 ＼
　　　　　　　　　　∧
／￣￣￣￣￣￣　￣￣￣￣￣￣￣￣￣￣￣￣￣￣
| Helo >>52, I just caled to say your a fagort.
＼＿＿＿＿＿＿＿＿＿＿＿＿＿＿＿＿＿＿＿＿＿

>>53
I'm free to be forced to remain fagort, then

...now with tripcode!

>>54,55
Go away.

>>54,55
I hope this faggot's anus gets haxed

bampu pantsu~~

*grabs dick*

62 Name: Sgt.Kabukiman壘㖐 2012-05-23 4:34

鈋鳕﹁ퟐ넺︸㚯愎䃹