endtimes.dev

See also the 14KB website article: https://endtimes.dev/why-your-website-should-be-under-14kb-in-size/ Optimizing per-packet really improves things but has gotten very difficult with SSL and now QUIC. I'm not sure Google ever got the front page down to a single packet (would love a reference!) but it definitely paid very close attention to every byte and details of TCP performance.

I use a "textured" font on my website (https://fonts.google.com/specimen/IM+Fell+English, see https://maya.land) and it bothers me all the time that the deformations repeat across letters -- like cracked stone ones where the cracks are the same on every "a"? Because I think mine's simple enough, eventually I'm going to figure out how to get a similar effect with an SVG filter like the "xerox" one on https://endtimes.dev/.

I switched my small personal projects to preact in a (temporarily successful effort) to get one under 14kb after re-reading [0] a year or two back. So far haven't run into any limitations. If you need React, then go ahead and use React, but I'd encourage people to try a simple s/react/preact/g on their websites. (Okay, not quite as simple as that, but even if you don't like vibe coding, this is something an LLM can be trusted with.) [0] https://endtimes.dev/why-your-website-should-be-under-14kb-in-size/

if a website's bundle is <14kb, it will load instantly. https://endtimes.dev/why-your-website-should-be-under-14kb-in-size/

Another reason to golf. It's not quite right, but it's a fun goal to fit an app within the first few TCP roundtrips. https://endtimes.dev/why-your-website-should-be-under-14kb-in-size/

10K seems arbitrary, why not 14K as discussed here: https://endtimes.dev/why-your-website-should-be-under-14kb-in-size/

I’ve written a tutorial on building one of these that uses a checkbox. There’s more ways than a button or a link. Some people have suggested in the comments using details and summary. It works without javascript, represents the states open and closed without requiring any aria attributes and some other usability features people might find interesting. https://endtimes.dev/html-and-css-only-multiple-color-scheme-picker/

The article is a rebuttal to this article (https://endtimes.dev/why-you-should-dither-images/), which in fact used photographic images, so definitely not a straw-man article in this case. Mpqzcp nzxxpyetyr htes pxzetzylwwj-nslcrpo nzxxpyed, dpp tq jzfc nzxxpye xlvpd dpydp ty esp nzyepie zq esp lcetnwp lyo yze ufde esp etewp. Nzxxpyetyr hteszfe vyzhtyr esp nzyepie xlvpd jzf wzzv (opdpcgtyrwj) defato.

> You don't need this code! > By default, all browsers look for a file /favicon.ico in a site's root directory. That must be a drop in the ocean compared to all the requests for non-existent favicons thanks to this behavior... (Which can be prevented via [2], apparently!) > 180x180 is the largest icon size any iOS device requires. Other devices will downscale the image to fit. Using more data (which uses both energy and is often still paid!) and some compute resources to downscale, which wears out the battery of mobile devices, requiring a swap or incentivizing people to upgrade sooner than they otherwise would. Better reason about the externalities thoroughly when throwing out vague statements like "more environmentally friendly websites"! By the same author: "why lowercase letters save data" [1], "Show you how I came to the conclusion that title case on hacker news emits the equivalent yearly carbon as a car driving the width of Sri Lanka." – featuring sub-headlines rendered using some squiggly font effect powered by an SVG filter that probably uses enough collective renderer CPU/GPU cycles to drive the same car to the moon and back. I get and applaud the desire to make the world a better place. But something that people seem to overlook too often with short-sighted initiatives such as this is that one of the most finite resources is human attention. Making somebody feel good about having spent time and effort to implement symbolic/effectively useless measures means…