Re:Building a new Windows 3.1 app in 2019: A Slack Client
by AdrianB1 on Thursday December 19, 2019 @04:13AM
(#21833255)
There is no direct correlation between the size of an executable (64kb) and the size of the RAM usage (can be hundreds of MB). I could not find any information about the total memory usage of the application, is it described anywhere?
[ Parent
| on HN ]
Re:Building a new Windows 3.1 app in 2019: A Slack Client
by amiga-workbench on Thursday December 19, 2019 @04:45AM
(#21833410)
Its running on a ThinkPad 390e, 64mb as standard, and tops out at 256mb, so there is your upper bound.
Even at an absolute worst case it still beats the pants off Slack.
Re:Building a new Windows 3.1 app in 2019: A Slack Client
by yeokm1 on Thursday December 19, 2019 @04:54AM
(#21833450)
You are correct. My 390E has 384MB of RAM but only 256MB is accessible by Win 3.1.
An earlier blog post shows this http://yeokhengmeng.com/2016/09/windows-for-workgroups-3-11-...
Re:Building a new Windows 3.1 app in 2019: A Slack Client
by StavrosK on Thursday December 19, 2019 @05:27AM
(#21833592)
And is probably quite a bit faster, too.
Re:Building a new Windows 3.1 app in 2019: A Slack Client
by cwyers on Thursday December 19, 2019 @11:15AM
(#21836189)
It's also lacking so many features as to be unusable.
Re:Building a new Windows 3.1 app in 2019: A Slack Client
by yeokm1 on Thursday December 19, 2019 @04:56AM
(#21833459)
Win 3.1 apps can also access memory in 64K segments which I only use 1 to hold the humongous HTTP+JSON reply from Slack.
Wikipedia says "However, no single process can use more than 16 MB.". Not sure where is the source of that though.
Re:Building a new Windows 3.1 app in 2019: A Slack Client
by tinus_hn on Thursday December 19, 2019 @07:02AM
(#21834124)
https://en.m.wikipedia.org/wiki/Protected_mode
It’s a limitation from the 286 Protected Mode.