Article discussing Go, could well be D

Nick Sabalausky a at a.a
Wed Jun 8 23:56:38 PDT 2011


"Adam D. Ruppe" <destructionator at gmail.com> wrote in message 
news:isovu6$21k6$1 at digitalmars.com...
>I find it interesting that so many people complain about the lack
> of libraries.
>
>
> software library: a way to waste a programmer's time
>
> reinventing wheels: a lie some programmers, who are paid by the
> hour, perpetuated so they can justify the "use" of software libraries
>
> The project could have been done in one day if he just sat down and
> got to work. Instead, he made up some bullshit about how reinventing
> wheels is bad.
>
> Thus, he now spends 3 days searching for a library. Another 5
> days trying to make it work. Another 10 days reading the
> godawful documentation. A day bitching about the suckiness on the
> internet.
>
> Then, finally, two days to integrate the library into his project.
> For bonus points, force the end users to install it too, because
> the more time wasted, the better.

Yup. There's definitely a lot of cases where pre-made libs are a huge help 
and a much better option, but I've gotten really fed up with the Anti-NIH 
Holy Crusaders, largely for the reasons you stated above. (Another good 
reason to actually embrace NIH-syndrome instead knee-jerking away from it 
out of principle is for mission-critical things where you can't afford the 
possibility of being left at the mercey of some outside group.)

What you said above is also why I *strongly* believe that good (and I mean 
*good*) documentation is every bit as important as actually 
writing/releasing a tool or library in the first place. I've seen so much 
"already-made" work that's rendered barely-usable due to less-than-stellar 
documentation (or even worse: bad or non-existant documentation). What's the 
point out of putting stuff out there if nobody knows how to use it? What's 
the point of using something if figuring it out and getting it to work takes 
about as much effort as DIY? That's why (for public projects anyway) I force 
myself, even if I don't want to, to put all the effort I need to into 
documentation to make things as easy as possible. Otherwise, all that effort 
writing the code would likely have been for nothing anyway.






More information about the Digitalmars-d mailing list