I still remember a couple years ago I wanted to contribute to Chromium. I took one look at the build instructions and decided I didn't want to contribute that badly...
If you haven't followed the drama, here's ESR's take:
The key paragraph:
We lost sight of what mattered for our users, focusing on features that were nice but perhaps not as necessary as we thought. We overengineered. We didn't get rid of the crufty unnecessary features. It's harder to comprehend, contribute to or fix performance issues in a large layered codebase. And the larger a codebase becomes, the larger the surface for bugs, the harder it is to refactor.
% host www.stationary-traveller.eu
Host www.stationary-traveller.eu not found: 2(SERVFAIL)
In fact, I think I have something, because dig www.stationary-traveller.eu +trace seems to work: http://stackoverflow.com/questions/12025173/dig-returns-serv...
My resolv.conf is just 220.127.116.11 and 18.104.22.168 so I'm pretty sure this is affecting others. OpenDNS resolves it, though:
% nslookup www.stationary-traveller.eu 22.214.171.124
www.stationary-traveller.eu canonical name = aurelia.vernstok.nl.
aurelia.vernstok.nl canonical name = aurelia.jelmer.uk.
> EDIT,fixed: The CAUSE was that /etc/named.conf had no zone set for that domain. and also there was file for "DB record" missing in /var/named/domain.com.db file. This manual fixed it: http://kb.iweb.com/entries/21155058-Adding-new-domains-to-DN...
just ideology? I would have expected most individuals in position to be doing development work in 2014 to have a little more ram than this.
Not knocking your opinion as I will admit to being a bread plebeian, but wow.
My housemates (in London) are from Palestine, Poland, Romania and Hungary, and in average British terms all count as bread elitists. None can understand why the squashy, tasteless, white bread is popular here, and struggle to understand why people would buy crap bread, of all things!
To understand the question, you need to know that if you buy a bread product in a Chinese bakery, there will be some sort of filling -- beans, a hot dog, anything -- hidden in the middle (well, a hot dog will usually stick out visibly on either side).
When I replied that bread is bread all the way through, there was a followup question: "If it's all just bread, how can one bread be different from another bread?"
It was hard to know how to respond. Different breads taste different. Some are high-quality, some are low. People aren't just imagining the difference between sourdough and wonderbread.
Feature Request: M-x slice-bread
"Emacs gives you everything, including sliced bread!"
"Vim gives you a knife."
Jokes apart IMHO the only editor comparable to VIM is Emacs :-)
esr's apparent attempts to get everybody to move to git are a little quixotic, I have to say - but if it happens, it's probably a good thing. Where a DVCS is a good fit, then you might as well use git. But even while I support this move and assume workflow will be improved for emacs regulars, I wonder whether it will prove so valuable for occasional contributors. (N.B., I'm English, so I guess what I mean is: I don't believe that this will make much difference.)
I've now seen a couple of attempts to frame this change that way and I'm not sure I buy it.
And he does have a point. I for one do not look kindly on projects that still use Google Code or SourceForge for hosting or other version control systems other than Git or at least Mercurial. And this is because I look out for projects that aren't well maintained - after all, the noise amongst open-source stuff is incredible and I take notice of things such as when the last release or last commit was, current issues, mailing list activity and yes, the tools used.
That said, it's a pity that Emacs isn't being hosted on GitHub or BitBucket, because if these services are good at something, that's quick browsing of recent activity, plus they provide pull requests.
Also, the pull request system is not very good, IMO. It encourages bad practices like having to use git push --force to submit a new patch set without opening a brand new pull request (I suppose you could delete the remote branch and recreate it each time). And then there's the merge commit that it adds if you merge via Github, rather than rebasing to master and doing a fast-forward for a clean history. As ugly as it is, I much prefer submitting a patch set to a mailing list.
But anyway: bzr has simply become a barrier. Not only to attract new developers but also some long term contributors have ceased contributions because they considered bzr to be too much of a hassle. But it's not only that git has simply become the vcs everybody knows. Bazaar development has stopped and it's in "maintenance mode", which sadly means that some bugs aren't getting fixed. Switching to git therefore made sense from several perspectives.
But, I myself used the git mirror rather than bother with bzr. And this certainly is giving emacs some publicity, which (as I understand it) is always a good thing. And if it's being spun as some kind of a push to be friendlier to new developers, mabye the whole exercise will indeed prove more significant than I expect?
Anyway, fortunately we are now in a position to test my theory, one way or the other ;)
I wonder who those could be. I can't remember any major contributor leaving because of bzr.
* John Wiegley, author of eshell and other things.
* The ada-mode was moved to GNU elpa because the maintainer didn't want to work with bzr.
I could only find https://code.google.com/p/vim/ ,
but there are only 3 contributors