Most people make a business case for any feature that they implement or technology that they use. Just because something is a recommended practice does not mean

Most people make a business case for any feature that they implement or technology that they use. Just because something is a recommended practice does not mean it is a best practice. When one looks at the numbers of older non-supporting browsers and people who intentionally turn Javascript off. It does not make a compelling case to adopt an older more costly development model that cannot support the superior feature set of the new development model. Just as COBAL was once a recommended practice it no longer is, the world moved on. As for the 5% or less that still cannot execute Javascript for whatever reason, study after study has highlighted that you spend an exponentially larger volume of money to chase this market than you do on the 95% solution. Money that for all intents and purposes would be better spent trying to increase conversion in the 95% market or adding new revenue stream to provide to the 95% market. So when we talk about best practices we should be mindful of the technical egos, as well as lack of any business grounding of some of the people that make up "Best Practices" that believe their way is the only way and always offset it with marketing 101. JSP has best practices, ASP has best practices and PHP has best practices some conflict with each other and none are weighed against what you are personally trying to achieve. At one point in time in the industry unified programming environments where the DB, the code and the execution platform where rolled up into one technology where "Best Practice". The list of no longer in vouge best practices stretches from hear to Siam. Whenever best practice is seen it should serve as a red herrin that someone may not be listening to opposing view points. People in the technical industry following other people blindly is why we get so much group think and brain dead design patterns from people who believe in the Highlander model of development. JavaScript is standards compliant and that is all that should matter, the rest is just working the numbers.