I can't seem to remember that Mythical Man Month used the terms cathedrals...
ok, then you haven't read it for a long time lol
There is no such evidence that the general population can deal with even the most basic coding constructs.
Plop them down in front of LOGO Turtle, and they'll do fine.
functions as first-class types, type inference, generics, arrays and dictionaries as built-ins....None of this speaks to programming for dummies
Yeah, that's enough to scare away beginners quickly.
In fact, the 'Cathedral' being criticized was the GNU Emacs team.
Interesting, I figured it was a reference to Mythical Man Month, which uses Cathedrals to describe a method of software development (that is the opposite of the bazaar).
The logic of programming is why it's good for everyone to learn programming. If it helps people learn to think a little more formally, then it's worth it.
You seem to be ignoring the overwhelmingly positive utility of a site like that.
Please note, I didn't say that the website has no utility......the utility comes from compensating for weak developers and weak projects. If the developers are not weak and the projects have high discoverability, then there's no need to ask questions about it on stackoverflow.
(Of course, it can still fill a role, but all the basic questions would be gone).
My first thought on reading this is that this guy started coding this year. #1-3 is solved by using GitHub, TFS online or one of the popular choices most FOSS projects already seem to use. (e.g. How would an experienced developer get these problems in the first place?)....I see he's employed by Red Hat. Does this list as news suggest that Red Hat's internal development processes are immature too?
He wrote the list based on things he'd seen in Chromium, so it's Google's problems. Here is the full list. Not surprising, since they used to jam all their code into a single repository.
(It's hard to fault them for a 100+MB source code download though, unless there's a lot of redundancy in the code).
there are better legal and technical deterrents and preventatives to this type of thing now.
hmm? In one paragraph you say 'shut up and hack' and in the next you criticize Poettering for doing exactly that?
Specifically, he criticized Poettering for not taking care of features he'd created.
On the other hand if you fall behind current dev tools, you miss out on the potential for a lot of community support
I might be flamed for saying this, but if you can't be a software developer without "community support" like asking questions on StackOverflow, then you're not really a software developer. (Likewise, if a tool can't be used without asking questions on stackoverflow, it's the wrong tool to be using for anything serious).
Successful projects are ones where the people who want to use it want to use it enough to fund development.
I'm going to call you a moron right here because you only think of success in terms of monetary value and popularity. Success is not measured by money alone.
A successful project is one that produces great code, one that makes its creator happy.