Path: utzoo!attcan!uunet!ginosko!gem.mps.ohio-state.edu!tut.cis.ohio-state.edu!network!ucsd!orion.cf.uci.edu!uci-ics!zardoz!ccicpg!cci632!rit!tropix!moscom!ur-valhalla!uhura.cc.rochester.edu!rochester!rutgers!psuvax1!psuvm.bitnet!h40 From: H40@PSUVM.BITNET (Bob Hasenfratz) Newsgroups: comp.windows.ms Subject: Why not Qbasic for Windows development? Message-ID: <89167.205221H40@PSUVM> Date: 22 Jul 89 00:52:21 GMT Organization: Penn State University - Center for Academic Computing Lines: 6 Maybe this is silly. I've done a lot of programming in QuickBasic and have recently got a copy of Quick C. I'm not generally slow, but it occurs to me that Microsoft would be able to establish Windows a lot more quickly for every day users if it allowed you to write windows applications through QuickBasic. I have to admit that I find C somewhat baffling. There must be a thousand technical reasons why this can't be done. What are they?