Quote Originally Posted by JVene
One area where the win32API is not well suited is in real time systems. They are industrial applications where the computer must respond to events in predictable timeframes without fail, and Windows isn't geared toward that. Neither is Linux, in most flavors.
There are ways around this limitation, which is due (in part) to the low priority of timer msgs in the OS que (lower than paint msgs).

We use XP Embedded based industrial PCs to monitor heavy machinery in real time and so require finer/more reliable time resolutions than the >10ms Windows provides.


Quote Originally Posted by maxorator View Post
It's so funny - I deleted all ocx files on my computer.

The big difference between MFC and VB is that MFC is just a wrapper which wraps WinAPI, but VB runs on a run-time environment.

I'm just used to use Win32 API and I can do everything easily with it. That's why I don't need MFC. I usually have enough time to do it with WinAPI and for many things I've made my own functions which I can easily copy-paste to another application.
I used to be like you when I first started programming.

Ewwww! MFC I don't need the bloat to do something I can hand code!
VB is the spawn of satan and only used by those who can't write REAL code!

Then my programming skills matured and I came to understand that a good programmer uses the right technology for the task at hand and mixes them when you have to.

Why spend a day coding/testing that app in WIN32 when I can do it in VB in a hour?

I suppose it is different when it is your living, to just playing around trying to be 'leet.