Oops. I wasn't going to tell anyone this yet, but since you've made
this argument I feel I must be up front here....
After CML2 has proven itself in 2.5, I do plan to go back to Marcelo
and lobby for him accepting it into 2.4, on the grounds that doing so
will simplify his maintainance task no end. That's why I'm tracking
both sides of the fork in the rulebase, so it will be an easy drop-in
replacement for Marcelo as well as Linus.
> What are the precise issues with Python? Just claiming it is an issue is
> not useful for discussing this. Archive pointers are welcome.
The issues can be divided into two groups: silly and serious. The
representative silly objection was "Python is evil because significant
whitespace sucks!". Cristoph's objection to the use of a binary pickle
as an intermediate format is in this category also.
I heard two serious objections:
(1) The overhead of learning a new config language is too high.
(2) Requiring Python introduces another tool into the requisites list for
kernel building.
As to (1), the very people who maintained the in-kernel CML1 tools
judged that the overhead of sticking with what they wrote was
forseeably going to be higher than that of putting a new language in
place. Otherwise they would not have encouraged me to replace it when
I offered.
As to (2), I could make all kinds of elaborate defensive technical
arguments, or I could point at Greg Bank's CML2-in-C project, but
screw that. I'm just going to say "Today's problems, today's tools."
Progress happens. If you don't like it, feel free to go back to
writing Autocoder on your 1401.
-- <a href="http://www.tuxedo.org/~esr/">Eric S. Raymond</a>"The state calls its own violence `law', but that of the individual `crime'" -- Max Stirner - 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/