Taking Action For Free JavaScript
Atticus Rex writes "Today the FSF kicked off a campaign to put pressure on webmasters to make their sites work without requiring nonfree JavaScript. The first target is Regulations.gov, a site the US government uses to take public comments on proposed regulations. Right now, the site requires nonfree JavaScript, requiring citizens to sacrifice their freedom as users to take part in their democracy."
I never realized visiting a website required me to "sacrifice my freedom"!
So the FSF still seems to be able to find ways to make themselves more loony and fringe. Nice job guys!
Wait until Stallman realizes he's "sacrificed his freedom" just by turning on a computer.
There's no -1 for "I don't get it."
The most important aspect of this issue is transparency.
Users should be aware of what's going on.
In theory, it means one should not be able to enter a website without a disclaimer about the site and what it does.
The website authors/owner should be providing the info on automation and/or any info taken from the user and how it is used.it is the user's responsibility to decide if they wish to enter and as such, this means they must agree with the terms of the site.
Now, in the case of federal sites and/or governmental sites, this must be enforced. Basically they should be able to police themselves on this.
More than likely add this to Section 508 when it comes to the US Government.
This issue has been around for a long time when it comes to privacy, cookies use, etc.
To me, it's not about "non-free" JavaScript, but rather, it should be about awareness of the site and it's purpose and whether or not they collect data and what they do with it.
That's not even the tip of the iceberg.
The HTML code you download for the vast majority of the web is protected by copyright. The exact same copyright that protects the Javascript. The exact same copyright that gives the GPL license its power to force GPL upon derivatives.
What about all the non-free images and text taking away your rights?
Wake up people!111
Contrary to popular perception, JavaScript does not run "on the Web site" -- it runs locally on users' computers when they visit a site.
This statement makes no sense. If you actually know what JavaScript is, you probably know it runs in the web browser. If you don't know what JavaScript is, you don't have any perceptions about it whatsoever.
Does this downloaded copy of the JS code come with a license that secures the four essential freedoms to users? Usually it doesn't unless you're on GNU.org or a MediaWiki site.
What meaningful freedom? You can't easily take the source, modify it significantly and use it on the site no matter what license they give you. Yeah, you can hack your own library into the page, but who really cares at all about whatever insignificant javascript the government is using to validate their form. I can kind of see making some kind of fuss about obfuscated javascript (because then it's hard to know what your computer is about to do, if you're the paranoid type), but most javascript is only obfuscated by being poorly written. Either that, or it's condensed for very practical reasons of bandwidth conservation.
I can live with copyrighted Javascript. It's obfusicated Javascript that looks like hostile code that I object to.
Have you looked at Google's home page lately? For a page that appears to do almost nothing, there's a vast amount of obfusicated Javascript involved. Some of it:
(function(){ window.google={kEI:"a62mUcucJYHQiwKgx4DwDw",getEI:function(a){for(var b;a&&(!a.getAttribute||!(b=a.getAttribute("eid")));)a=a.parentNode;return b||google.kEI},https:function(){return"https:"==window.location.protocol},kEXPI:"17259,4000116,4001351,4001947,4003714,4003921,4004320,4004334,4004702,4004788,4004844,4004897,4004943,4004949,4004953,4004971,4005031,4005198,4005731,4005817,4005987,4006191,4006374,4006426,4006442,4006448,4006466,4006541,4006578,4006727,4006806,4006974,4007007,4007009,4007020,4007040,4007055,4007060,4007073,4007077,4007080,4007117,4007118,4007131,4007140,4007158,4007217,4007231", kCSI:{e:"17259,4000116,4001351,4001947,4003714,4003921,4004320,4004334,4004702,4004788,4004844,4004897,4004943,4004949,4004953,4004971,4005031,4005198,4005731,4005817,4005987,4006191,4006374,4006426,4006442,4006448,4006466,4006541,4006578,4006727,4006806,4006974,4007007,4007009,4007020,4007040,4007055,4007060,4007073,4007077,4007080,4007117,4007118,4007131,4007140,4007158,4007217,4007231", ei:"a62mUcucJYHQiwKgx4DwDw"},authuser:0,ml:function(){}, kHL:"en",time:function() {return(new Date).getTime()},log:function(a,b,c,h){var d=new Image,f=google.lc,e=google.li,g="";d.onerror=d.onload=d.onabort=function() {delete f[e]};f[e]=d;!c&&-1==b.search("&ei=")&&(g="&ei="+google.getEI(h));c=c||"/gen_204?atyp=i&ct="+a+"&cad="+b+g+"&zx="+google.time();a=/^http:/i; a.test(c)&&google.https()?(google.ml(Error("GLMM"),!1,{src:c}),delete f[e]):(d.src=c,google.li=e+1)},lc:[],li:0,j:{en:1,b:!!location.hash&&!!location.hash.match("[#&]((q|fp)=|tbs=simg|tbs=sbi)"),bv:21,cf:"",pm:"p",u:"c9c918f0"},Toolbelt:{},y:{},x:function(a,b){google.y[a.id]=[a,b];return!1},load:function(a,b){google.x({id:a+k++},function(){google.load(a,b)})}};var k=0;window.onpopstate=function(){google.j.psc=1}; window.chrome||(window.chrome={});window.chrome.sv=2.00;window.chrome.searchBox||(window.chrome.searchBox={});window.chrome.searchBox.onsubmit=function(){google.x({id:"psyapi"},function(){var a=encodeURIComponent(window.chrome.searchBox.value);google.nav.search({q:a,sourceid:"chrome-psyapi2"})})};})(); (function(){var d=!1;google.sn="webhp";google.timers={};google.startTick=function(a,b){google.timers[a]={t:{start:google.time()},bfr:!!b}};google.tick=function(a,b,h){google.timers[a]||google.startTick(a);google.timers[a].t[b]=h||google.time()};google.startTick("load",!0); try{google.pt=window.gtbExternal&&window.gtbExternal.pageT();}catch(e){}})();
Google's home page was once just HTML with a form. It did about what it does now.
I really wonder if RMS feels able to use a microwave oven. Hrm, maybe he found one from the 70's with a mechanical dial timer and no firmware?
Although I fail to understand why that would be more ethical than having a modern microwave that does have firmware. Why is it okay to not have firmware, but not okay to have firmware unless you have source code? Even if the firmware is so trivial that all it gives you is a power setting and a countdown timer?
Not trolling here; I think this really is a logical conclusion from RMS's public pronouncements. He has publicly denounced the use of any network interface that allows the user to download firmware as a binary blob, unless the full source code for that firmware is available under a license approved by him.
Hang on, he hasn't denounced network interfaces with non-updateable firmware... has he? Maybe he just hasn't got around to that yet.
But never mind; he has denounced Tivo for making an appliance that doesn't allow the user to install any code the user chooses. So I'm pretty sure a microwave would be a problem for him.
Likewise, modern cars have engine computers, so he probably has to drive a car from the 70's or so. Hrm, actually I think he doesn't own a car. I wonder if he is uncomfortable riding in modern cars.
Really I'm glad I'm not RMS.
Who cares what license the javascript has underneath a page that I happen to visit? As long as it runs. It's not like I have to install some evil proprietary flash or java applet to run it. Get a life, FSF!
I have built maybe 30 Javascript heavy websites and not once did I use anything but free Javascript. Not out of any philosophical bent but just that there is so much awesome free Javascript out there in so many forms. Occasionally I stumble on some library where they want money but 5 seconds later I find something free that makes me go oooooh. Or I build it myself.
So instead of going on and on about how much of a waste of time this is I'll suggest a few campaigns of more importance: Better freedom of information acts. Less stupid patent laws. Less stupid copywrite laws. Better privacy regulations severely limiting what data governments and corporations can gather. Better built in security into nearly everything I use so that people can't backdoor their way into my data (i.e. no backdoors into things like Skype). To name just a few of the 100 million more important causes out there.
No, because the problem you're describing is no way related to what TFA is talking about.
You're talking about requiring a certain environment for the page to work.
They're talking about the javascript on the page being licensed to you in a certain way, which has no bearing whatsoever on if it actually works or not.
-- "So they told me that using the download page to download something was not something they anticipated." - Bill Gates
I'm sacrificing my freedom by loading a webpage that is going to run some code which I can look at with any text editor and see exactly what it's doing (though I may need to de-minify it first)?
Honestly, if that is the biggest threat to my freedom these days, we're in much better shape than I thought!
TFA in this case is surprisingly difficult to understand. It reads like it's aimed at the converted, and the rest of us who are more concerned with "does the site work?" and "are there security concerns?" aren't invited. Either that or I'm really missing something, because I can't fathom why in a million years I would ever care in the slightest about this.
-- "So they told me that using the download page to download something was not something they anticipated." - Bill Gates
I can't just rape and pillage every site I want for javascript snippets and samples. I have to read the license for the code first.
Just think how much easier it would be if everything were GPL'd. Then nobody would own anything. Or get paid.
(Yes, I release my code under GPLv3 and LGPL, but that's because I want to, not because I expect everyone else to!)
I do not fail; I succeed at finding out what does not work.
How? Do they even know how the webpages work? We would basically have the web of 1995 in all its slow, clunky awfulness.
You want a web without JavaScript? Go right ahead and make a viable open source alternative that offers the same facility.
Took me a bit to realize what they meant too but they meant the copyright towards the javascript code, not the interpreter itself. Yeah, it's stupid to the point where it doesn't register (especially with the crappy way the summary is written). Who cares if the JavaScript isn't open sourced, doesn't prevent users from learning how the code works and writing their own version (there is obscurification but it's not like that is a show stopper for the dedicated). You still have quite a bit of freedom with javascript, even if it's not EASY. So many other battles that people's time could be better spent.
So I read Stallman's article and am not quite certain that it is completely accurate. I've written a decent amount of JavaScript code, and all of it was built into HTML pages, even if some of it used AJAX to interact with PHP code on the Web Server. It has always seemed to me that that the entirety of the JavaScript code was right there for the user to inspect with a browser's "View Source" option, regardless of whether or not the overall web page was copyrighted. Well, at least it is easy to view the code that doesn't get loaded in a separate ".js" file; you need to use a browser's Developer Tools to access the "include" stuff. I am of course aware that there exists Server-Side JavaScript, and when it is used that code does not get sent to the browser. However, since it runs on the Server, not even Stallman can complain that the user who connected to the Server is being asked/required to run that non-free JavaScript code (But obviously if the web page is copyrighted, it may qualify as including non-free JavaScript code.)
Accuracy aside, there is a different issue that is personally bothersome. I'm a good programmer and have been writing code for a long time, working with a variety of languages --I have actually enjoyed Assembly Language; many can't say that! But I haven't been able to find a "best fit" type of job that lasted more than a few years, and so my income-situation is not the best (nor even remotely near to "the best"). I'm sure it is quite easy for someone who has a decent steady income to write and give away software. But when you need to sell it to put food on the table, copyright is supposed to be an author's friend. As an example, suppose I put a few years of effort into creating a nice unique web site, free for users and paid for by advertisers. Do I want that unique-ness to be copied immediately, all across the Internet, and my ad-revenue proportionately diluted, by giving away the source code? What do I deserve to earn, financially speaking, for those years of effort? Remember the children's tale of the Little Red Hen? The assumption behind Free Software is that what you offer will get improved and come back to you, thereby benefitting you. It ignores the fact that that process takes time that you might not be able to afford!
So, what is the Answer to that conundrum, besides "Obtain the nice-income job that lets you afford to give away software"?
God, grant me the serenity to accept the things I cannot change,
The courage to change the things I can,
And wisdom to know the difference.
The real question we should be asking ourselves is why is there so much redundant JavaScript libraries out there? Date Pickers, Fancy Dialog Boxes, Slideshows, Accordion Components, Menus, Widgets, etc all use JavaScript. How come the HTML standard has not implemented these common components?
Some of them are in HTML5, but browsers haven't implemented them yet, and since everybody uses JavaScript anyway (and will continue to use JavaScript to support older browsers for the next decade) there's no pressure for browser devs to implement them.
$x='S24;r)>63/* h@<5+oZ)32"5cz';$me='phroggy'x$];
$x=~y+ -xz+\0-Tx+;print$_^chop$me for split'',$x;
This is not a private entity -- government services should be available to everyone without a requirement to purchase "widget A from coporation M". Until that becomes a rule -- FSF is doing a very good job.
I really like this idea.
I don't.
It has one great flaw - in order to do like FSF asks and fill out the form on regulation.gov, we have to use a browser with non-free JavaScript.
So in essence, RMS asks us to use non-free JavaScript!?
It's this kind of misguided fanaticism by the FSF that makes hairyfeet despise the greater Linux community and ruin any chance of demonstrating that yes, there are some Linux users who are actually reasonable humans.
Let's ignore the whole copyright issue of EVERYTHING else on the website. The CSS, the HTML, the words, and so on. The article talks about "it prevents people from understanding, modifying and building on the programs they are running" Well no it doesn't. Other than it being copyrighted. People could still understand it, modify it... But legally you can't run it, just like you can't take the text or the images and stick them on your page. Or is Richard suggesting we should do that as well?
I use it all the time. Very few sites are allowed to run javascript at all.
I've decided to stop wasting my time responding to AC trolls/sockpuppets... so if you want a response from me... login.
That doesn't make sense to me. Of course JS code, HTML, text, images, movies, etc. will be copyrighted. It's just a communication medium. Just because it is relatively new and the InTeRnEt doesn't mean it should all be an open collaboration with everything given away by default. Demanding 'free' Javascript is a bad message, imho. It gives the sense that it should all be free and therefore it might even be ethical to steal.
Don't get me wrong, I was a Linux kernel contributor for several years and I've released my own projects under L/GPL. But, I'm also a commercial programmer who knows the importance of keeping proprietary code protected. I don't find the two in conflict. I'm even on the fence for thinking a semi-standarized web DRM might not be a bad thing.
Part of my distaste on the matter stems from students who email me about a few papers I posted on the web while in college. Several blatantly told me they are going to submit my paper with their name at the top but just wanted a few clarifications in case their prof asked them any questions. Pissed the hell out of me. It was completely lost on some that that was stealing, plagiarism, and cheating. The web isn't all public domain and it wasn't meant to be and it shouldn't be or else it would become a very dull desert wasteland.
Having "non-free JavaScript" on a site seems no different to me than reading materials that are copyrighted. Does Stallman not read anything that's copyrighted? What's the problem with that? I just don't see the negative effect here.
What Stallman and the FSF are complaining about is bone standard ECMAscript, nothing proprietary about it. Minification is done by web administrators to conserve bandwidth and make their pages load faster. Stallman deliberately used a loaded term to paint this like it's worse than it is. If he'd just come out and said "People need to use more readable javascript" he'd look like an idiot So he fudged things a bit, coined a new phrase which if you read it literally doesn't make sense, then wrote a big essay about it. What's next, is he going to ban PERL because no-one can read it? Is everyone going to be required to use Python because it's the most readable language?
If the server ran ActiveScript or Flash, I could see getting excited, but it's just minified javascript. This is the problem, were Stallman to describe minified code to most people they wouldn't see the 'evil' in it. So he invented a new phrase to try and make the rest of the planet see things the way he does.
No it's not. It's about the license the script is given to you under.
It has nothing to do whatsoever with what the script actually *does*, or if it's harmful. Code doesn't magically become safer because the license changes.
-- "So they told me that using the download page to download something was not something they anticipated." - Bill Gates
Bollix... next..
The article specifically talks about government websites, I can see if I already paid for it through taxes, then why should not be able to modify it and run in my browser on my machine as I see fit ?
This isn't related to copyright, you aren't distributing the code by running the code in your own browser on your machine.
New things are always on the horizon
FAFSA does not require IE. It throws big scary warnings about browser incompatibility at the user, but it does not stop you from continuing in Firefox or Chrome. I filed FAFSA from 2006-2009 in not-IE without issue.
Also, you cannot change the code on the server(sort of, if you intercept calls at the browser level you could)
There already exist tools to "intercept calls at the browser level", such as Greasemonkey. Non-free licensing of JavaScript code prohibits end users from sharing their improvements with other users of Greasemonkey.
If we had a choice to use the web site without the script that "the author licensed [...] that way", it'd be fine. But a lot of pages that use non-free JavaScript won't work at all with script off.
Javascript can certainly cause a lot of problems, but none of them are really related to it being non-free. Sticking a GPL on top of the Javascript code doesn't really solve anything. It doesn't make webpages more accessible or machine readable, it doesn't make it load faster, it doesn't make it run faster and it doesn't even make it easier to modify. If the server starts to ship on updated Javascript my Greasemonkey scripts would break just the same no matter if the Javascript is GPL or not. Lots of the time the Javascript code isn't even code that does something interesting, but just used for transition animations and such because CSS3 is not yet ready for widespread use.
I think the FSF should better spend their time on advocating good web practices, encourage people to provide APIs for their websites, make sure that data can be important and exported from the cloud and such. If it's Free Software or not doesn't really matter, as while it runs on your computer, you don't really control it either way, as it all depends on what kind of data the server ships to you. If the data format from the server changes, all your Free Software Javascript would be rendered useless.
Forgive me if I post comments covered better by smarter people but I have just spent the past hour pacing in the hallway after reading this.
My initial reaction was "Non-free JavaScript? RMS must have glaucoma because his herbal remedy is really impacting his judgement". JavaScript is open source. As a computer security duck I can tell you that JavaScript is easily altered on any page you visit, and only a fool would license their JavaScript code... or worse "open source" it like Al Gore did to his web page just before we found out what a "chad" was. Calling a set of JavaScript code "closed source" is similar to closing the source on a batch file or shell script, or trademarking/copyrighting an arrangement of flowers or dead bees. It is possible to lay claim to such a "design" but as to how it could be enforced is beyond me.
Then I read some comments and people seemed to think this had to do with the readability of the JavaScript as "minified" JavaScript is too obfuscated to read by a lay person (by lay person I mean non-JS compiler). But this is silly as many plugins that allow you to alter the JavaScript you run on your browser when you visit a page will also easily de-obfuscate the JavaScript. So readability is more about presentation and the presentation can be trivially altered.
But, I have come to peace with the basis of the article, that there exists something called "non-free JavaScript" and that pages can implement such a thing. Here is how one can implement Non-Free JavaScript, if you use a JS library such as Sencha ExtJS (with the commercial license) and offer no alternate HTML only page. Sencha ExtJS with the commercial license is not GPL, so the license is not "free". And with the lack of an HTML page (where you kill off your search engines and section 508 ADA usability compliance), then RMS can't use the page in the pristine "free" form he desires as a nutty free software advocate.
This issue is a lot like having a "death and murder-free dinner party" for insane vegans. Normal people would be happy to throw a burger on the grill and drink some beer but people like RMS would amplify decisions like eating meat kills everything and hurts the environment and that beer prevents kids in Iceland from learning to read (with a 2 hour explanation as to why). Why can't the FSF install Firefox and use the web the way a given developer intended is beyond me. People who block JavaScript are jerks and people who block ads are theives. If you don't like a given web page, don't go there. The rest of us are sick of hearing you old coots yelling "get off my lawn", or more accurately quoting Sheldon "you are in my spot". Take some lithium and enjoy 2013.
..the same exact thing. Their site won't work unless you download and execute their proprietary javascript, thereby creating a specific environment within your browser.
A more careful (and slightly more believable as well) analogy would be that the municipal government's site only works with MSIE 6 running on Windows XP, but they do have a download link to a free-as-in-beer VM image which contains that software (And they expect everyone to use that VM, even people who already have Windows.) You're apparently allowed to click the link and use the VM image, but what exactly you're really allowed to do with it, is murky unless you research it.
Lawyers working at FSF looked into it, and found out that you're not allowed to improve, repair, or otherwise maintain this code which is required to use this taxpayer-funded government service. If it has a bug (or malicious bit) which happens to exploit your VM containment, then sucks-to-be-you: your only two legal recourses are 1) to fix your VM instead of removing the exploit itself, and just live with the hostile code constantly probing your containment. [and I'll admit that's a good idea nevertheless.] 2) Or completely replace the entire environment (what Berkeley did to AT&T's Unix) since you aren't allowed to create derived works ; make your custom WINE environment do whatever is needed to interoperate with the government's service. If that means implementing some MSIE6 bugs, so be it.
And on the topic of whether or not Microsoft and Adobe have actually consented to you downloading and using that VM, the lawyers can't even find a solid answer (Microsoft and the webmaster probably did negotiate some kind of license, but neither of them ever happened to tell you anything about it) so the lawyers are tempted to assume that copyright law prohibits you using the VM. If Microsoft ever did happen to sue you over it, could you prove you were allowed to copy that VM?
"Believe me!" -- Donald Trump
This is another one of those RMS things which really does seem pretty nitpicky and impractical, at the time it's written but history shows that whenever you later look back, RMS is almost always right.
Javascript is so transient, so unimportant, and so close to the blurry line between code and content (though I'm surprised to be reading so many opinions here which are placing it on the "content" side). Our browsers are getting pretty decent at sandboxing these days, so the consequences of running unmaintainable and unauditable code within them, seem light. Who really needs maintainance for code that you only use for a few seconds and then throw away?
But it's creep. Unless I have my browser only run Javascript from whitelists, the "normal" operation is that it's doing something (running all kind of crazy proprietary stuff) that, outside the browser, just doesn't happen. My machines aren't are "pure" as RMS' machines but even so, there are really only so many places where I still have unmaintainable and unauditable code. The browser multiplies that by thousands.
It's funny; I normally don't go adding thousands of proprietary PPAs to my Ubuntu machine, and tend to be pretty conservative about what I allow to be installed. Yet my browser still isn't using a whitelist for Javascript. That's not entirely sane or consistent, is it? No matter where you stand on the Free vs proprietary spectrum, you get to call me a hypocrite. (Fortunately, I probably get to call you one right back -- unless you're as hardcore as RMS or as resigned as an iPhone user.)
They're individually inconsequential (I think!!), but I sure spend a lot of time in the browser. What's otherwise a fairly trustworthy machine, seems to be hanging by a thread: the browser's correct virtualization of the Javascript universe. If I'm really ok with that, then you'd think I'd also have some Windows or Mac OS X virtual machines around too, to further run more unmaintainable and unaudited code for my convenience. Why don't I? Maybe it's simply because doing that wouldn't really give me any more convenience. But maybe I'm inconsistent because I don't have my shit together, mentally.
I think there's a valid concern here, it's just hard to say it's important or what (if anything) to do about it. But I remember when "The Right to Read" pretty much got the same opinion from me.
As far as what to do about it, FSF's proposal seems pretty modest: don't have government actively making the creep deeper. We have enough to worry about without our own government putting us further at risk. Regulations.gov shouldn't be distributing a bunch of proprietary code to citizens; leave that sort of thing to commercial sites. Even if it's currently believed that the current version of that code is harmless (it wouldn't totally surprise me if some people have illegally(?) audited the Javscript), it's not a best practice, and outside of exceptional-because-we-don't-have-our-shit-together web it's something we normally wouldn't do or permit. If regulations.gov told you to download and execute regulations.exe or the iOS app as the only way for citizens to get some information from them, I'm sure plenty of people would be screaming. This is the same, but also different, by degrees. Whether it's two degrees or ten, though, I don't know...
As copyright owner of this comment, I authorize everyone to defeat any technological measure which limits access to it.
I specifically remember it not working, it is possible that they simply blocked functionality for non-IE browsers. Obviously your mileage may vary.
When I was on unemployment, the state of Oklahoma's unemployment website thing actively prevents you from using anything but IE 7 and below. (IE8 didn't work, IE9 was still in beta at the time). The way I solved it was using a user agent switcher with Firefox. Everything worked as expected afterwards.
1) Even though ECMAScript is an official spec, Javascript with obfuscation is now "wrong". Even though its an interpreted language and not encrypted, the fact that it's not easy to debug it is wrong. That means all perl is wrong, cause you really can't read the code anyway. Nevermind the fact that single character member names help with bandwidth costs. You'll pay more, because, well, Stallman says.
2) BSD is bad because of the license clause, adding a license was too unwieldy. Adding a license to FSF code somehow is ok, because, well, Stallman says.
If we had a choice to use the web site without the script that "the author licensed [...] that way", it'd be fine. But a lot of pages that use non-free JavaScript won't work at all with script off.
Then don't view the website, you don't have the right to force them into your ideology. And if you must view it then do it on a computer other than your own.
My understanding is that greasemonkey adds scripts that modify the page, rather than modifying the incoming javascript, but I don't know much about how it works under the hood, perhaps I'm mistaken. Even so, there is nothing illegal about running greasemonkey or sharing greasemonkey scripts, is there? Which means that changing the license for the page's javascript doesn't add anything from a legal or practical standpoint.
If I browse to a website that executes proprietary code in my browser, non-free code is executed. But is this really any different than if I browse to a website that executes proprietary code on the SERVER? Does it matter which CPU runs the code?
--- wad
For a minute there I thought that there was a new technological invention called NonFreeJavascript. OK
You're also forgetting the part where W3C was sitting in their ivory tower doing nothing useful, so the browser vendors (sans Microsoft) got together and formed their own group, WHATWG, which created HTML5. W3C only decided to adopt HTML5 after it became clear that all the browser vendors (except Microsoft) were already committed to implementing it. (Microsoft didn't get on board until W3C's adoption.)
But you're right, the expectation is that JavaScript is a big part of how the web is supposed to work.
$x='S24;r)>63/* h@<5+oZ)32"5cz';$me='phroggy'x$];
$x=~y+ -xz+\0-Tx+;print$_^chop$me for split'',$x;