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"!
The BIOS, you say? Stallman's way ahead of you there.
You can hold down the "B" button for continuous firing.
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.
Ah yes, nothing says "freedom" like buying a product from the Chinese government.
There's no -1 for "I don't get it."
You do realize that Stallman uses a Yeelong lemote right? It's a computer that runs on entirely free (as in freedom) software and firmware: https://en.wikipedia.org/wiki/Lemote#Netbook_computers
So the FSF still seems to be able to find ways to make themselves more loony and fringe. Nice job guys!
Yes, this is pretty pathetic. There are plenty of areas where free software is very important, such as basic computing infrastructure like compilers, operating systems, networking, web standards, and audio/video decoders. But instead they are focusing on the script that makes text blink on some random website.
Look this isn't quite so pathetic as you think. The accessibility tools on Linux often depend on running really old browsers on the console. First hand experience. We have upgraded them for ipv6 etc but working js is another matter.
You are aware of what minification is, right? Having nicely formatted javascript also means that you waste a lot of bandwidth sending all that format information that 99.99999999% of users will never look at. There are reverse-minification tools out there if you really want to look at the code.
Monstar L
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
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"?
Stallman wants users to do exactly that, wrt regulations.gov and others, in the case "when the use of the nonfree software aims directly at putting an end to the use of that very same nonfree software". That's how he developed GNU: until it was more mature (and Linux came along), he used non-free Unix to test.
You can hold down the "B" button for continuous firing.