Live data from Hacker News

PHP will switch to git

news.php.net

81–90 of 108 posts

Re: PHP will switch to git

#81
post #40

Earlier quoted context omitted.

I'm a pious hg user - even gave git a good run (mostly because of Github). I can't get over how amazing mercurial patch-queues are. Big win. I love mercurial's easy plugin development and hooks (thank you Python); I love how many awesome plugins exist for mercurial. On and on and on.

I'm pretty addicted to git's lightweight branching now. Mercurial looks appealing in some ways but, from what I understand, it doesn't support anything similar, at least not in the core.

You are thinking of Bookmarks, which have been a part of core since 1.8 and was an extension included with mercurial for a few versions prior.

Re: PHP will switch to git

#82
post #2

Rasmus gave a talk yesterday and I asked if they were switching to github. He said they'd likely switch to git (it's now happening, apparently), but not github because it can't do ACLs and the PHP project has thousands of people who need commit access to various places.

This sounds like a horribly broken development process to me. Is there any article that explains the idea behind this? I would really like to know how this could work.

Re: PHP will switch to git

#83
post #40

Earlier quoted context omitted.

I'm a pious hg user - even gave git a good run (mostly because of Github). I can't get over how amazing mercurial patch-queues are. Big win. I love mercurial's easy plugin development and hooks (thank you Python); I love how many awesome plugins exist for mercurial. On and on and on.

I keep seeing people talk about all the good of hg over git, but I haven't seen anything that really sets it apart. If you were doing a sales pitch, what would you show that hg has over git? What are some specific plugins that ease your development or release process? What are some real-world advantages of the hg patch-queue over how git handles pulls? I'm honestly curious. I just haven't seen anything to sell me on…

From the perspective of a longtime hg user who switched jobs and is now in git land: hg is easier to pick up and start using than git.

git lets you do incredible things with your tree, things that hg forbids or makes impossible. But git also lets you make big mistakes, and isn't very nice about helping you fix them.

hg, on the other hand, has a much nicer learning curve. As an example, try to forget everything you know about version control and type `hg help push` and `git help push`.

Which one would you be able to parse? Personally, when I read "The format of a parameter is an optional plus +, followed by the source ref , followed by a colon :, followed by the destination ref ", I want to punch a baby.

At the end of the day, if I want to transition a team away from SVN onto a DVCS, I'd pick hg -- just because it lets a team Get Shit Done without spending a ton of time learning a new VCS. But if I'm starting my own project? I'd pick git in a heartbeat.

Re: PHP will switch to git

#84
post #40

Earlier quoted context omitted.

I'm a pious hg user - even gave git a good run (mostly because of Github). I can't get over how amazing mercurial patch-queues are. Big win. I love mercurial's easy plugin development and hooks (thank you Python); I love how many awesome plugins exist for mercurial. On and on and on.

I keep seeing people talk about all the good of hg over git, but I haven't seen anything that really sets it apart. If you were doing a sales pitch, what would you show that hg has over git? What are some specific plugins that ease your development or release process? What are some real-world advantages of the hg patch-queue over how git handles pulls? I'm honestly curious. I just haven't seen anything to sell me on…

Besides the simplicity when starting to use a DVCS, i would add the simplicity for setting up a server (At least on Windows). There are a lot of organizations which need a centralized repo. And setting up mercurial for serving is a breeze. That's my 2 cents.

Re: PHP will switch to git

#85
post #60

The votes are a stark contrast to those of the core Python developers when they were voting on which DVCS to migrate to[1]—although understandably they favoured Mercurial, they disfavoured git. (Bazaar got a good share of votes as well.) The victor's margin was much smaller. This was all early-2009, though. I wonder if git's increasing popularity has swayed the core PHP developers? [1] http://www.python.org/dev/peps/…

Mercurial is written in Python - as a Python developer I can attest to the phenomenon of Python developers preferring software written in Python. Part of this is rational, part of this is pure "my tribe" bias (by the way, I use and like git, don't know Mercurial at all.) PHP developers are less likely to be affected by that.

To be fair, now there exist a library of git function written in pure python. http://www.samba.org/~jelmer/dulwich/

Re: PHP will switch to git

#86
post #41
post #24

Earlier quoted context omitted.

I went from 999 to 992. I guess I should have kept my mouth shut, but it was worth it. But tbh, I have nothing against PHP; it was just a joke.

Wow, I went from 999 to 964.. that's 35 down-votes! This is insane, but not surprising coming from PHP folks. (Too serious to laugh, too stupid to switch, too stubborn to think, too old to learn, amen.)

924, and continuing. That'll make a nice karma average. We see clearly the revenge of the PHP dumpshit.

Re: PHP will switch to git

#87
post #39
post #29

Earlier quoted context omitted.

Interesting. I was a barely competent sysadmin that couldn't contain my interest in learning how to develop software. So, over the last 6 months I messed around with Vim and Emacs/ Git, Hg, and Bazaar/ and Erlang, Ruby, Lua and Python. I settled on Emacs, Python, and Git; however, the only choice I made that was overwhelmed by popularity was the choice of learning a DVCS because that is a central piece of the functio…

Mercurial has quite a few merits! I like git but I like hg better. The main thing (to me) git has going for it, is GitHub. Even though BitBucket is getting better; it's still not GitHub.

OTOH, bitbucket has free private hosting and git doesn't (AFAIK). I think that is a crucial point for a beginner who is just learning to code and doesn't want to a) pay money, or b) have his ugly code be visible to the world.

Re: PHP will switch to git

#88
post #50

Earlier quoted context omitted.

> It's as simple to commit projects to github as it is to sf, bitbucket, google code, etc. Wait... you need to set up ssh credentials on github... sorry, it's more difficult to commit a project to github than it is to most of the alternatives. You can just as easily use it over HTTPS and use your github login (which is how a lot of SVN repos are setup). SF, BitBucket, Google Code, et. all are no easier or harder than…

To be fair, it's easier to commit to a project on Github. There's an 'edit' button, which lets you make changes inline on the website.

Google Code also has this feature.

Re: PHP will switch to git

#89
post #54

Earlier quoted context omitted.

To add further evidence toward your argument, consider also the alternative name, "svn": http://www.indeed.com/jobtrends?q=cvs%2C+subversion%2C+svn%2... The popularity would actually be the sum of both.

Not necessarily. Some entries might refer to both but be in the same entry. So the correct way to calculate totals would be `subversion + svn - (subersion and svn)`

The following link should provide the correct unions of job postings:

http://www.indeed.com/jobtrends?q=git%2C+hg+or+mercurial%2C+...

Re: PHP will switch to git

#90
post #39

Earlier quoted context omitted.

Mercurial has quite a few merits! I like git but I like hg better. The main thing (to me) git has going for it, is GitHub. Even though BitBucket is getting better; it's still not GitHub.

OTOH, bitbucket has free private hosting and git doesn't (AFAIK). I think that is a crucial point for a beginner who is just learning to code and doesn't want to a) pay money, or b) have his ugly code be visible to the world.

Don't be afraid to show your code to the world. Better yet, paste some in a pastebin and ask for tips in an IRC channel: it'll make you a better developer.
Post reply on HN