[Coco] toolshed under Linux

[John W. Linville]

Yeah, that about sums it up -- good job! :-)

Mercurial and git originally had similar feature sets. They were
developed around the same time under about the same sets of influences.

Over time, git got a lot more use, more development, more features,
etc -- the virtuous cycle of open source.

Mercurial...well, notsomuch...Bitbucket is even ending support for
it, FWIW.

	https://bitbucket.org/blog/sunsetting-mercurial-support-in-bitbucket

The main reasons to use Mercurial today would be either personal
preference (i.e. you don't care about recruiting developers), or just
momentum (i.e. should have stayed with CVS years ago).	The reasons
not to use git today? I can't think of any good ones.

Just my $0.02...

John

On Thu, Apr 23, 2020 at 04:09:27PM -0700, Andrew wrote:
> Just wanted to weigh in on this:
> 
> >> Also, why are we still using mercurial??
> 
> My 2 cents:
> 
> TL;DR: Git and github are the most popular and widely used; virtually every
> software engineer has used them, other tools notsomuch...
> 
> --- Longer Version Below ---
> 
> I don't know anything about mercurial myself; I've never used it, so I will
> refrain on saying anything about its pros or cons.
> 
> But the software engineering world has almost (seemingly) standardized on
> using git (and github by extension - gitlab is also an option).
> 
> Now - I know that toolshed and other CoCo projects aren't really a part of
> the common "software engineering" space; these are all retro projects
> maintained by a small number enthusiasts. So maybe it doesn't really matter
> what versioning tool is used...
> 
> ...until and unless another maintainer has to take it over.
> 
> That new guy may or may not have mercurial or ever used it - but it is
> almost guaranteed that they have used git and/or github. Git (and github)
> are almost default tools in a developer's toolchain at this point. If they
> weren't, you'd see "mecurial-hub" or something like that making inroads and
> taking business away from github. But you don't, because it isn't...or
> something like that.
> 
> Yes, I guess I'm arguing for popularity and commonality; not the best
> argument. As a professional (though currently jobless) software engineer, I
> almost expect any serious project (which I think toolshed is) to be
> available on github, if it isn't proprietary (and especially if it is
> open-source). I expect to be able to make changes and pull requests, etc -
> and to continue to use the tools I know. I have never worked at an employer
> that used anything other than git and/or github. I know there are plenty of
> employers that don't use those tools, but I suspect they may be in the
> minority (just a gut feeling - I have nothing to back that up).
> 
> 
> On 4/23/20 2:44 PM, coco-request at maltedmedia.com wrote:
> > Message: 8
> > Date: Thu, 23 Apr 2020 16:36:00 -0500
> > From: Allen Huffman<alsplace at pobox.com>
> > To: CoCoList for Color Computer Enthusiasts<coco at maltedmedia.com>
> > Subject: Re: [Coco] toolshed under Linux
> > Message-ID:<1E77411B-1F9B-42D0-B124-C2722857B2F2 at pobox.com>
> > Content-Type: text/plain; charset=utf-8
> > 
> > > On Apr 23, 2020, at 2:45 PM, John W. Linville<linville at tuxdriver.com>  wrote:
> > > 
> > > Also, why are we still using mercurial??
> > What would you suggest? (If you say git, that’s nice because I know it. No so much anything else.)
> 
> -- 
> Andrew L. Ayers
> Glendale, Arizona
> https://github.com/andrew-ayers
> https://www.phoenixgarage.org/
> 
> 
> -- 
> Coco mailing list
> Coco at maltedmedia.com
> https://pairlist5.pair.net/mailman/listinfo/coco

-- 
John W. Linville		Someday the world will need a hero, and you
linville at tuxdriver.com			might be all we have.  Be ready.