For 99% of folks outside the HN echo chamber, email works fine. Spam is a problem, but I've never heard or read of anyone who thinks email needs to go the way of the dodo except on this site.
I'm having a really hard time getting my friends to email me. They want me to use awful garbage like FB Messenger or Whatsapp instead.
Why kernel development still uses email (2016)
71–80 of 97 posts
Re: Why kernel development still uses email (2016)
#72Earlier quoted context omitted.
It was intended to be disparaging: one of my major beefs with this community is the massive culture of groupthink and aggressive self reinforcement/adulation.
> It was intended to be disparaging and thus your thesis of 'HN doesn't like to be reminded' falls to the simpler explanation of 'trashtalk usually gets downvoted'.
I prefer to see it as the down votes reaffirming that I am correct.
Re: Why kernel development still uses email (2016)
#73What I want to know is: which of Tower, GitKraken, GitHub Desktop or Stash do the kernel developers prefer?
Re: Why kernel development still uses email (2016)
#74Earlier quoted context omitted.
Sure, all these points are true. Notmuch is a bit unfinished I think. What email setup do you have?
I'm actually using notmuch in emacs myself, but I'm just running in to a bunch of its limitations and looking around for an alternative. Very sorry to hear that Gnus with a notmuch backend is slow, as that's what I was considering trying next.
I really like Notmuch's interface. I think limitations are perhaps not that hard to patch on Elisp unless you have a complicated setup.
I'm trying to implement a DSL to coordinate tag maildir sync on top of a few macros.
Re: Why kernel development still uses email (2016)
#75Earlier quoted context omitted.
> It was intended to be disparaging and thus your thesis of 'HN doesn't like to be reminded' falls to the simpler explanation of 'trashtalk usually gets downvoted'.
Perhaps. I prefer to see it as the down votes reaffirming that I am correct.
Re: Why kernel development still uses email (2016)
#76For 99% of folks outside the HN echo chamber, email works fine. Spam is a problem, but I've never heard or read of anyone who thinks email needs to go the way of the dodo except on this site.
Email is the pinnacle of human communication. Without notifications, which I, of course, do not use, email is the least intrusive and least disrupting way someone can contact me. I simply check my email when I feel like it, which is about two times daily, morning and sometime late evening. Then, even when I look at my email, I don't have to respond. I don't have to do anything. And if there's an email I want to reply…
Re: Why kernel development still uses email (2016)
#77Earlier quoted context omitted.
If Linus declared that everyone must use, say, Gitlab from now on, some Linux developers might leave. But developers who don't use email may never start working on Linux. That's why it cuts both ways: either option alienates some developers.
A developer that does not use mail :-) that is very unlikely
Re: Why kernel development still uses email (2016)
#78>, kernel developers still use email because it is faster than any of the alternatives. Over the course of the last year, the project accepted about eight changes per hour — every hour — from over 4,000 developers sponsored by over 400 companies Compare with Google's ~1875-per-hour from 2015[1]: >, and Google’s 25,000 engineers make about 45,000 commits (changes) to the repository each day. Obviously, we can't extrap…
The problem with a ALM is it is a global lock. It is enormously disruptive if it is unavailable or even slow.