I was not impressed with the blog ... As several commenters pointed out, this kind of stuff goes on all the time. The PHBs are ubiquitous.
Anyhow, that's a nice description of OS/360 et. Seq. I also worked on that system as well as the Unisys (Univac) 1100 Series. Mainframe OS (in the dark ages) were concerned with conservation of resources. Actually, all programming was concerned with conservation of resources, hence the Y2K issues. My impression based on what I've seen and read is that Windows really does not have a consistent architecture. That is one with a "vision," like OS/360, Exec8, VAX/VMS and most of the DEC o/s. There is also a lot of bloat because resources are really cheap. So everyone kind of goes off and does what he needs to do with little regard for how it is done. The growth of computer availability has spawned some counterproductive habits and attitudes. Today you can knock-out a program lickety-split because you have instant notification of errors. Over time this causes sloppiness. Years ago, minor coding errors were significant setbacks to a schedule. I could go on but I seriously doubt that anyone is interested. HALinNY _______________________________________________ Post Messages to: [email protected] Subscription Maintenance: http://leafe.com/mailman/listinfo/profox OT-free version of this list: http://leafe.com/mailman/listinfo/profoxtech ** All postings, unless explicitly stated otherwise, are the opinions of the author, and do not constitute legal or medical advice. This statement is added to the messages for those lawyers who are too stupid to see the obvious.
