It improves my quality of life, that would be enough by itself. And
since I am doing this purely for my own satisfaction at the moment, I
*will not* waste my time screwing around with 60's tools because
somebody who is paid whether or not they work productively thinks they
imbue the kernel with some kind of airy-fairy zen quality.
Look, we tried the zen state thing. It didn't work. Think about the
madness in the period between 2.3 and 2.4, with one oops after another
reported to the list, each taking days or weeks to track down. Sure,
it allowed Linus and Al to show off their superior powers of cerebration,
solving the things given only a few lines of oops as a result, but it
sure fucked everything else up. As I recall, it wasn't fun at all in
the end, not for Linus or Al either, and some folks got pretty close
to burned out.
The answer to the question "is this sillyness slowing down development
and reducing the quality of the kernel?" is "yes". I don't have to
speculate about that any more, I've seen it enough with my own eyes.
Now ask yourself who the most productive hackers are today, and ask
yourself if they are using the good ol zen state blunt edged tools.
> Good thinking and coding does improve kernel quality. Debugger
> certainly does not help if someone cannot code.
Sorry, but you are full of shit.
-- Daniel - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/