Re: NewEra vs VB/Delphi

On 23 Jun 97 at 19:02, Michael Segel wrote: > Billy Wheeler wrote: > > OK, so you need to do your penalty shot! Since you probably can't > drink in Kuwait, I think you need to head over to Ryadia (?sp?). ;-) Riyadh? In Saudi? Hell, you *definitely* can't drink there! :-) > Ahh, this is fairly simple. > Each object should have a tag associated with it. What I mean is > that at the object class (root class) you should have some form of > descriptor. This descriptor should allow for a numeric ID, a title, > and a isa field. (ie isa Window_object;) Hm. Sounds nice and easy. So you would have (somewhere): 1. helpWindow WindowObject 2. customerWindow WindowObject ... But where? And how would you find your actual source code and header files if they're all called window1.4gl, window2.4gl, etc? My point is that any way you implement this will have some practical consequences, and we're happy with the practical consequences of the way NewEra is implemented, whether we're right or wrong! :-) > > Nope. We've found it cheaper to write even small, stand-alone apps > > in NewEra and pay the outrageous licensing fees than to write in > > VB. As the complexity of the app scales up, we believe the > > deployment cost becomes less of an issue. > > > Yes and no. > Remember I'm not advocating anything from Mr. Bill. ;-) > The problem is that N.E is not the best tool based on > price vs performance, and portability. (Reusability and > portability are somewhat tied together.) Well, what is the best tool then? Every tool has its compromises. All I'm saying is that if you take the trouble to become an Power Developer (TM), NewEra can be very powerful. > > At the risk of being mailbombed: "LONG LIVE NEW ERA!!!" :-) > > Mailbombed? No. Beshoften? Definately. ;-) Probably! :-) -- Ciao, Billy Nose to the ground and ear to the grindstone in: Kuwait