The author says that every software domain that gets touched by the web browser gets swallowed by it.
Perhaps it is early days and all compilers will be web based soon (makes me think of that dystopian horror story "The Right to Read"), but browsers have touched every aspect of the compilation process and besides JS I would say the majority of compilers are not online.
For a compiler-related example, Rust's cargo build tool (the interface that most developers use to the rustc compiler) interoperates with other tools by outputting JSON: https://doc.rust-lang.org/cargo/reference/external-tools.htm...
Another example that's more of a standard is the Language Server Protocol, which is JSON over HTTP even though it doesn't (always) touch a browser: https://en.wikipedia.org/wiki/Language_Server_Protocol
In these very comment threads, we've seen proposals for stuff like
df -h --json
making it abundantly clear that JSON is a data format, not a technology inevitably associated with browsers or even just HTTP.
>video editors. DAWs. Console-y video games. Compilers. Linkers. Operating systems. The overwhelming majority of mobile apps. Dental imaging systems. Robot assisted surgery systems. CNC controllers. Scientific data analysis. GPT-N.
Because many of those already offer web interfaces, or can be done online
>get your head out of the sand and grasp the scope of what software actually is and does.