ABSTRACT
Languages-what's to learn from them? Relics of the past; we know how to design them / to use them. Types / messages / invocation / loops / numbers / methods / big ol' libraries / lots of = signs. Heh, but what is programming, and what role do programming languages play in that process? We have learned a lot over the last five decades: organizing principles, established conventions, theory, fashions, and fads. "Those who cannot remember the past are condemned to repeat it." In this talk we survey what we think are the most important lessons of the past that future programmers, and future programming language designers, ought not forget. We illustrate each lesson by discussing specific programming languages of the past, and endeavor to shine what light we can on the future.
Supplemental Material
Recommendations
50 in 50
OOPSLA '07: Companion to the 22nd ACM SIGPLAN conference on Object-oriented programming systems and applications companionLanguages--what's to learn from them? Relics of the past; we know how to design them/to use them. Types/messages /invocation/loops/numbers/methods/big ol' libraries/lots of = signs. Heh, but...
What is programming, and what role do programming languages ...
50 Years of CS1 at SIGCSE: A Review of the Evolution of Introductory Programming Education Research
SIGCSE '19: Proceedings of the 50th ACM Technical Symposium on Computer Science EducationThe SIGCSE Technical Symposium is celebrating its 50th year, and a constant theme throughout this history has been to better understand how novices learn to program. In this paper, we present a perspective on the evolution of introductory programming ...
Comments