News for hackers. Stuff that matters.
Re:Reasons Not to Use Google (2015) by jasode on Thursday August 29, 2019 @11:56AM (#20830627)
>In general, most Google services require running nonfree Javascript code. If you refuse to run that (for instance, by running LibreJS), you'll see that you should not use those services.

Well, I use Google Maps just about every single day so Stallman's advice banning Javascript is way too hardcore for me.

But for sake of discussion, let's entertain what he's suggesting. What are the most practical alternatives to avoid Google's Javascript maps in 2019?

- other websites like Bing Maps and even openstreetmap.org also don't work without Javascript

- using local software like old CDROMs of map software means I'm using data that's 20 years old because no mainstream software publisher (e.g. Microsoft Streets, DeLorme, etc) is selling it and only cover a region instead of the entire globe. Also that CD software is proprietary and not free-as-in-libre.

- using folding paper maps like Rand McNally have similar problems to CDROMs -- the maps are old and more cumbersome.

- other alternatives I overlooked are ... ?

Inevitably, this leads to the condescending question... "How did we get by _before_ Google Maps?!?"

I got by in the past by making the usage of maps more inconvenient.

EDIT to replies about OpenStreetMap: Last I checked, OpenStreetMap doesn't have publicly accessible satellite images or 3D/birdseye views or street-level 360 degree views. Openstreetcam is missing a lot of roads. I use that type of photographic imagery even more than the line drawings of streets. Is there a practical non-Javascript alternative for that data?

Re:Reasons Not to Use Google (2015) by 153791098c on Thursday August 29, 2019 @12:44PM (#20831152)
He has nothing against javascript. He is against non-free javascript which is just non-free software running in your browser. Using Openstreetmap is fine because you don't have to run non-free software on your computer.

Almost all proprietary javascript is obfuscated and tracks everything you do, will identify you and can compromise your system. It's no different than any other non-free software maybe with some better (but nowhere near perfect) isolation from your system provided by the browser you are using.

There are also pretty good free mobile map apps that are on f-droid.

Re:Reasons Not to Use Google (2015) by goda90 on Thursday August 29, 2019 @12:01PM (#20830671)
OSM data can be used with all sorts of software though and not just the website. I imagine at least one of them is free software.
Re:Reasons Not to Use Google (2015) by cycloptic on Thursday August 29, 2019 @12:15PM (#20830849)
The website (and all of the mapping tools) are free software. The repo is on their github: https://github.com/openstreetmap/openstreetmap-website

For mobile I recommend OsmAnd: https://github.com/osmandapp/Osmand

Re:Reasons Not to Use Google (2015) by TulliusCicero on Thursday August 29, 2019 @12:31PM (#20831007)
I doubt there are any web clients that don't use JavaScript, though. How would that even work?

Like, I can understand being peeved at the use of JS for text that really doesn't need it. But something like a mapping app, I don't see how you get around it.

Re:Reasons Not to Use Google (2015) by dllthomas on Thursday August 29, 2019 @02:06PM (#20832070)
But the complaint is being misread. In "require running nonfree Javascript code" Stallman isn't saying "require running Javascript code, which we all know is inherently nonfree". He's saying "require running particular Javascript code which in this instance is nonfree." A web client that uses free (as in speech, not as in bird) Javascript code is presumably fine.
Re:Reasons Not to Use Google (2015) by saagarjha on Thursday August 29, 2019 @12:34PM (#20831049)
He's not banning JavaScript, he's banning nonfree JavaScript. I'm sure he'd be happy to use a mapping service that was licensed under the AGPL.
Re:Reasons Not to Use Google (2015) by millstone on Thursday August 29, 2019 @12:26PM (#20830950)
It won't satisfy rms but seriously: Apple Maps, which is actually good now.

The Maps app on Macs and iOS does not use JavaScript. It also supports satellite and 3d views, and the street view shipping in a month looks better than what Google offers:

https://twitter.com/rvdsteege/status/1139264604918485005

Re:Reasons Not to Use Google (2015) by eloisant on Thursday August 29, 2019 @12:33PM (#20831036)
He doesn't want to use Javascript because he doesn't want non-free software (the JS code) running on his computer.

Using a proprietary software on a proprietary OS is not going to be any better.

Re:Reasons Not to Use Google (2015) by adrian_mrd on Thursday August 29, 2019 @12:46PM (#20831174)
Serious question: why is JavaScript not free (as in ‘freedom’ to use)? Who is the owner of JS and do web browsers have to pay for it?

edit: tried to make my questions clearer :)

Re:Reasons Not to Use Google (2015) by hiq on Thursday August 29, 2019 @12:57PM (#20831329)
You can read https://www.gnu.org/philosophy/javascript-trap.html.

Note that the discussion here is about JavaScript code, not JavaScript the programming language (there seems to have been some confusion in this thread).

Also note that being able to read the code doesn't entail that the code is free as in freedom (i.e., released under a corresponding license). If you share some non-trivial[0] code of yours on GitHub, or deploy a website with your own non-trivial JS code, it still fully belongs to you, and people are not free to reuse it without asking you.

[0]: you probably cannot claim much for a hello world even if you wrote it yourself

Re:Reasons Not to Use Google (2015) by adrian_mrd on Thursday August 29, 2019 @01:40PM (#20831816)
Thanks for that link and info. My reading is that it seems the GNU’s/FSF’s issue with JavaScript is that the code is not always available (to view/peruse):

“It is possible to release a JavaScript program as free software, by distributing the source code under a free software license. If the program is self-contained—if its functioning and purpose are independent of the page it came in—that is fine; you can copy it to a file on your machine, modify it, and visit that file with a browser to run it. But that is an unusual case.” [0]

JS code can obviously be client-side (generally readable in a browser via View Source, but not always, unless I am mistaken) or server-side (not generally readable, unless explicitly shared by the devs).

But based on [1] and [2] and [3], it appears that JS the language is owned and maintained by ECMA, which is a not-for-profit standards org.

So then I’m still a bit confused as to who whose lawyers would be coming after you if you published some JS code on Github or your own web-site? Not the ECMA’s right?

[0] https://www.gnu.org/philosophy/javascript-trap.html [1] https://en.m.wikipedia.org/wiki/JavaScript [2] https://en.m.wikipedia.org/wiki/Ecma_International [3] https://www.quora.com/Who-is-the-owner-of-javascript

Re:Reasons Not to Use Google (2015) by cycloptic on Thursday August 29, 2019 @02:11PM (#20832113)
You can publish as much of your own javascript code as you want under any license on your website or github, or anywhere. The issue they have is not with the ownership of javascript the language. The issue is that if you wanted to take the frontend code to Facebook, Google Maps, Office 365, or something like that, and modify it to create your own version, you have two problems. One, that it probably isn't allowed by the license and the Facebook/Google/Microsoft lawyers could come after you if you tried to redistribute it. Two, it's likely it will be very difficult to attempt to do that because the code is intentionally obfuscated by a javascript minifier.
Re:Reasons Not to Use Google (2015) by adrian_mrd on Thursday August 29, 2019 @03:06PM (#20832581)
Thanks for that.

So really their (FSF/GNU) issue is not with JS at all, but with devs who don’t licence their code under a free software licence? In other words, who enforce the copyright of their own algorithms?

What I also find a bit confusing (inconsistent?) with this stance is that a dev can do a reasonable amount of interesting things with HTML+CSS+SVG (obviously there are limits on the ‘interaction’ side of things), and assumably devs can also licence their HTML+CSS+SVG under whatever licence they wish: so then why pick on JS?

Re:Reasons Not to Use Google (2015) by cycloptic on Thursday August 29, 2019 @04:15PM (#20833186)
I think they would if we got to a point where HTML+CSS+SVG alone was turing-complete and became useful enough to perform general computations, and large programs were written in it.
Re:Reasons Not to Use Google (2015) by y4mi on Thursday August 29, 2019 @01:02PM (#20831387)
Try downloading their code, use it on your site and tell us what their lawyers thought of that argument after you've brought to court for copyright infringement.
Re:Reasons Not to Use Google (2015) by zucker42 on Thursday August 29, 2019 @12:35PM (#20831051)
You are misunderstanding Stallman's argument. He doesn't have a problem with Javascript. He has a problem with non-free javascript. He probably would have even more of a problem with Apple Maps because it's an entirely proprietary program.
Re:Reasons Not to Use Google (2015) by saagarjha on Thursday August 29, 2019 @12:30PM (#20831000)
Note that Look Around only supports a small set of locations currently.
Re:Reasons Not to Use Google (2015) by overcast on Thursday August 29, 2019 @11:59AM (#20830659)
The most practical alternative is using a real map.
Re:Reasons Not to Use Google (2015) by TulliusCicero on Thursday August 29, 2019 @12:32PM (#20831016)
I remember the days of using real maps instead of mapping apps on my phone.

Those days fucking sucked.

Re:Reasons Not to Use Google (2015) by overcast on Thursday August 29, 2019 @12:59PM (#20831356)
Well, if you're going to cry about using something that runs on the entire web, then that's your alternative. Or grab a Garmin, though I'm sure Stallman probably believes there is a mind control listening device in those too.
Re:Reasons Not to Use Google (2015) by 0x5002 on Thursday August 29, 2019 @12:02PM (#20830682)
Probably OpenStreetMap/Nominatim or something along those lines.