This information HAS errors and is made available WITHOUT ANY WARRANTY OF ANY KIND and without even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. It is not permissible to be read by anyone who has ever met a lawyer or attorney. Use is confined to Engineers with more than 370 course hours of engineering.
If you see an error contact:
+1(785) 841 3089
Take the LAMP stack - A Linux system running Apache and Mysql to support Php. Not a bad system, but look what happened. Under native HTML we have CSS for formating which works pretty well, but then people couldn't resist adding java to extend the formatting. Then there is the jquerey extension and Ajax and soap -- and now you end up with a web site that take several skill sets just to support.
The added features just are not worth it because the cost of supporting this stack of kludges is just too high.
We can look at any one of a multiple of commercial sites that pull in content and gadgets from perhaps a dozen domains - load speed and reliability drop like a rock and anyone with a clue about security should realize that if you are getting content from 10 sites that there is a 10x greater likelihood that one of the servers has been infected.
Good software engineers need to realize that keeping the number of technologies on the lean side is what we need - and that if marketing folks are calling the shots that you should exit anyway as you will be blamed when the system eventually fails. (At least make them put the decision to override your advice on paper with signatures.)
There is also a tendency to see the new bells and whistles and forget what long term consequences each brings. Going back to the LAMP stack - one can do all that is needed with out using java. This might require a bit of work - but if you can code it in PHP and CSS you have eliminated long term support problems.
|Top Page||wiki Index|
(C) Copyright 1994-2019
All trademarks are the property of their respective owners.