OCX & Efficency

[Grok]

I think you have to require a pretty narrow definition of performance to say that C++ has more performance overall.  There's way more to application development than coding and debugging, which should be at worst a fifth of your time.

This confuses me. Why would your time other than coding and debugging be affected much by your choice of language?

Choosing VB has some implications in design and architecture, some of which you cannot escape.  VB is almost unique in that by selecting it, you WILL be using Microsoft Windows as your platform.  This reduces the number of decisions you have to make from personnal and project management perspectives.  It affects debugging, testing, and even deployment, in ways that differ from planning generic, without prior knowledge of the language.  So in many ways, selecting VB ahead of time actually makes the entire project more efficient.

And why would the performance of the resulting application not be possible to make better or as good with C++, considering VB is most likely written in C++, i.e. using VB to do something is a subset of using C++ - in the worst case you'll have Microsoft give you the C++ sources for VB, compile your VB, and then write your app there.

I have no doubt that the performance of the resulting application could be possible to make as good or better with C++ instead of VB.  I suppose I was responding to the term "efficient" from a project management angle, while iago may have meant efficient as in tight code.

I do want to add that the skill level of the programmer probably has more of an impact on the final efficiency of either the VB or the C++ code than the language of choice, assuming an average amount of time and resources are given to each programmer.

[iago]

With limited time/need for power, Java all the way

But yes, me and Grok were taking different definitions of the word "efficient"

[Banana fanna fo fanna]

Yay, terrible RAM consumption, slow startup time, slow, thread-happy GUI library, and incompatible class file versions! Woohoo!

[Tuberload]

Yay, terrible RAM consumption, slow startup time, slow, thread-happy GUI library, and incompatible class file versions! Woohoo!

Aren't you the same storm that used to hype up Java all the time? What happened? Anyways, I like it.