Building a new Windows 3.1 app in 2019: A Slack Client (yeokhengmeng.com)

Article summary

The article describes the process of building a new Windows 3.1 app in 2019, specifically a Slack client, using modern tools and hindsight of old technologies. The author details the challenges of developing for an outdated operating system, including limited resources, lack of modern libraries, and the need to read books and inspect header files for documentation. The app was successfully created, with a binary size of 23 KiB, and the author reflects on the lessons learned from this project. The project involved overcoming obstacles such as memory allocation, socket programming, and JSON parsing.

Main themes

• Windows 3.1 development
• Retrocomputing
• Low-level programming
• API documentation
• Memory constraints
• Socket programming

What commenters say

• The quality of documentation has decreased over time, with modern online resources often being less reliable than older offline resources.
• The lack of modern libraries and tools makes development for outdated operating systems extremely challenging.
• Some developers prefer working with older systems and documentation, finding it more productive and peaceful.
• The signal-to-noise ratio of online documentation has decreased due to the abundance of amateur documentation writers.
• Older browsers may not support modern HTML elements, but they often ignore invalid elements instead of failing to render the page.
• Cooperative task scheduling in older Windows versions can simplify certain aspects of development, but also introduces limitations and potential issues.
• The transition from modern programming languages to older ones, such as Visual Basic 6, can be difficult due to the lack of features like JSON support.