Mark:

Mark Wonsil wrote:

>Hi Olav,
>
>  
>
>>What ever happened to idiot proof the code.  This means we should code to
>>allow an idiot to understand what need to be done, not have idiots code and
>>everyone else try to understand them.
>>    
>>
>
>First, I prefer bullet-proof since some very smart people can break code. :-)
>
>I think that's the point of Progressive Enhancement. Start simple and
>make sure it works. Add functionality as you go along.
>  
>
This is the problem with Micro$oft.  They add functionality and break 
code as they go.  If it was to be re-designed, maybe it would run faster 
and better.  Every time they add additional code to one place, they need 
to make sure all the other code still works.  The fact that they send 
out countless number of patches, states alot about how they code.

>Remember that writing "web applications" is not the same as coding for
>MPE. In MPE, you have to handle the different architectures, versions
>of OS, versions of Image and VPlus, and maybe different terminals. A
>web application may run on an iPhone, an web browsers (Netscape 3, 4,
>5, 6, 7; FireFox 1, 2, 3 on Windows; IE 3, 4, 5, 6, 7, 8 on Windows;
>IE on MacOS; IE on OS X; Opera on Windows; Opera Mini; Safari on OS X;
>Safari on Windows; Google Chrome; Windows Mobile phones; Android
>Phones, Nokia phones, the AOL browser (at one time); and at any time,
>any of these users could change their font setting, turn off styling,
>deny plug-ins or turn off scripting altogether. And don't even get me
>started about server languages from ASP to Zend PHP...
>
>Meanwhile, HTML 5 has turned into a fighting match between WHATWG and
>the W3C. Standards aren't set but browser companies are adding
>features already.
>
>It's official: the system can't be idiot proofed!
>
>Makes one long for the days of Cobol85/XL....
>
>Mark W.
>
>* To join/leave the list, search archives, change list settings, *
>* etc., please visit http://raven.utc.edu/archives/hp3000-l.html *
>
>  
>
As I stated earlier, it needs to be done right the first time.  In the 
past, I have coded for many different versions and OS's, using Speedware 
4GL code, and they all worked perfectly before I put them into 
production.  To this day, very little (if any) of my code in production 
has been broken if left in its original version.

Olav.

* To join/leave the list, search archives, change list settings, *
* etc., please visit http://raven.utc.edu/archives/hp3000-l.html *