> [...] > > The big question here you seem to avoid commenting on is what is > > the workflow you expect the next generation to seriously adopt? > [...] > > Perhaps playing devil's advocate a bit, but why do you assume that > young people are incapable of learning and using working, > established systems? Having worked closely with new contributors on > various projects, many fresh out of school, I think you do them a > disservice in implying that they will only use flashy new > technologies.
As I wrote today: > But I am worried about the next generation of open source > contributors. I have never seen anyone under 40 e.g. use Emacs to read > email. I have seen a few use Mutt, though. I don't think this is a question of "flashyness". Everybody uses e.g. command-line git and ssh like bread and butter. This is a question of workflows and doing efficient code reviews. If you have people who start fresh and try code reviews by email and in a browser I suspect the number of people who decide to build up their personal code review workflow with email plugins and stuff is near zero, and definitely if you are mentoring new people and they as how to do a code review I don't think mentors spend hours in helping people configure Mutt/Emacs for have all plugins needed for an efficient code review, but new people tend to start doing their first reviews in a browser UI and then probably never leave it..?
