We've been wanting to make a "browser" that doesn't render HTML/JS/CSS from the server and instead converts the content to a non-executable format (like markdown but probably not actually markdown) that it then displays in a consistent way.
This is the nuclear option for the constant distractions that are common now.
We're not doing that because we're pretty sure it would be a full-time job we wouldn't get paid for, and we'd have to abandon all the existing projects we maintain.
@mavica_again Sort of. You still have to load the page normally before you can use reader mode. It doesn't have the features and compatibility I'd like. Ideally I'd want it to replace my normal web browser entirely. Which is why it'd be a full-time job just building heuristics and site-specific implementations, and fixing/rebuilding them when they break.