Peter Jakobsson so eloquently writes: >The original selling point of 4D was that it was stateful and that >statefullness >is what gave us massive productivity gains. Lower level languages like the >Microsoft developer platforms, Delphi and even Javascript/Python type >environments had the versatility but you had to pay the price in coding >according to the classic, stateless styles. 4D is now allowing us to do stuff >you could do in these languages but there's a great big banana skin potentially >associated with that transition which is productivity. For example when I >started >building widgets in 4D, they could be "very nice" but my productivity >absolutely >plummeted since you need to spend most of the time on designing plumbing >systems, event models and custom data structures instead of solving business >problems which have traditionally been the 4D developer's domain.
And if you give up that advantage, why develop in 4D at all? Can you imagine living without the Current Selection? Tom Benedict Optum This e-mail, including attachments, may include confidential and/or proprietary information, and may be used only by the person or entity to which it is addressed. If the reader of this e-mail is not the intended recipient or his or her authorized agent, the reader is hereby notified that any dissemination, distribution or copying of this e-mail is prohibited. If you have received this e-mail in error, please notify the sender by replying to this message and delete this e-mail immediately. ********************************************************************** 4D Internet Users Group (4D iNUG) Archive: http://lists.4d.com/archives.html Options: https://lists.4d.com/mailman/options/4d_tech Unsub: mailto:[email protected] **********************************************************************
