6 Replies - 3987 Views - Last Post: 03 October 2012 - 12:27 PM
Posted 07 September 2012 - 07:25 PM
Posted 08 September 2012 - 01:55 AM
Secondly, if you are considering that as an impact, then you have to look at the cost to you, the developer. It will increase your development time significantly, and the increase in development time may not be worth it considering the extra traffic will be minimal, and thus the extra income/interest.
Posted 08 September 2012 - 11:05 AM
Posted 08 September 2012 - 12:35 PM
Looking toward the future. When people talk about HTML5 driven sites, they're not talking about serving up static content. They're talking about a page that hosts scripts that drive a display. It is the semantic web nightmare! Sort of. Such sites generally talk to services that describe data as just data, either in JSON or XML. That stream establishes the ideal of markup only for data, just on a different tier.
Posted 08 September 2012 - 04:49 PM
This post has been edited by adn258: 08 September 2012 - 04:50 PM
Posted 03 October 2012 - 12:27 PM
If you're seeing one to two percent of web users disabling it, think about what other sites they're disabling - are these people you really need? If so, you build a non-js view. I don't know how necessary that's going to be, though.