Re:NeXTstep Manual, Systems Programming with Objective-C and...
by dang on Sunday June 05, 2016 @10:32PM
(#11844293)
> Who cares.
Whoa. This breaks the HN guidelines. Please edit personal nastiness out of your comments here.
Your comment would be so much better without that last bit.
Re:NeXTstep Manual, Systems Programming with Objective-C and...
by 4ad on Monday June 06, 2016 @05:26AM
(#11845522)
No, his mention of his experience working with Windows 3.0 is completely irrelevant in this discussion. It's just a very weak attempt at appeal to authority. And if you look in his message history, it's something he does consistently.
Re:NeXTstep Manual, Systems Programming with Objective-C and...
by dang on Monday June 06, 2016 @03:11PM
(#11849433)
Even assuming all that is true, it doesn't change the requirement that you (i.e. everyone) be civil when posting here.
Re:NeXTstep Manual, Systems Programming with Objective-C and...
by yuhong on Sunday June 05, 2016 @09:34PM
(#11844120)
Ah, the Win16Mutex. My personal favorite however (especially when discussing the OS/2 2.0 fiasco) is how the continued dependence on DOS allowed Caldera lawsuits to continue.
Re:NeXTstep Manual, Systems Programming with Objective-C and...
by 4ad on Monday June 06, 2016 @11:29AM
(#11847486)
I'd love to hear more about that!
Re:NeXTstep Manual, Systems Programming with Objective-C and...
by pjmlp on Sunday June 05, 2016 @01:04PM
(#11841881)
Not everyone was running old 16-bit software.
As for who cares, the customers that value my detailed knowledge of how the Windows stack works, since I don't mix technology with OS religion.
It mattered just as much as it matters now, and it will always continue to matter. People didn't know that it mattered because people didn't know anything better. After all, for the vast majority of people crappy DOS-based Windows from Microsoft was the only thing they could afford to use (in every sense of the word, not just financial sense).
> Also unless you are speaking about Windows 3.x, your statement about prempemptive multitasking and memory protection is wrong.
No. 16-bit software was cooperatively scheduled, and there was a lot of 16-bit software in the Windows 95 era. Even significant components of the first version of Windows 95 were 16-bit. Hell, lots of drivers were real-mode drivers!
Software used virtual memory, but there was zero, nada, nil memory protection. In fact it was pretty standard for programs to stomp over each other's memory as a "feature".
> I develop software for Windows since the 3.0 version.
Who cares.