aboutsummaryrefslogtreecommitdiff
path: root/programming/a_plan_against_the_current_web.md
diff options
context:
space:
mode:
authoralex <alex@pdp7.net>2025-05-03 14:30:18 +0200
committeralexpdp7 <alex@corcoles.net>2025-05-03 14:35:52 +0200
commit6c546aa9243a1d09840a36d0b462dae19bcf44a7 (patch)
tree57974d78d9c9051280521b0d5338960115a4e8a8 /programming/a_plan_against_the_current_web.md
parente412dbb8a63507a0ff3ff5eb1f3fdd354138194a (diff)
Evolve the plan against the current web and the content web manifesto
* Simplify the content web manifesto to "terminal non-JS browsers" * Move stuff from the plan against the current web into the content web manifesto * Centralize links in other content to both documents * Move from IDEAS.org to programming/the-content-web-manifesto/NOTES.org
Diffstat (limited to 'programming/a_plan_against_the_current_web.md')
-rw-r--r--programming/a_plan_against_the_current_web.md21
1 files changed, 1 insertions, 20 deletions
diff --git a/programming/a_plan_against_the_current_web.md b/programming/a_plan_against_the_current_web.md
index 4e9a670d..55e58da4 100644
--- a/programming/a_plan_against_the_current_web.md
+++ b/programming/a_plan_against_the_current_web.md
@@ -6,26 +6,7 @@ This complexity is derived from using the web for delivering applications, where
## Part I: Make content websites simple again
-Nowadays you cannot use "simple" browsers like Lynx, Dillo, etc. conveniently to browse content.
-You will run into pages which are not usable without a fast and sophisticated Javascript engine, or without a fully-featured web renderer.
-The most common example are websites that are just a blank page when viewed with a browser with Javascript disabled.
-
-If users could browse content using simple browsers, then the power of Chrome would decrease.
-Also, content sites which are usable with simple browsers in my opinion have a nicer user experience: faster, lighter, more accessible, and more flexible.
-
-This is in part impossible nowadays due to the popularity of Javascript-first websites developed as SPAs, and the fall from popularity of progressive enhancement.
-But you can do your part: ensure that you test your content website using a low-powered browser.
-Not Chrome, not Firefox, not Safari; use Dillo, Lynx, etc. to verify that your website works.
-
-This will not move the needle, but your normal users (those who use Chrome) will benefit too.
-
-### Diversion: Gemini
-
-Yes, I cannot avoid talking about Gemini.
-Gemini is this idea driven to the extreme.
-It's an alternative to web browsers and HTML which is so simple that you can implement a Gemini browser in a weekend.
-Of course, it is so extreme that it cannot be a mainstream success.
-But it is an insightful study about these ideas that can be analyzed to learn.
+See [the content web manifesto](the-content-web-manifesto).
## Part II: Application distribution sucks