News for hackers. Stuff that matters.
Re:Design Principles Behind Smalltalk (1981) by samatman on Friday May 20, 2022 @02:48PM (#31451120)
"Even if you’re designing for professional programmers, in the end your programming language is basically a user-interface design. You will get much better results regardless of what you’re trying to do if you think of it as a user-interface design." -Alan Kay

https://www.doc.ic.ac.uk/~susan/475/AlanKay.html

Re:Design Principles Behind Smalltalk (1981) by igouy on Friday May 20, 2022 @03:09PM (#31451361)
Let's take that to be true, as-before — Perhaps "to serve the creative spirit" of the coder is not what most software development should be about.

Perhaps most software development should be about effectiveness or reliability or …

Re:Design Principles Behind Smalltalk (1981) by roeles on Saturday May 21, 2022 @03:35AM (#31456020)
In the words of Christopher Alexander, the programmer is the true inhabiter of the program. Since we can expect the world in which the program should function will change, so should the program.

It is the programmer that has to figure out, often with experiments, what changes to the program work best.

Therefore it makes no sense to me to focus on anything but serving the programmer.

Re:Design Principles Behind Smalltalk (1981) by samatman on Saturday May 21, 2022 @07:51AM (#31457084)
The better the experience is for the programmer, the more users will say "y'know what? This doesn't quite do what I want, I wonder how I change that" and presto, they're a programmer now.

We would never have had Hypercard if it weren't for Smalltalk and Alan Kay, and we've never had a platform as good as Hypercard since. That's a crying shame.

Re:Design Principles Behind Smalltalk (1981) by igouy on Saturday May 21, 2022 @01:57PM (#31460218)
Who does the programmer "serve" ?