On Friday 01 December 2017 00:30:05 Graeme Geldenhuys via Lazarus wrote: > On 2017-11-30 11:46, Michael Schnell via Lazarus wrote: > > Nonetheless, IMHO RAD is a great way to start programming, as you > > immediately and painlessly can see (visualize) what your "business > > RAD should only be used for prototyping. ie: once the prototype is done > and not needed, bin the code. And don't be fooled thinking small utility > apps are great for RAD too. Once that utility get traction, feature get > added, the thing grows like wild-fire and you are in a sh*t storm once > again. Even "small" utilities can do with a good design and business > logic separation. > > It might sound harsh, but boy will you save yourself from headaches > years down the line when your application has grown to multi-million > lines of code. > That is your opinion, my opinion is that RAD is the most productive development technology for most of the projects if done right, separating of GUI and business logic is perfectly possible with RAD. For me MSEide+MSEgui doubled the productivity compared with other tools. It seems to me because you repeat your statement over and over again you never made a RAD development "right" with the right tools. ;-) And the often heard statement that RAD should not be used because it is possible to write bad applications with RAD applies to every other design methology too.
Martin -- _______________________________________________ Lazarus mailing list Lazarus@lists.lazarus-ide.org https://lists.lazarus-ide.org/listinfo/lazarus
