Re: Tree-sitter maturity

[Eli Zaretskii]

> Date: Sat, 04 Jan 2025 15:46:49 -0500
> From: Daniel Colascione <dancol@dancol.org>
> CC: owinebar@gmail.com, bjorn.bidar@thaodan.de, philipk@posteo.net,
>  emacs-devel@gnu.org, rms@gnu.org, manphiz@gmail.com
> 
> >> And it creates the need to do code distribution in a bespoke way. How is 
> >> that a net win?
> >
> >It's _our_ win.  The problem is shifted to the distros, where I think
> >it belongs.
> 
> No, it isn't, because distros *can't* do a good job of this.

Then they need to get their act together and improve.

> Besides: plenty of people (I'd guess a majority going by how the industry is 
> set up) were using Emacs outside the context of a distro. If we weren't 
> allergic to telemetry, we'd know.

People who do that (I'm one of them, btw) can build their grammars.  I
do.

> >> Nobody has been able to describe these legal aspects. Grammars are free 
> >> software. GPL compatible, too.
> >> That means we can put them in Emacs. That's what software freedom means.
> >
> >I did explain that, and don't want to repeat.  You can consider those
> >reasons unimportant, but I don't (and cannot, really: I don't call the
> >shots in this particular game).
> 
> No, you didn't explain. You asserted.
> 
> You said that we would need to get written permission from grammar projects 
> to include their code in Emacs. When I asked where this requirement comes 
> from, you said it had always been this way and that RMS might have more 
> information. He appears not to.

RMS explicitly asked me to do that for every package we admit into
Emacs.

> >You are missing the point.  My point is that several branches means we
> >need to match a different version of the library to each branch
> 
> If you check the grammar into the tree, the version in each branch matches 
> that branch automatically. That's what a version control system is. It's the 
> essence of what it does. Same goes for submodules, which are just checked-in 
> pointers.

Again, you are missing the point: we need to find an appropriate
version for each branch, and we need to track the versions of the
grammar so ass to be able to know, for each of our branches, the
compatible version of the grammar.  The maintenance burden is
multiplied by the branches.

> Can you give me a concrete example of how checking in code burdens branch 
> maintenance? Your position isn't making any sense to me in context of how 
> version control systems work.

Finding the matching version and testing whether it matches does.

> >> >The difference is that the RI changes.  And that's not something to
> >> >ignore, from where I stand.
> >> 
> >> Huh? In what possible way could a bespoke downloader be a better 
> >> engineering choice than submodules?
> >
> >I didn't say anything about engineering, I was talking about the
> >responsibility.
> 
> Good engineering minimizes the number of moving parts and needless failure 
> points in a system.

Responsibility has nothing to do with engineering or moving parts.