News for hackers. Stuff that matters.
Re:Design Principles Behind Smalltalk (1981) by igouy on Friday May 20, 2022 @01:23PM (#31450288)
Perhaps users want to use apps without needing to program apps?

Perhaps some want to play in a garden without needing to dig and plant and weed and…

Re:Design Principles Behind Smalltalk (1981) by carapace on Friday May 20, 2022 @09:30PM (#31454493)
> Multics Emacs proved to be a great success—programming new editing commands was so convenient that even the secretaries in his office started learning how to use it. They used a manual someone had written which showed how to extend Emacs, but didn't say it was a programming. So the secretaries, who believed they couldn't do programming, weren't scared off. They read the manual, discovered they could do useful things and they learned to program.

~ https://www.gnu.org/gnu/rms-lisp.html

Re:Design Principles Behind Smalltalk (1981) by t0suj4 on Friday May 20, 2022 @02:30PM (#31450928)
I think you shouldn't need to program if you don't want to understand the problem domain.
Re:Design Principles Behind Smalltalk (1981) by igouy on Friday May 20, 2022 @03:11PM (#31451379)
Do you think someone should need to program if they want to understand the problem domain?
Re:Design Principles Behind Smalltalk (1981) by macintux on Friday May 20, 2022 @03:21PM (#31451477)
Speaking for myself, I’ve never found a better way to understand something new.
Re:Design Principles Behind Smalltalk (1981) by igouy on Friday May 20, 2022 @04:31PM (#31452150)
Perhaps a way to understand abstract categories.