• Welcome to Valhalla Legends Archive.
 

Visual Basic .Net vs Visual Basic 6.0

Started by DarkVirus, November 08, 2003, 12:20 PM

Previous topic - Next topic

Banana fanna fo fanna

Isn't RAD "officially" the way GUI's are design and code is integrated via the IDE?

Skywing

Quote from: St0rm.iD on November 11, 2003, 01:24 PM
I think weak typing is core to RAD. VB.NET is strongly typed, isn't it? I could be wrong on this one.
I think strong typing is good for RAD, because it shows you many bugs at compile time instead of making you waste time in a debugger later to fix them.

Banana fanna fo fanna

I don't, IMO RAD is meant for prototyping mostly.

Grok

Quote from: St0rm.iD on November 11, 2003, 08:36 PM
I don't, IMO RAD is meant for prototyping mostly.

RAD development platforms are the first choice of business for most applications that have limited distribution, limited lifetime, liberal performance constraints, and a narrow return on investment.

That is to say if it is not going to be used by hundreds, or for longer than 4x or 5x the time it takes to develop it; if performance is one of the weightiest design considerations, or if the cost of development outside RAD causes the payback to be nulled, then companies will first turn to RAD tools.