On 10/6/24 11:18 AM, Gavin Smith wrote:
Now imagine that half of DomTerm gets rewritten in Rust and then you
are scratching your head looking at a bunch of Rust code that you barely
understand when trying to fix problems in DomTerm. That's the situation
you are promoting for Texinfo.
First, compared to C++ to Rust, moving from C to C++ is much more modest of
terms of
code changes as well as new skills needed.
Right now DomTerm is a one-person project. However, suppose somebody cames to
me and says
"I love the concepts of DomTerm but I think it would be better (for whatever
reasons)
if it were implemented in Rust - and I volunteer to do the rewrite." If they
show
they understand the architeture and philosophy of DomTerm, and have
demonstrated Rust
proficiency, I would consider it. More likely if there was community and the
consensus
of the community was that we should re-write to Rust. I would be willing to
help with
and advise a Rust project, and gradually increase my Rust proficiency.
In the case of Texinfo and C++, it is quite different. We don't have anybody
strongly arguing for C++ who is also willing to do the work. We also have a
primary
maintainer who is strongly opposed to C++, and unwilling to work on C++ code.
So unless those things change, Texinfo will stick with C and Perl. And that's
OK.
--
--Per Bothner
p...@bothner.com http://per.bothner.com/
