tmp43522

I hate to depart from the group think, but there's another explanation aside from a smart engineer getting carried away with their own brilliance:

    They remarked how they spent a couple of days looking over the system which was complicated and creaky, they couldn't figure it out

Now it may be the case that they didn't really try to fix it and are just using that as an excuse, but OTOH, they may actually have been stumped despite best efforts.

If the system really did defeat this smart engineer's days of study, then in my opinion, and the opinion of at least one discussion I've seen on HN, the software should have been rewritten. (IMO) this really needs more clarification before scorn is passed.

No they're not that good, if the arrests are correct then they're actually pretty bad. For the little value that they are worth, they're worth far more as an example to be made for others.

It's actually not a bad suggestion

    #define BUF_INITIAL 1024
    char buf[BUF_INITIAL];
    
    int main(int argc, char** argv)
    {
        char* p;
        ...
        p = len > BUF_INITIAL ? malloc(len) : buf;
        ...
        write(1, p, len);
        ...
    }

So one of the first languages with closures to get huge mainstream popularity hasn't helped? right...

I've just ordered a beagleboard-xm, and though I was initially looking for an ARM computer purely for the sake of owning one, it now seems like the perfect device for use as a personal 24/7 internet server. Should only draw 10-15 watts when operational, hope it works okay!

I used to mv the old files, but now I just rm.

Host- specific files I handle by doing if [ -f ~/.host-bashrc ]; then . ~/.host-bashrc; fi

I also use proper extensions on my files like bashrc.sh and emacs.el for automatic syntax highlighting in editors.

My shell script just goes through the current dir turning eg. bashrc.sh into a link at ~/.bashrc

#define FALSE 0 is the common one