LINUX Message Board - Msg: 10867400

STOCKTALK

We've detected that you're using an ad content blocking browser plug-in or feature. Ads provide a critical source of revenue to the continued operation of Silicon Investor. We ask that you disable ad blocking while on Silicon Investor in the best interests of our community. If you are not using an ad blocker but are still receiving this message, make sure your browser's tracking protection is set to the 'standard' level.

Technology Stocks : LINUX

Public Reply Prvt Reply Mark as Last Read File

Previous 10 Next 10 Previous Next

To: JC Jaros who wrote (1695)	8/8/1999 12:35:00 PM
From: E. Charters	of 2617

We may have Special Excludable X objects in order to preserve legacy compatibility with X-Windows. If we broker them commonly we may be accused of running a Common S.E.X. Object Request (solicitation) Brokerage House and there could be penalties for that. GUI would pass X requests or calls transparently so X programs would run as clients under this Client server system. There may be no reason not to CORBA the architecture if object oriented programming is used. I am a bit leery of CORBA as 4GL programs get so big and then object confusion sets in. Really large programs are better off using standard non-event driven programming techniques. 80% of 4GL language projects fail because of code complexity and bloat. Most of the rescues are written in standard procedural languages that are known to work, like COBOL. If we write databases in XML then there is no need to write them with CORBA standards as XML may eventually form a standard to access many types of databases. But I will admit that where it is likely that procedures, aka objects will be used by other CORBA implementing programs then it may pay to do things according to that architecture. It is a point to ponder. I would like to be assured that the speed, development time and usability of the project would be improved before leaping to any "standard". I would like to see that other large projects of this kind have benefited from such adherence. Don't forget that we may inherit much of the code from an already written code base. This is the advantage hopefully of tackling this project. If we wanted the thing to run fast we would write it in FORTRAN which is faster than C and does graphics well. (OK really good flexible powerful graphics might need another language) It is slightly weak on data structures but is a much better compiler when it comes to nesting and overall structure. C is a functional nightmare with no structure at all. C++ is an even more nightmareish usage of C, with every greater pitfalls and traps lurking under its hidden semi-re-usable code. No less than Ritchie has said that C++ is an abomination and obsolete. If he said it I rest my case. RESERVAC the immense Air Canada dynamic database and reservation system was written in Fortran because they wanted the thing to work, be fast and they had to get hundreds of programmer to write in the language quickly. It is the still the best and fastest program of its kind. I would not want to write such a beast in OOP. You would never get done and if you did it would crash once a day at least. EC<:-}

Report TOU Violation

Share This Post

Public Reply Prvt Reply Mark as Last Read File

Previous 10 Next 10 Previous Next