> Sources: > https://bugzilla.gnome.org/show_bug.cgi?id=685393 > http://ftp.gnome.org/pub/GNOME/core/3.7/3.7.1/NEWS
Browsers enable JS by default -> sites require it -> browser developers think disabling JS will confuse users; I don't understand the last step, not knowing people breaking their browsers by changing settings (more often they don't change settings with bad defaults). (Having two configuration interfaces with different options somehow isn't considered bad for usability.) > My opinion is that web browsers should do the reverse: make JS > disabled by default. Sadly, I don't see any influential browser > creators like Mozilla doing this any time soon, so the JavaScript trap > continues. I agree, although there might be other incompatible solutions that would solve more privacy or security problems. > There's also question that I've been looking for an answer to for a > while: is GNOME still a part of the GNU project, and what's the > relationship between them? It is and this is the relationship between them. I don't see any relation between GNOME and freedom or extensibility policies of projects like GNU Emacs (which makes nearly all options browsable; the development list has many cases completely opposite to GNOME Shell's OpenGL dependency: old systems are supported so users won't upgrade to newer nonfree ones, multithreading isn't used so it works well on single core systems with no nonfree software (although this has many other reasons)) or GCC (which doesn't hide dangerous options).
pgpFYEJI5HQJ4.pgp
Description: PGP signature
