Slashdot Mirror


Firefox 23 Makes JavaScript Obligatory

mikejuk writes "It seems that Firefox 23, currently in beta, has removed the option to disable JavaScript. Is this good for programmers and web apps? Why has Mozilla decided that this is the right thing to do? The simple answer is that there is a growing movement to reduce user options that can break applications. The idea is that if you provide lots of user options then users will click them in ways that aren't particularly logical. The result is that users break the browser and then complain that it is broken. For example, there are websites that not only don't work without JavaScript, but they fail in complex ways — ways that worry the end user. Hence, once you remove the disable JavaScript option Firefox suddenly works on a lot of websites. Today there are a lot of programmers of the opinion that if the user has JavaScript off then its their own fault and consuming the page without JavaScript is as silly as trying to consume it without HTML."

5 of 778 comments (clear)

  1. Re:why? by Joce640k · · Score: 5, Insightful

    Maybe, maybe not ... but there's definitely a lot of privacy and distracting-advertising issues.

    --
    No sig today...
  2. Simple != Dumb by sjbe · · Score: 5, Insightful

    Why must we dumb down everything?

    More like simplifying. Everything should be made as simple as possible but no simpler. Why have a menu option that never gets used? That is pretty much the definition of pointless. I'm pretty geeky and like to tinker with things but a menu option that never ever gets used is wasteful.

    I cannot remember the last time I disabled Javascript and I'm pretty confident that somewhere north of 99.9% of users never disable it either. Much of the modern web would be useless without Javascript. So long as there remains a method (extension, etc) to disable it if desired (ala NoScript) I really don't see the big deal.

  3. Re:Solution in extensions by girlintraining · · Score: 5, Insightful

    I'm running FF23 beta on my personal system and NoScript is still working as before.

    People seem to be forgetting that javascript can break a lot of accessibility readers. Everything about HTML, CSS, etc., was about separating content from layout. Javascript shits on that entire model, as does Java, ActiveX, and most other plugins.

    Web developers should continue to create websites that don't require javascript, and we shouldn't be in such a hurry to move away from that. The promise of the internet was accessibility, the ability to freely share information, and to connect everything together.

    This push towards app-ification of the internet, the W3C caving to DRM in HTML5... it's after the very heart and soul of the internet. The internet we built, as hackers, as creatives, as professors, academics, researchers, scientists... it's being gutted. And Firefox, the white horse of the "free" internet, in it's 11th hour of need, chooses this?

    They should be ashamed.

    --
    #fuckbeta #iamslashdot #dicemustdie
  4. Re:why? by Jah-Wren+Ryel · · Score: 5, Insightful

    ActiveX was actually smart in the way that it executed fast native code instead of slow interpreted Javascript.

    Yeah, smart like in the way it is smart to give a gun to the guy mugging you with a his bare hands.

    --
    When information is power, privacy is freedom.
  5. Yeah, focus is slipping by Medievalist · · Score: 5, Insightful

    they're trying all kinds of stupid shit and this "the user is a stupid dolt" move from them is just the latest dick move

    Disrespecting the end user is one of the stages of software development team meltdown.