ATL or Visual Basic? Does it matter?
-
>> VB is no more suited to database work than Oracle > > What are you talking about? I was trying to be funny. Let me start with something simpler: There was this traveling salesman. He was driving down a country road when without warning (and for no apparent reason), his car sputter to a stop. He coast to the side of the road, go out and opened the hood, looking for something he was sure he wouldn't recognize. "It's the carbeurator", a voice behind him said. He turned, only to see a horse grazing by the fence. Seeing nobody, he turned back to the car, again inspecting the top of the engine for any tell-tale sign of what might be wrong. He started jiggling wires, and mysterious hosts, and electrical connections. "I told you - it's the carbeurator". He spun around again. Again, only the horse was to be seen, but this time, the horse was looking directly at him. "Did you say something?", the salesman asked. "Yep. It's the carbeurator", the horse replied. The salesman couldn't believe his ears. He saw a car approaching off in the distance and he began running toward it, waving his arms wildly. The salesman was completely breathless by the time the old man in the beatup pickup truck stopped next to him. "My car broke down over there and I was trying to figure out what was wrong, when this horse started talking to me!" "Show me", the old man in the truck said. When they got back to the saleman's car, the old man pointed out the horse grazing by the fence and asked, "Is that the horse that you say talked to ya?" "Yeah, that's the one!", the salesman wheazed. "What'd he say?" "He said 'It's the carbeurator'", responded the salesman. "That's funny", said the old man. "I didn't think he knew anything about cars." "...the staggering layers of obcenity in your statement make it a work of art on so many levels." - Jason Jystad, 10/26/2001
-
All, I would like to have some opinions on my next project. I am building an n-tiered financial application with Visual Studio 6. I am not building it in .NET because of the hardware requirements, possible delays to the actual release of .NET and potential performance issues. I’d like everyone to put on his or her pointy-haired cap for this one. :) Does it really matter what tool I use to build the application? Will the customer notice the speed difference between ATL and Visual Basic? Is it worth increasing the development time for this speed increase? Will it be an effective marketing tool to say it is written with Visual C++ and ATL? I have heard some interesting thoughts on this. I would appreciate any thoughtful comments. Thanks, Rich
Three reasons to use ATL 1/ It means you can do the GUI in VB if you absolutely must. 2/ You'll be able to hold your head up at parties when people ask what you used instead of muttering it and hoping no-one hears 3/ You'll end up with a reusable cross language component. Christian After all, there's nothing wrong with an elite as long as I'm allowed to be part of it!! - Mike Burston Oct 23, 2001
