xtodo read

• read https://www.w3.org/Graphics/SVG/WG/wiki/SVG_in_HTML

• [Concurrency is not Parallelism. Rob Pike at Waza 2012 [video]. At https://blog.heroku.com/concurrency_is_not_parallelism ]
• [Concurrency is not parallelism 2013-01-16 By Andrew Gerrand. At https://go.dev/blog/waza-talk ]

to read.

[The Hijacking of Perl.com 2021-02-28 By Brian D Foy. At https://www.perl.com/article/the-hijacking-of-perl-com/ ]

• https://winaero.com/clear-file-explorer-history-windows-10/

• carrot sticks — Today at 2:29 PM
• @Xah Lee i didnt read all the conversation but i think ive got some stuff youd be interested in. basically its using javascript in a way to create dynamically created webpages, from fetches, from api requests, etc, etc, and caching the end javascript result. then the visitor sees the cached page as just pure html without any JS, while JS was responsible for rendering the whole thing.
• so you can have a website with a page for every single possible API request, say a movie API. a page for every single move and actor, built on demand. the user wouldnt be able to tell that it all came from a couple API requests that you got the data from. only the first visitor who requested the specific movie that wasnt generated yet, would feel a little lag. but once it has been made its cached and very fast. the cached data can be periodically re-populated with updated data based on whatever time you want to specify.

• https://vercel.com/docs/concepts/incremental-static-regeneration
• https://vercel.com/docs/infrastructure/data-cache
• https://vercel.com/docs/concepts/functions/edge-middleware

theres a lot of frameworks for doing this kind of thing, some more complicated than others. i'd say https://svelte.dev/ is one of the simpler ones