3 ms·
> In my experience, choice of language makes only a > superficial difference to the difficulty of a project. That largely is my personal experience as well, a
by mpweiher 10y ago
> In my experience, choice of language makes only a
> superficial difference to the difficulty of a project.
That largely is my personal experience as well, and your point that the "real challenge is always figuring out exactly what you're trying to do" echoes Brooks's point from No Silver Bullet regarding accidental vs. essential complexity.
However, these are actually two different things, and I am not convinced they are as connected or as universally true as presented.
First of all, language choice these days is largely superficial, languages have much more in common than they differ, even when you include the more "esoteric" choices such as Smalltalk and LISP. So maybe the reason that choice of language doesn't make much of a difference in projects is that they all suck pretty much the same.
Second, there is a lot of at least circumstantial evidence that "accidental" complexity is actually much larger than we think, and at least partly dependent on architectural choices, and on what you consider "accidental". There's the
20KLOC Xerox PARC vs. 400MLOC MS-Office example, or Knuth vs. McIllroy ( 12 pages vs. 1-6 lines), or my current project, Wunderlist, which is 100KLOC just for a single iOS/Mac client. Or TBL's WWW at 5KLOC vs. Firefox at >13MLOC, or Nile/Gezira at 500LOC vs. Cairo at >100KLOC.
Something is going on here, and I certainly welcome all efforts to figure out what it is and hopefully do something about it.
- taneq 10y agoI think "accidental" complexity is hugely situational and depends on the interaction between original architecture choices and subsequent maintainers of a piece of code. Good maintainers will decrease accidental complexity by eliminating it as they find it, via refactoring or other code tidyup. Bad maintainers will increase it via cut-and-paste coding, bandaid fixes, and poorly structured code. In a long-enough-lived project, there will always be bad maintainers, so I agree that a language that eliminates accidental complexity would be great, if it were possible. A lot of those examples seem to be related more to the amount of functionality given. For example, Xerox PARC (I'm assuming you're talking about their early desktop publishing software?) does a vanishingly small amount compared with MS Office.
- mpweiher 10y ago> related to the amount of functionality Related, yes. Reasonably related? Is MS-Office really 20,000 times better at doing personal computing than what they had at PARC? Is Firefox really a 2600 times better web-browser than WWW.app? I would say it is a stretch to say that MS-Office is 100 times better, but let's assume it is. What's the other 99.5% of the code doing? Let's say Firefox is a 10 times better browser than WWW.app. Again, what's the other 99.5% of the code doing? There's some sort of polynomial (or exponential?) involved as we try to grow software systems, and I don't think it has to do with "bad maintainers", or at least not primarily.