News for hackers. Stuff that matters.
Re:Graying Linux developers look for new blood by uuilly on Thursday August 29, 2013 @04:56PM (#6298560)
Being a little more friendly could help their cause.
Re:Graying Linux developers look for new blood by jamesaguilar on Thursday August 29, 2013 @05:00PM (#6298579)
Careful, keep talking like this and you're liable to be informed that cursing someone out is efficient communication by the HN crowd.

It's hard, but I think what needs to happen here is a culture of mentoring like in most successful software companies. If there is such a thing for aspiring Linux devs, I've never heard of it.

Re:Graying Linux developers look for new blood by zanny on Thursday August 29, 2013 @05:28PM (#6298743)
Come on, Linus curses out one guy a year and it always hits HN front page. It isn't like your kernel commits are going to get you an angry veto with 90% explitive vocabulary density on a daily basis, it is the exception that people like to point out.
Re:Graying Linux developers look for new blood by bitwize on Thursday August 29, 2013 @05:34PM (#6298771)
When Linux curses someone out, it is usually someone who's been in the community for a while and should have known better than to push the crappy code they pushed.

If you're a kernel n00b, chances are you will not be submitting your patches to Linus himself but someone two or three levels down from him, the maintainer of some driver or FS or virtual memory subsystem, who will tell you in nicer terms what you did wrong and how to fix it.

By the time you get to the submitting to Linus stage, it is assumed that you will have your shit in one sock, code-wise; violating that assumption is what earns you the Finnish-obscenity-laden opprobrium.

Re:Graying Linux developers look for new blood by jlgreco on Thursday August 29, 2013 @05:41PM (#6298815)
Exactly right; this notion that people here have of kernel devs spewing vitriol with reckless abandon at anybody not in their club is pure fantasy.

Why does it persist? Because normal conversations from kernel dev mailing lists are boring while the occasional directed vitriol is very amusing and spawns lots of heated discussions on Slashdot and HN. That, and because calling people out for "things", whether those "things" are cursing, or any other number of things on other days, makes people feel good and superior. See? I'm doing it right now. ;)

Re:Graying Linux developers look for new blood by anonymous on Thursday August 29, 2013 @05:20PM (#6298696)
Well, it is efficient if you want to minimise the number of people who aren't star programmers with hard heads and don't care how many star programmers with manners you turn away. If your supply pool is big enough, you will have great success.

Hypothetically though - would it be that much better if Linus et al. were turning away people politely with words like "this code doesn't meet our standards of quality because X Y Z" instead of "your code is shit, see X Y Z"? Also, for people at the lead, you need those who can say "no", know when to say "no", aren't going to compromise just because the patch was sent by so-and-so and won't hold back from saying where they see a problem. You also want them to be good at communicating with people in a civil manner. The two are unfortunately orthogonal qualities. It seems to me that we should first take the people who are definitely good enough in the engineering aspect to understand and lead the project, then select the best communicator, rather than seeking someone with a best average score at engineering and communicating. You might get impolite people at the top, but you will guarantee the project won't get worse.

Re:Graying Linux developers look for new blood by takluyver on Thursday August 29, 2013 @05:27PM (#6298738)
> would it be that much better if Linus et al. were turning away people politely with words like "this code doesn't meet our standards of quality because X Y Z"

It seems quite reasonable to imagine that more of those people would come back and try again if they were treated politely. Working with new contributors takes time at first, but it's an investment that you hope will pay back when they're productive core developers.

Re:Graying Linux developers look for new blood by SEMW on Thursday August 29, 2013 @05:38PM (#6298794)
See https://lwn.net/Articles/559061/ for a recent discussion about the tone of LKML.
Re:Graying Linux developers look for new blood by anigbrowl on Thursday August 29, 2013 @05:22PM (#6298707)
Or user-friendly for that matter. I think it's pointless to keep using utilities with titles like man, cp, ls, fsck, grep etc., which are are extremely unintuitive to most people. We're not using 300 bps dumb terminals any more, but the Unix command line remains about as friendly as a leopard. I hated this ~20 years ago when I first learned Linux, but it was the price I had to pay to set up my own domain and hey, a free Unix clone. But two decades later, it's still pretty unfriendly, and a there's still a lot of command-line snobbery that seems dedicated to preserving this unintentional but obsolete obscurantism, like thoroughbred horse breeders who refuse to acknowledge the market's preference for cars and bicycles.
Re:Graying Linux developers look for new blood by tptacek on Thursday August 29, 2013 @10:00PM (#6299812)
Not-so-compelling examples of Unix command line idioms that are needlessly baroque: cp, man, ls, grep.

Great examples of Unix command line idioms that are needlessly baroque: find, ifconfig, route, netstat, lsof.

Re:Graying Linux developers look for new blood by anigbrowl on Friday August 30, 2013 @12:25AM (#6300256)
I agree with you about find, but I was thinking of the utility itself rather than the command-line usage. 'find' is at least descriptive of what the command does. 'cp' is somewhat like 'copy' but 'man' should be called 'help', 'ls' should be called 'list' and 'grep' would be more obvious with any name, except maybe 'brian.'
Re:Graying Linux developers look for new blood by glurgh on Friday August 30, 2013 @02:25AM (#6300500)
The 'unfriendliness' doesn't come from the names, it's that for it to make sense you have to absorb some conceptual framework of how the thing works. People adapt to odd names quite easily, just as you have, once they get used to them - both syntactically (ls doesn't actually stand for 'list') and semantically (find doesn't really find, maybe 'ftraverse' for filtered traverse).

To use the unix command line you have to get your head around a bunch of key concepts, say, globbing, i/o redirection, pipes, etc. After that, whether it's 'grep' or 'brian' isn't going to get in your way much.

This sort of jargon is pretty typical, though, and I think it's a fairly small barrier. Want to learn some LISPy language? Here come the entirely meaningless car, cdr, cons, s-expression. Functional processing of sequences? Well you can map, you can reduce, you can zip, you can fold. Building your first RoR app? Don't forget to railtie your merb to the phusion gem of the sinatra rack, but not before you've raked your capistrano with a cucumber. You can probably safely rename every JS framework to an MMM (Marklar, Marklar, Marklar) framework given the liberties they take with the meaning of the things M, V and C stand for.

You can give, say, 'cat' or 'tee' magically and perfectly clear names but than in itself won't make anyone understand things like 'unix utilities have one input and two output streams' any better.

Re:Graying Linux developers look for new blood by dylangs1030 on Friday August 30, 2013 @04:52PM (#6304138)
I actually love grep. I'm not sure why, but it's taken such a hold in my brain that I intuitively associate searching for something specific with the word "grep."

I agree with man. It makes sense technically because of "manual"...except that "man" is its own word. Every time I type man, I feel like I'm typing the gender, and it's weird.

cp bothers me because they shortened a four-letter word, the same with ls and list. Despite the original terminal constraints, they couldn't spare two characters?

Re:Graying Linux developers look for new blood by dragonwriter on Friday August 30, 2013 @05:18PM (#6304273)
> cp bothers me because they shortened a four-letter word, the same with ls and list. Despite the original terminal constraints, they couldn't spare two characters?

Really, I think that with an OS designed in the late 1960s, brutally reducing commonly-used commands to the shortest recognizable form was a very good idea.

Storage capacity (both RAM and persistent), processor speeds, and bandwidth for internal and network transfers were all many orders of magnitude less than today's systems. Extra bytes had a real cost.

Re:Graying Linux developers look for new blood by glurgh on Friday August 30, 2013 @07:54PM (#6304900)
I get to self-pedantipoint myself here, 'ls' does not stand for the Multics 'list segments' as I thought, it didn't mean 'list segments' in Multics either, that's just folk etymology that's made it into Wikipedia (I just took it out).

http://alt.folklore.computers.narkive.com/7q9reknM/1950s-at-...

Author of that post is Tom Van Vleck, who ought to know.

http://en.wikipedia.org/wiki/Tom_Van_Vleck

Re:Graying Linux developers look for new blood by kragniz on Thursday August 29, 2013 @05:36PM (#6298780)
I believe we're talking about kernel development here, not GNU utilities. However, what naming scheme would you prefer? The command line is fairly unintuitive as it is. I would argue it is preferable to have short, memorable and fast to type names.
Re:Graying Linux developers look for new blood by anigbrowl on Friday August 30, 2013 @12:27AM (#6300260)
It is about kernel development, but I think this small issue I've pointed to is symptomatic of the general problem.

These names are short, but not memorable or easily discoverable.

Re:Graying Linux developers look for new blood by nsmartt on Thursday August 29, 2013 @06:46PM (#6299133)
To be fair, it's entirely possible to create aliases with more intuitive names and dump a "you can type ____ for short" message on each run.
Re:Graying Linux developers look for new blood by jlgreco on Thursday August 29, 2013 @07:53PM (#6299364)
Which leads me to suspect that if there were a demand for "a big file to source in your bashrc to alias 'cp' to 'copy'", it would exist. It is not exactly a difficult thing to do, but nobody actually cares enough to do it (probably because it is not actually a problem).
Re:Graying Linux developers look for new blood by nsmartt on Thursday August 29, 2013 @08:46PM (#6299559)
I suspect people get used to cp, mv, etc, and then aren't interested in longer versions anymore. I'd still say it'd be a good default.
Re:Graying Linux developers look for new blood by zanny on Thursday August 29, 2013 @05:29PM (#6298753)
I agree with this. A lot of the limitations of 1980s unix no longer exist, yet we still constrain our terminals to obtuse nomenclature and bad syntax like we only have 80 characters before the terminal auto-returns.
Re:Graying Linux developers look for new blood by munin on Thursday August 29, 2013 @05:01PM (#6298584)
seriously, why subject yourself to that kind of acidic ridicule when you can make more public contributions working on things closer to the frontend. doing the systems engineering work to make the kernel go is very important, but unless you're at the very very top (linus) nobody is going to care about you.
Re:Graying Linux developers look for new blood by jlgreco on Thursday August 29, 2013 @05:56PM (#6298906)
"Padding your resume" is not a priority shared by everybody. Many people contribute to projects that are not visible because they see an inadequacy and they believe they have a solution. Or you know, for fun. Fun is pretty independent of visibility, if it wasn't then single-player video-games wouldn't exist.
Re:Graying Linux developers look for new blood by uuilly on Thursday August 29, 2013 @05:23PM (#6298713)
That depends a lot on your industry. At most places I've worked, nobody knew what node.js or bootstrap was. At all those places being a journeyman kernel dev would look REALLY good.
Re:Graying Linux developers look for new blood by Demiurge on Thursday August 29, 2013 @05:04PM (#6298611)
Rewriting linux from scratch in a cool language like Go would also help a lot.
Re:Graying Linux developers look for new blood by pyre on Thursday August 29, 2013 @05:07PM (#6298623)
Yes. The Linux kernel should be entirely rewritten every 5-10 years so that it can be in the latest "trendy" programming languages.
Re:Graying Linux developers look for new blood by greenyoda on Thursday August 29, 2013 @05:23PM (#6298717)
Go doesn't even support all of the architectures on which Linux runs, for example, IBM mainframes.

Not to mention that a language that relies on its own automatic memory management (garbage collection) might not work so well for kernel programming.

Re:Graying Linux developers look for new blood by Demiurge on Thursday August 29, 2013 @05:34PM (#6298773)
I thought it was obvious that it was a joke motivated by the recent headlines on HN...
Re:Graying Linux developers look for new blood by bifrost on Thursday August 29, 2013 @05:27PM (#6298737)
I think it should be rewritten in assembler, because its so old its retro and now will become the new hotness.
Re:Graying Linux developers look for new blood by vikas0380 on Thursday August 29, 2013 @05:23PM (#6298711)
Or in java or any other language
Re:Graying Linux developers look for new blood by Demiurge on Thursday August 29, 2013 @05:37PM (#6298789)
As long as it's cool and has goroutines and interfaces and no semicolons.
Re:Graying Linux developers look for new blood by rubiquity on Thursday August 29, 2013 @05:02PM (#6298597)
Since when is Linus the only middle aged person working on Linux? Your comment reeks of ignorance and cargo culting.
Re:Graying Linux developers look for new blood by pyre on Thursday August 29, 2013 @05:08PM (#6298627)
Are you suggesting that Linus is the only person in FOSS that cusses people out?
Re:Graying Linux developers look for new blood by chatman on Thursday August 29, 2013 @05:19PM (#6298689)
Linus is against free software [0]. Linus publicly abuses fellow developers for making mistakes [1]

Linus representing "FOSS" just doesn't sound right. Look at RMS for a real leader.

[0] - www.youtube.com/watch?v=bw58LZTuZjA [1] - news.ycombinator.com/item?id=5107386

Re:Graying Linux developers look for new blood by pyre on Thursday August 29, 2013 @05:40PM (#6298805)
I'm aware of Linus' thoughts on Free Software. Regardless of those thoughts the Linux kernel is a Free Software project, and by extension Linus is a "person in FOSS."
Re:Graying Linux developers look for new blood by rubiquity on Thursday August 29, 2013 @06:28PM (#6299026)
No I'm saying the exact opposite.