Live data from Hacker News

Interview with Ken Thompson (2011)

drdobbs.com

11–20 of 29 posts

Re: Interview with Ken Thompson (2011)

#11
post #6

Earlier quoted context omitted.

> "an object-oriented C" ... minimalism That's Objective-C in a nutshell. Or was, anyway. The most minimal way to have useful OO on C. Of course, you could make it even simpler if you drop the "must be a superset of C"-requirement.

Thus Swift.

Cough. Well, except the the "simple" part...

Re: Interview with Ken Thompson (2011)

#12

"The language grew up with one of the rewritings of the system and, as such, it became perfect for writing systems. ... It became the perfect language for what it was designed to do." Really? Perfect? Why then are there entire books filled with "C gotchas" or "C traps and pitfalls"? The language is an inconsistent, inelegant, error-prone mess that has left us with decades of serious bugs and security vulnerabilities.…

C was certainly a major step forward at the time, but he does seem oblivious to its flaws (at least in this interview). I was also disappointed to see how he casually trashed C++ at the same time. Not very diplomatic.

If anything, it's also ironic, because a lot of downsides of C++ stem from its requirement to inherit C downsides.

Re: Interview with Ken Thompson (2011)

#13

"The language grew up with one of the rewritings of the system and, as such, it became perfect for writing systems. ... It became the perfect language for what it was designed to do." Really? Perfect? Why then are there entire books filled with "C gotchas" or "C traps and pitfalls"? The language is an inconsistent, inelegant, error-prone mess that has left us with decades of serious bugs and security vulnerabilities.…

It can be perfect for something without being "perfect period".

Re: Interview with Ken Thompson (2011)

#14
post #6

Who here thinks they should have made "an object-oriented C" instead? I was under the impression that a big part of C's success (as a lingua france / lowest common denominator) is its minimalism. It forces only a few concepts on its users.

> "an object-oriented C" ... minimalism That's Objective-C in a nutshell. Or was, anyway. The most minimal way to have useful OO on C. Of course, you could make it even simpler if you drop the "must be a superset of C"-requirement.

Maybe the most minimal, but not the most efficient, and C's minimalism is only useful because it lets you be as efficient as the hardware will be. Without that goal, the Lisps are more minimal than both C and Objective-C.

Re: Interview with Ken Thompson (2011)

#15
post #6

Who here thinks they should have made "an object-oriented C" instead? I was under the impression that a big part of C's success (as a lingua france / lowest common denominator) is its minimalism. It forces only a few concepts on its users.

> "an object-oriented C" ... minimalism That's Objective-C in a nutshell. Or was, anyway. The most minimal way to have useful OO on C. Of course, you could make it even simpler if you drop the "must be a superset of C"-requirement.

I have a fondness for ObjC because I was a Smalltalk programmer once upon a time (it's also probably why I like Ruby), but you could imagine a simpler object system on par with Object Pascal. I'm actually kind of surprised that nobody tried that but maybe with ObjC and C++ fighting it out people assumed yet another object-oriented dialect would go nowhere.

Re: Interview with Ken Thompson (2011)

#17

"The language grew up with one of the rewritings of the system and, as such, it became perfect for writing systems. ... It became the perfect language for what it was designed to do." Really? Perfect? Why then are there entire books filled with "C gotchas" or "C traps and pitfalls"? The language is an inconsistent, inelegant, error-prone mess that has left us with decades of serious bugs and security vulnerabilities.…

To me, C is honestly one of the most elegant languages there is, right next to Scheme.

Re: Interview with Ken Thompson (2011)

#18

"The language grew up with one of the rewritings of the system and, as such, it became perfect for writing systems. ... It became the perfect language for what it was designed to do." Really? Perfect? Why then are there entire books filled with "C gotchas" or "C traps and pitfalls"? The language is an inconsistent, inelegant, error-prone mess that has left us with decades of serious bugs and security vulnerabilities.…

To me, C is honestly one of the most elegant languages there is, right next to Scheme.

I've heard similar opinions before, and would love to see this expanded on... in particular how it can be elegant compared to Scheme, which is by far the most elegant language I know.

Re: Interview with Ken Thompson (2011)

#19

Earlier quoted context omitted.

To me, C is honestly one of the most elegant languages there is, right next to Scheme.

I've heard similar opinions before, and would love to see this expanded on... in particular how it can be elegant compared to Scheme, which is by far the most elegant language I know.

Its simplicity is what I'm attracted to, and I think that's why I think Scheme is elegant too. It has less syntax than comparable languages, fewer keywords, a smaller standard library etc.

I'm not sure if it makes the case for elegance or if I'm misunderstanding it.

Re: Interview with Ken Thompson (2011)

#20

Earlier quoted context omitted.

I've heard similar opinions before, and would love to see this expanded on... in particular how it can be elegant compared to Scheme, which is by far the most elegant language I know.

Its simplicity is what I'm attracted to, and I think that's why I think Scheme is elegant too. It has less syntax than comparable languages, fewer keywords, a smaller standard library etc. I'm not sure if it makes the case for elegance or if I'm misunderstanding it.

Do you also consider simple having about 200 cases of UB on the standard?
Post reply on HN