<instructions>Your goal is to analyze the following comment and estimate how highly it will be upvoted by the Hacker News community.</instructions><comment><author>travisgriggs</author><text>I’m always amused that this is called a magazine. At least this particular issue. It’s nearly 500 pages long!!&lt;p&gt;My favorite chapter in the tome is the one by Peter Deutsch on control structures. Starts on page 322. I did Smalltalk for 20 years. I don’t have right words to express how much I loved the Smalltalk block closure, the fact that it was a reified object type that you could extend and use polymorphically is one of the unsung geniuses in Smalltalk. Every time I use python lambdas or Swift’s closures or Kotlin’s closures (the three closure enabled languages I use most today), I just sigh and wish.</text><parent_chain></parent_chain></comment><story><title>Byte Magazine – Smalltalk (1981)</title><url>https://archive.org/details/byte-magazine-1981-08</url></story>
<instructions>Your goal is to analyze the following comment and estimate how highly it will be upvoted by the Hacker News community.</instructions><comment><author>dominicl</author><text>Smalltalk is an amazing time sink if you can get past the syntax. Having learned about it with Squeak Smalltalk the first time during University, it immediately captured my mind. The great collection library, integrated ide, integrated version control, the absence of files. And most exciting everything you interact with comes with it&amp;#x27;s underlying code and can be changed at runtime.&lt;p&gt;Unfortunately trying to release a Smalltalk creation into production always turned out to be the most complex task. Smalltalk is an island. A beautiful island you can get lost in for years. But still an island.</text><parent_chain></parent_chain></comment><story><title>Byte Magazine – Smalltalk (1981)</title><url>https://archive.org/details/byte-magazine-1981-08</url></story>