Level Extreme platform
Subscription
Corporate profile
Products & Services
Support
Legal
Français
Wil Hentzen's 17 deadly questions about Foxpro
Message
From
23/04/2001 00:10:59
 
 
To
22/04/2001 23:10:22
General information
Forum:
Visual FoxPro
Category:
Other
Miscellaneous
Thread ID:
00494600
Message ID:
00498460
Views:
25
Hi John,

>Hey Doug,
>
>>I would imagine so. However, the difference was in how memory was managed. Remember Bill gates saying that there would be no way we'd ever use more than 640K? <g> Well, the 80x86 family of chips thought that was just fine - until reality intervened. <g> hence a few years of screwball memory management schemes plus a few ok to good ones and finally we've managed to get that family of chips where they are linear rather than segmented (paged).
>
>Well, to give Bill some credit, it certainly appeared to be so way back when.

I know but it is pretty hilarious in retrospect. <g>

>
>>Remember QEMM? That wa sone of the pretty good managers. Goodness.. Foxplus and the early Foxbase & FoxPro were kick-butt programs primarily because of the Watcom C memory manager. Pharlap? Lots better than MSFT's at that time if I correctly recall.
>
>Ahh, Quarterdeck. Aren't they still (barely) in business?

I honestly do not know.. Just checked.. They got 'borged' by Symantec. <g>

>
>Not to go off on a rant, but back to the main issue: memory management. Today's developer is so far insulated from the hardware that any decent application is going to be a pig. In around 1990, if not before, things shifted: PC operating systems went from being productive to being user-friendly. It used to be that developers took great joy from squeezing a few more bytes out of an application. One could do a good app in about 40K with a decent interface. Now a marginal Win app takes up a couple of MB. Why? Well, first we coded to the pre-DOC machine (assembler and tweaked 2 and 3GLs in the late 70's and early 80's). This was optimized to the point where we only had to support functions we used or were in ROM/BIOS. Then, with the rule of DOS, we coded to the DOS interrupt and EXE link files (more mem used)....here came some baggage. Now we code towards WinAPIs, whether nakedly or via a higher level code function. More and more baggage.

Coulsn't agree more ut it takes the likes of a Steve Gibson (www.grc.com) to write ASM Windows Dialog boxes and there are precious few who have the interest and ability that he does these days.

Actually, Linux is where the 'purist' is these days I'd imagine.
Best,


DD

A man is no fool who gives up that which he cannot keep for that which he cannot lose.
Everything I don't understand must be easy!
The difficulty of any task is measured by the capacity of the agent performing the work.
Previous
Reply
Map
View

Click here to load this message in the networking platform