<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>eb0la</author><text>I expected to be compiled in some kind of VM, not on an &lt;i&gt;actual&lt;/i&gt; computer with Windows 3.11 :-).&lt;p&gt;I feel &amp;quot;old-style&amp;quot; documentation is much better than we have now. My most productive _python_ only work times were when I had only the python .hlp file and a _physical_ paper book.&lt;p&gt;What are your impressions?</text><parent_chain><item><author>yeokm1</author><text>I built a Win 3.1 app during a company hackathon just for fun. Here, I detail learnings and process for how a new old app can be created with the aid of modern tools and hindsight of old technologies. And perhaps what lessons can it offer us today.&lt;p&gt;Without the benefit of modern libraries and languages, I had to read up and take care of many low level details, socket programming, HTTP, JSON parsing, UI design in code all under tight memory constraints. Nevertheless, it was a terrific lesson in understanding how things work under the hood.&lt;p&gt;I had to do things the old-fashioned way reading books and header files due to the dearth of online documentation. I can empathise with the plight of the programmers of yesteryears who had to code without the benefit of online search engines.&lt;p&gt;With this blog post, I hope you&amp;#x27;ll find it interesting to learn about developing a modern-ancient app for Win 3.1.&lt;p&gt;&lt;a href=&quot;https:&amp;#x2F;&amp;#x2F;github.com&amp;#x2F;yeokm1&amp;#x2F;w31slack&quot; rel=&quot;nofollow&quot;&gt;https:&amp;#x2F;&amp;#x2F;github.com&amp;#x2F;yeokm1&amp;#x2F;w31slack&lt;/a&gt;
&lt;a href=&quot;https:&amp;#x2F;&amp;#x2F;github.com&amp;#x2F;yeokm1&amp;#x2F;http-to-https-proxy&quot; rel=&quot;nofollow&quot;&gt;https:&amp;#x2F;&amp;#x2F;github.com&amp;#x2F;yeokm1&amp;#x2F;http-to-https-proxy&lt;/a&gt;</text></item></parent_chain></comment><story><title>Building a new Windows 3.1 app in 2019: A Slack Client</title><url>http://yeokhengmeng.com/2019/12/building-a-new-win-3-1-app-in-2019-part-1-slack-client/</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>dboreham</author><text>Prior to online search engines there were similar offline resources such as the MSDN CDs.</text><parent_chain><item><author>yeokm1</author><text>I built a Win 3.1 app during a company hackathon just for fun. Here, I detail learnings and process for how a new old app can be created with the aid of modern tools and hindsight of old technologies. And perhaps what lessons can it offer us today.&lt;p&gt;Without the benefit of modern libraries and languages, I had to read up and take care of many low level details, socket programming, HTTP, JSON parsing, UI design in code all under tight memory constraints. Nevertheless, it was a terrific lesson in understanding how things work under the hood.&lt;p&gt;I had to do things the old-fashioned way reading books and header files due to the dearth of online documentation. I can empathise with the plight of the programmers of yesteryears who had to code without the benefit of online search engines.&lt;p&gt;With this blog post, I hope you&amp;#x27;ll find it interesting to learn about developing a modern-ancient app for Win 3.1.&lt;p&gt;&lt;a href=&quot;https:&amp;#x2F;&amp;#x2F;github.com&amp;#x2F;yeokm1&amp;#x2F;w31slack&quot; rel=&quot;nofollow&quot;&gt;https:&amp;#x2F;&amp;#x2F;github.com&amp;#x2F;yeokm1&amp;#x2F;w31slack&lt;/a&gt;
&lt;a href=&quot;https:&amp;#x2F;&amp;#x2F;github.com&amp;#x2F;yeokm1&amp;#x2F;http-to-https-proxy&quot; rel=&quot;nofollow&quot;&gt;https:&amp;#x2F;&amp;#x2F;github.com&amp;#x2F;yeokm1&amp;#x2F;http-to-https-proxy&lt;/a&gt;</text></item></parent_chain></comment><story><title>Building a new Windows 3.1 app in 2019: A Slack Client</title><url>http://yeokhengmeng.com/2019/12/building-a-new-win-3-1-app-in-2019-part-1-slack-client/</url></story>