Silicon Investor (SI) -- The First Internet Community

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 : Microsoft - The Evil empire -- Ignore unavailable to you. Want to Upgrade?

To: Pink Minion who wrote (581)	1/21/1998 11:15:00 PM
From: Kal	Read Replies (1) \| Respond to of 1600

You are a prime example of the state of affairs for the industry. Go back to school and learn about OO development. More lines of code usually means sloppy programmers, or more likely sloppy management of the architecture. NT at 30 million lines of code is scary. to the best of my knowledge, this is how the whole inddustry is. maybe it is shifting more towards OO, but not as much as people people in the industry think. So there is a way to go. from my experience and the programmers I work with, OO development initially take more time. The project might take abit longer but the result is more managable and flexible. If the manager wants the result fast, we tend to slap code together to just get it done and rnning. it's not as simple as what programmers want to do.

To: Pink Minion who wrote (581)	1/22/1998 11:48:00 AM
From: K. M. Strickler	Read Replies (1) \| Respond to of 1600

It is interesting to think that there are those who think that all code can be OO! When you are actually programming in the heart of the computer, OO may not really apply. As an example OO would be good for writing a program for an extremity, like clipping your fingernails, but open heart surgery can be a little more deadly. Additionally, OO is in itself more 'codey' than 'machine' language because it usually handles more event types. As for the industry, OO works well for developing application programs which require and use many recursive routines. OO is the only way that code can be managed by many programmers in industry. Before, when code changed, and the original programmer was not available, it took a long time for another to learn the code and fix or patch the program. In order to be efficient in industry OO is used not because of its resource efficiency but it manpower efficiency. In the beginning, nobody had the computing power we enjoy today, and the OO code in comparison is really 'bloated'. Look at the size of some of the source code that is required to generate the final product. The old systems would 'barf' on files this size. I wrote a program that resides in 65K, that same program in WINDOWS is OO and 300K, the source files are about 5M. Talk OO, talk BLOAT. As for NT's size, it is directly proportional to the work that it has to perform. You know that a program that writes "HI" on the screen was significantly easier to write and debug, than the program that launches a space shuttle! Are you calling the space shuttle launch program 'bloated' or 'complex'.