3 ms·
The backend is someone else's. It's out of scope, because it's effectively a service. The frontend code executes in your browser, on your machine. It's in scop
by TeMPOraL 6y ago
The backend is someone else's. It's out of scope, because it's effectively a service.
The frontend code executes in your browser, on your machine. It's in scope of GNU/FSF interest, because the end-users of that code would benefit from the four freedoms. A lot of people who strongly believe in the value of the Four Freedoms try to minimize the amount of non-free code they run, hence the desire for free frontend replacements.
The way I see it, this concern meshes nicely with a more general desire to be able to substitute your own frontend for the one that's served to you. If you imagine a world where people develop and exchange alternative frontends, the users would benefit from these frontends being "free as in freedom".
Of course we're pretty far from that world - but it's not impossible; the term of art is "adversarial interoperability" and I'm a great fan of it.