3 ms·
Do go on.
by MaxBarraclough 8y ago
Do go on.
- pjmlp 8y ago"Oh, it was quite a while ago. I kind of stopped when C came out. That was a big blow. We were making so much good progress on optimizations and transformations. We were getting rid of just one nice problem after another. When C came out, at one of the SIGPLAN compiler conferences, there was a debate between Steve Johnson from Bell Labs, who was supporting C, and one of our people, Bill Harrison, who was working on a project that I had at that time supporting automatic optimization...The nubbin of the debate was Steve's defense of not having to build optimizers anymore because the programmer would take care of it. That it was really a programmer's issue.... Seibel: Do you think C is a reasonable language if they had restricted its use to operating-system kernels? Allen: Oh, yeah. That would have been fine. And, in fact, you need to have something like that, something where experts can really fine-tune without big bottlenecks because those are key problems to solve. By 1960, we had a long list of amazing languages: Lisp, APL, Fortran, COBOL, Algol 60. These are higher-level than C. We have seriously regressed, since C developed. C has destroyed our ability to advance the state of the art in automatic optimization, automatic parallelization, automatic mapping of a high-level language to the machine. This is one of the reasons compilers are ... basically not taught much anymore in the colleges and universities." -- Fran Allen interview, Excerpted from: Peter Seibel. Coders at Work: Reflections on the Craft of Programming
- MaxBarraclough 8y agoI presume that interview was several decades ago? High-level languages are doing extremely well these days. In certain domains, no-one writes C. No-one writes a website in C. Desktop GUI applications are a mixed bag - some use C/C++ (inappropriately, in my opinion), and some use 'managed' languages. Incidentally I studied compilers at university. I agree that any supposedly serious computer science course that doesn't study them, is cheating their students.
- pjmlp 8y agoCoders at Work: Reflections on the Craft of Programming was published in 2009. One year and a half missing to one decade, in case we are counting them.
- MaxBarraclough 8y agoWell into Java/C# time then. I suppose Allen's point was that Java and C# hadn't done much to improve on the basic ideas of C?
- pjmlp 8y ago> By 1960, we had a long list of amazing languages: Lisp, APL, Fortran, COBOL, Algol 60. These are higher-level than C. We have seriously regressed, since C developed. C has destroyed our ability to advance the state of the art in automatic optimization, automatic parallelization, automatic mapping of a high-level language to the machine. Java and C# weren´t even a thing. I suggest you read the IBM RISC research papers done with PL/8 with an LLVM like architecture in the mid-70's before they pivoted into UNIX when going into the market. The way system programming was done in Burroughs in mid-60's, nowadays still sold as Unisys ClearPath platform. OS/400 firmware being written in PL/S in the early 80's. Or even some analysis of Ada deployments in High Integrity Systems, like "Building High Integrity Applications with SPARK" (2015).
- MaxBarraclough 8y ago> Java and C# weren´t even a thing. Was the interview in 2009, or not? That was the Java 6 era. I'm still trying to make sense of "destroyed our ability to advance the state of the art" given that we now have modern Java and C#.
- pjmlp 8y agoYes it was in 2009. What she meant was that the adoption of C kind of destroyed their work doing optimizing compilers since the mid-60's, as C lacked any kind of optimization putting that on the shoulders of developers. It was the years of optimization work in C compilers, specially regarding UB abuse that has kind of matched what they were already doing on mainframes. As mentioned PL/8 was a safe systems programming language used to for IBM's RISC compilers and respective OS. The paper describing the toolchain was implemented and the pluggable optimization passes could be describing LLVM today. So with UNIX's adoption the computing world has spent a couple of decades making C compilers up to date with mainframe optimizers, rebuilding the world instead of carrying on where they already were, hence the "destroyed our ability to advance the state of art".