News for hackers. Stuff that matters.

A comment on Examining Windows 1.0 Hello.c. Parent comment

Re:Examining Windows 1.0 Hello.c by CyberDildonics on Monday May 25, 2020 @07:01PM (#23305789)
You would think mapping memory, files, pipes and general IO would have stabilized by now, at least in their basic forms.
[ Parent | on HN ]
Re:Examining Windows 1.0 Hello.c by NCommander on Monday May 25, 2020 @09:57PM (#23306745)
They did in 32-bit Windows (NT3.1 is pretty much the same on a core level from Win 10). The problem here was that the 8088 suffered from segmentation which put "interesting" constraints on programs, and then Intel's 80286 was alded to the point that it was only successful in the sense of "faster 8088" and not bringing 32-bit computing as was promised.
[ Parent | on HN ]
Re:Examining Windows 1.0 Hello.c by CyberDildonics on Monday May 25, 2020 @10:11PM (#23306817)
I was talking about linux in the era of virtual memory.
[ Parent | on HN ]
Re:Examining Windows 1.0 Hello.c by Narishma on Tuesday May 26, 2020 @05:04AM (#23308841)
The 286 is a 16-bit CPU, it never promised 32-bit computing. That was its successor, the 386.
[ Parent | on HN ]