Great talk, one of my inspirations.
The "nub" (slightly edited):
"A language design can no longer be thing. It must be a pattern, a pattern for growth".
"My point is that a good programmer does not just write programs. A good programmer builds a working vocabulary. A good programmer does language design, though not from scratch, but building on the frame of a base language"
Oh, the paper if you don't want to watch the whole thing:
A classic that is relevant today as it was 20 years ago. Thank you for the repost, it's a good reminder to (re-)examine what I'm doing these days in a larger context.
"..plan for growth with help from users. This is a win for you because you have help. This is a win for the users because they get to have their say and get to bend the growth to their needs."
"Parts of the language must be designed to help the task of growth. A good set of types, ways for a user to define new types, to add new words and new rules to the language, to define and use all sorts of patterns — all these are needed."
20 years later. What does Guy Steele thing about how Java ended up? We still have no operator overloading, no value types. There are plans, sure, but Java grows very slowly. Good thing? Bad thing?
Does anyone know if there is a follow up on this?
This is one of my favorites. They played it for us when I was at https://www.recurse.com. I half appreciated it then, but it's gotten better with repeat viewings.
Thank you for this! I'd forgot the name of the talk, and I spent some days looking for it, with no success...
this was the first video handed to me when I started in Java