Heceta Head Light, Florence, Oregon (© Tom Schwabel/Tandem Stills + Motion)

WordPress rants are a joy to read, but where’s the simpler, safer replacement? Never forget that software is highly corporatized and mostly crafted for corporations, not humans. WordPress sits among the few that mere mortals can work with and understand. The complete revival of static sites might save us, maybe.

Take the innocent PHP web server cli.

php -S 127.0.0.1:8080

Best not to use PHP’s web server cli (even for PHP) because routes with a dot (.) are assumed to be static files. Use a real web server or superior cli web servers with minor gotchas.

python -m http.server --bind 127.0.0.1 8080
busybox httpd -f -p 127.0.0.1:8080
ruby -run -e httpd . -p 8080

nikitonsky: Don’t hide what’s useful

Atlantic puffin pair billing, Shetland Islands, Scotland (© Vince Burton/Minden Pictures)

This document specifies version 3 of the RFC Editor Model. The model defines two high-level tasks related to the RFC Series. First, policy

This document describes the individuals and organizations involved in the IETF standards process, as described in BCP 9. It includes brief

Fannette Island surrounded by Emerald Bay, Lake Tahoe, California (© Rachid Dahnoun/Tandem Stills + Motion)

I might try out the Fresh framework from deno to see if the hype is true hype.

Reading about the Fresh framework lead me to an article about islands architecture and progressive hydration. “Island based client hydration” looks like a type of progressive enhancement.

Wonder how an adjustment to that theory pans out? Might be enough of a golden hammer for most use cases but imo, scaling/speed issues are more fundamental/situational. You could swap between or hybridize client/server all you want and still mess up.