Re: Source code, git and cvs

[uzibalqa <uzibalqa@proton.me>]

Sent with Proton Mail secure email.

------- Original Message -------
On Friday, July 21st, 2023 at 7:12 AM, uzibalqa <uzibalqa@proton.me> wrote:


> 
> ------- Original Message -------
> On Friday, July 21st, 2023 at 6:31 AM, Eli Zaretskii eliz@gnu.org wrote:
> 
> 
> 
> > > Date: Thu, 20 Jul 2023 17:33:41 +0000
> > > From: uzibalqa uzibalqa@proton.me
> > > Cc: help-gnu-emacs@gnu.org
> > > 
> > > > > README should describe both immediately at the start. Not just about
> > > > > installing from the tarball.
> > > > 
> > > > We clearly disagree.
> > > 
> > > Of course, hide it and make things more difficult for new users. And then
> > > expect them to figure out things by themselves. And when they ask questions,
> > > never be straightforward and give them the code they need to use. It is their
> > > job to go through the ever increasing obfuscation of information embedded within
> > > deeper and deeper levels of cyclomatic complexity. Classic example of development
> > > malpractice.
> > 
> > You should stop your arrogant and rude remarks about project practices
> > that you just learned yesterday. It is not wise, to say the least, to
> > show your ignorance by claiming you are right even after you have been
> > pointed to your mistakes and stuff you missed in the docs.
> 
> 
> Yes, I am right, you are wrong.
> 
> > The README, INSTALL, etc. files in the top-level directory are the
> > result of many years of experience and many users contributing to
> > them, they are not just random text that was written yesterday and
> > therefore needs to be polished. It's already polished, so any change
> > you suggest based on 5 sec of thought is more than likely to have
> > downsides that were already considered and rejected in the long
> > history of Emacs development.
> 
> 
> Typical nonsense.
> 
> > You have ample opportunity to exercise some humility and learn (and
> > you have a lot to learn, believe me) before you get to the position
> > where you might "know better", and have the moral right to teach us
> > what is "malpractice". Suggest to use that opportunity.
> 
> 
> I just look at things how they are, so one can effortlessly navigate
> through the material. There is no need to be humble and I definitely
> have the autonomy to take action without approval or authority. I am
> certainly not bound by any requirement of external validation or permission
> to do so.

At one time you stated that one of the gravest problems you see for the future 
of Emacs development is that we slowly but steadily lose old-timers who know a 
lot about the Emacs  internals ... If this tendency continues, we will soon lose 
the ability to make deep infrastructure changes.

Yet you continue to refuse spending effort on making sure that future developers 
will be able to learn quickly.  But the direction I usually get is to work hard.  
The reality is that hard working people fail.  We complain about everything in life
because we're doing everything hard.  Once your intelligence has turned against you,
there is no power in universe that can save you, that's all.

The solution is not about adding more and more stuff but having a compact enough 
commentary that people would be willing to spend reasonable time on compared to 
the time taken to complete some task.  If that takes too long or requires too much
jumping around, the project is history.  Worked with companies like that, they are 
all gone.