Linked by Thom Holwerda on Tue 30th Jun 2009 15:56 UTC
Mozilla & Gecko clones As was anticipated, the boys and girls at Mozilla have released the final build of Firefox 3.5 today. Firefox 3.5 - originally supposed to be 3.1 - comes with many welcome improvements, chief among which is support for HTML5 audio and video tags.
E-mail Print r 12   · Read More · 63 Comment(s)
Thread beginning with comment 370891
To view parent comment, click here.
To read all comments associated with this story, please click here.
RE[4]: Javascipt Speed
by sbergman27 on Tue 30th Jun 2009 17:10 UTC in reply to "RE[3]: Javascipt Speed"
Member since:

I would agree that a server-side approach is to be preferred. It is *usually* the better technical solution when it is feasable. What I disagree with is the idea that graceful degradation to accomodate those people who refuse to enable Javascript is somehow sacred.

If people refuse to enable javascript they should expect to miss out on stuff. If they cannot use Javascript, do to physical disability, then they should complain to their vendors of screen interpreting software.

Although, as Jacob has reported, there are, apparently, good options today.

Edited 2009-06-30 17:12 UTC

Reply Parent Score: 3

RE[5]: Javascipt Speed
by supercompman on Tue 30th Jun 2009 21:04 in reply to "RE[4]: Javascipt Speed"
supercompman Member since:

I can understand people's desire for graceful degradation of sites, but I see Javascript as quickly becoming just as important as HTML. Web sites are no longer just about disbursing content, and often times are not just web pages, but highly interactive applications. The web isn't just here to replace the likes of newspapers and books, but in many ways it's here to surpass them for content distribution... not just static content, but also interacting with the user while providing information. The web used to be just about displaying content... those days are going away quickly.

As for the people that disable Javascript, they usually seem to do it because some web sites abuse it in ridiculous ways that take away from the user experience rather than add anything useful. Sometimes this happens due to developers trying to do more than the platform is ready for, but usually it's due to very poorly written, memory leaking, CPU burning code that the authors should be ashamed of. Javascript is a good technology, but like any technology it can be abused.

Reply Parent Score: 2