Women in Technology

Hear us Roar



Article:
  Is Linux Annoying?
Subject:   and here is the problem of any system, computer or not
Date:   2003-09-16 12:19:48
From:   anonymous2
Response to: The most serious problem with Linux Annoyances?

arrogance, plain and simple.


Starting out, it is stated that one has access to the source and therefore the ability to change/improve the annoyances. This is a good thing, it is a reminder of the inherant power of Open Source.


Then comes the 'tude. Gotta play that supposed trump card of "you only have your self to blame" topped of with the always useful loaded statement along the lines of blaming volunteers and everything that entails. (namely, that they don't 'owe' you anything and you should be thankful)


Logically this only makes sense if you ignore the inconsistency and hypocrisy.


No one is "blaming" the volunteers OR the paid folk working on various Linux products and packages. At least no one you should bother to listen too.


Consider this: If you decide there is a niche to fill then why not strike up your favorite editor and get busy? Sounds good right?


Now consider this: If you want to actually fix a problem in a elegant (read: not a sloppy, temp/hack fix) then you plan and gather input from others. This is what engineering and science is based upon, the methodical and consistent use of facts with ideas.


So, when someone identifies shortcomings (perceived or real), then a wise developer listens and does not react like a crying baby. Sure, that person did not do it themselves, but by identifying shortcomings or just requesting new features then the developers WITH the skill and experience then know something that they would not have considered on their own. Again, it is the difference between developers and bleeding, crying babies.


One thing that these crying babies also refuse to comprehend is that many times, these identifications of shortcomings come with solutions as well. Remember how I mentioned "perceived or real?" Well, that is the key here... perception. A perceived problem often does have a very workable solution (not work around) and merely must be discovered. Helpful developers and other good souls in the open source community will be glad to solve these problems through fixes or just better pointing out existing fixes in documentation.


Lose the attitude please, it reminds me of all the 1337 lusers that appeared on scene around 1996. No one needed them, and they certainly did not contribute anything but attitude and drive off many interested and talented, but unexperienced developers (and other help) from other areas of the world.


"...but uh that seems a bit lame"
Indeed. This is what I think everytime I see a "hacker" get on his high horse.


The wise developer knows to pick the right tool for the job. Each comes with certain strengths and weaknesses, and more so when you factor in the problem domain at hand. Linux and Open Source is good in many ways, IMHO better than anything closed source solutions have produced so far. Yet its contains its problems as well.


Throwing your hands in front of your eyes and loudly chanting "NYAH NYAH NYAH NYAH NYAH NYAH" doesn't change that.


Again I add... no one credible is laying "blame" on the great army of volunteers. If perhaps you have the time and skill to fix each and every problem then by all means run for dictator of the planet, as you are obviously superhuman.

Full Threads Oldest First

Showing messages 1 through 3 of 3.

  • and here is the problem of any system, computer or not
    2003-11-29 17:36:42  anonymous2 [View]

    Arrogance? I disagree.

    The poster just pointed that, with proprietary software (sometimes called "lock-in software"), you're at mercy of the software creator.

    With Open Source, you can fix it yourself. Or hire someone to fix the problem. Or wait untill someone fixes it.
  • and here is the problem of any system, computer or not
    2003-09-30 21:29:53  anonymous2 [View]

    Sometimes open source developers can be such lamers...I have had the misfortune of trying to work with a bunch of guys on a graphic installer. What a waste...We couldn't agree on group-management software (you know, something to track other people's effort, like Gant tables, etc), some guys refused to be "coordinated" (as in: use the *f***ing* software I'm telling you), and also stuff like scripting languages, that we couldn't agree on.
    This all happened because some of the guys had no formal training, or refused to learn, because they were very independent. So it's a kind of social issue that reflects on bad software design and coding practice that will eventually end-up in your 100th C bug of the week.
    When I see some software projects that are just replicating previous functionality I just think "what a waste."
    Nowadays, I will be carefull to install software that's been around for a while, and preferably being developed by large teams (like Gnome). I avoid, e.g., a mail package being coded by some 16 year old that barely knows C.
  • and here is the problem of any system, computer or not
    2003-09-17 22:25:12  anonymous2 [View]

    hmmmm

    Arrogance? Arrogance is a long pontificating message sent to an email list with "useability" rants and complaints about documentation.

    Been there? Done that? Been ignored?

    You type lots. Why not write some documentation and maybe your suggestions will have more weight.