Because if you kill every single Freemason on the face of the earth without getting everyone on Linux or BSD, and the rest of the FOSS stuff first, nothing will change to be honest.
All you'll get is going from a proprietary 666 mark of the beast soystem to a free software 666 mark of the beast soystem.
And this is exactly what always bothered me back when I was still at the PINE64 forums.
People would buy a PinePhone to get as far away from Goolag and Fakebook as possible, and as soon as they unboxed the phone and configured it, they reach out to the forums and ask how to install WhatsApp, GayMail, JewTube, and Goolag Drive on it.
Just why the fuck did you get a PinePhone then?
I mean more like how several software projects, even ones not made by google just copy over stuff from google monorepos (aka bundling of dependencies to screw with distros), here is some examples:
- WebKit (and probably also firefox) uses ANGLE for WebGL, has no releases, can't be easily packaged as a system library, often a source of breakages
- NodeJS, wasm-c-api, wabt, … uses chromium *internal* JS engine (V8), which can't be easily packaged as a system library
- Firedfox uses "LibWebRTC", which is yet another thing internal to chromium, which also of course comes with a copy of Google's own fork of OpenSSL (BoringSSL) and probably other "fun" things like this.
With the only exception of MyMonero, I have literally nothing on my ThinkPads that uses Electron.
And on my desktop I have Bisq, but that's because it's literally the only way to get fiat into crypto (I don't care about crypto to fiat at all) without the KYC bullshit.
You can use different CLI, TUI, or GUI apps to minimize your dependence on a browser where possible, and perhaps use something like Netsurf or Lynx for the remaining part as long as it doesn't depend on any of the soydevvery.
@ryo @lanodan Speaking of NetSurf, I tried it with my personal website. It can't read my navbar which is the only JS part I have on there.
Yeah I know, I should probably find a better way to handle the navbar but this is the only way I know how to do it without resorting to a static-site generator (or using an iframe). But I don't think there is any reason why NetSurf still can't handle even the most basic JS. (The navbar script is just a few document.writeln() calls)
@lanodan @ryo I didn't realize that JS was disabled by default. Now it works.
>And there is several ways to include/concatenate files, none of those involve frameworks (aka static-site-generator).
You mean like writing shell scripts to concat the files using commands like cat? That's no different from a static-site generator to me, even if it's less bloated.
And sure you could argue it ends up being a SSG but with much less problems.
You'll probably want to have a basic one anyway to have RSS/Atom feeds.