On 17/12/10 00:35, Jeff Nowakowski wrote:
On 12/15/2010 04:31 PM, Nick Sabalausky wrote:
But if you're going to make, say, a mortgage rate calculator,
excluding Lynx or requiring JS makes absolutely no sense whatsoever.
This is actually a good example of why you might require JavaScript.
Here, JavaScript is useful to the end user because it doesn't require a
request and response to the server, so everything is faster and smoother.
Supporting both JavaScript and plain HTML takes extra work for little
benefit, since the vast majority of users have it enabled.
It's not 1995 anymore.
True its not 1995 anymore but in 2010 JavaScript has not made any
significant headway in language maturity since its lame-day incarnation
a decade ago. The paradox, of course, is that this lame language has
attained ubiquity (at least in the web client arena) and that there
seems little else in the way of competition as to a truly web-standard
offering (aside from plugins that the big end of town want you to
install, or try to install on your Open Source Browser without your
permission).
