Skip to main content
Software Engineering

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

3
  • I'd think you should clarify your question: what do you want to do? Write an OS? Follow the SIGOPS tutorial, read the Tanenbaum book. Learn Win32? There's the Petzold book (although I'm not sure why someone would want to do it without a strong motive). Device drivers? Systems programming is such a wide concept. Commented Jul 16, 2011 at 3:49
  • Why do you say that something would not want to learn Win32 without a strong motive? Commented Jul 16, 2011 at 3:52
  • 2
    Because the raw Win32 API carries a lot of cruft: it comes from the Win16 API, there's a lot of stuff that appears to make little sense. Using a modern GUI toolkit for most of your application and just calling a few methods of the Win32 API where you really need it is usually a better and less painful approach. Commented Jul 16, 2011 at 3:56