From: David Brown <git@davidb.org>
To: Frank Lichtenheld <frank@lichtenheld.de>
Cc: Alex Unleashed <alex@flawedcode.org>, Kyle Rose <krose@krose.org>,
Miles Bader <miles@gnu.org>,
Dmitry Kakurin <dmitry.kakurin@gmail.com>,
Git <git@vger.kernel.org>
Subject: Re: [OT] Re: C++ *for Git*
Date: Sat, 22 Sep 2007 23:25:27 -0700 [thread overview]
Message-ID: <20070923062527.GA8979@old.davidb.org> (raw)
In-Reply-To: <20070923020951.GF24423@planck.djpig.de>
On Sun, Sep 23, 2007 at 04:09:51AM +0200, Frank Lichtenheld wrote:
>On Sun, Sep 23, 2007 at 12:50:00AM +0200, Alex Unleashed wrote:
>> I'd say being forced to be explicit is a good thing here, so that the
>> programmer at least has some sort of good understanding of what is
>> going on, and chances are that if he doesn't really know, things just
>> won't work out (quite unlike a lot of other languages where this
>> programmer might actually end up with something half-assed that
>> "mostly" works).
>> For some reason it seems to me a lot harder to find bad programmers
>> surviving using C than a lot of the other languages.
>
>Idiot-proofness-by-complexity is a myth IMHO. Idiots can be quite
>persistent...
I work with plenty of them :-) It's all C. All of the same things happen,
with management looking for magic bullets to solve problems caused by bad
programmers.
Dave
next prev parent reply other threads:[~2007-09-23 6:26 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-22 10:42 C++ *for Git* Dmitry Kakurin
2007-09-22 11:11 ` David Kastrup
2007-09-22 12:48 ` Johannes Schindelin
2007-09-22 15:23 ` Marco Costalba
2007-09-23 4:54 ` Dmitry Kakurin
2007-09-22 15:15 ` Kyle Rose
2007-09-22 18:08 ` Miles Bader
2007-09-22 18:25 ` [OT] " Kyle Rose
2007-09-22 19:11 ` David Kastrup
2007-09-22 22:50 ` Alex Unleashed
2007-09-23 2:09 ` Frank Lichtenheld
2007-09-23 6:25 ` David Brown [this message]
2007-09-23 7:23 ` David Kastrup
2007-09-23 9:29 ` Marco Costalba
2007-09-23 9:42 ` David Kastrup
2007-09-23 9:50 ` Marco Costalba
2007-09-23 10:45 ` Pierre Habouzit
2007-09-23 13:42 ` Marco Costalba
2007-09-23 14:23 ` Nicolas Pitre
2007-09-23 14:45 ` Marco Costalba
2007-09-23 14:37 ` David Kastrup
2007-09-23 15:15 ` Marco Costalba
2007-09-23 17:49 ` Paul Franz
2007-09-23 16:54 ` Linus Torvalds
2007-09-23 18:05 ` Marco Costalba
2007-09-23 18:30 ` David Kastrup
2007-09-23 18:43 ` Marco Costalba
2007-09-23 19:11 ` David Kastrup
2007-09-23 21:22 ` Dmitry Potapov
2007-09-23 21:31 ` David Kastrup
2007-09-23 23:10 ` Robin Rosenberg
2007-09-23 22:25 ` Reece Dunn
2007-09-24 10:46 ` Dmitry Potapov
2007-09-22 22:24 ` Martin Langhoff
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20070923062527.GA8979@old.davidb.org \
--to=git@davidb.org \
--cc=alex@flawedcode.org \
--cc=dmitry.kakurin@gmail.com \
--cc=frank@lichtenheld.de \
--cc=git@vger.kernel.org \
--cc=krose@krose.org \
--cc=miles@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.