/explore

Click through on any links that interest you or select the planets on the right to continue exploring the Outer Web.
You are here

 www.eisfunke.com
SVG: The Good, the Bad and the Ugly | Eisfunke
| | freerangestats.info
Using svglite with web fonts
5.2 parsecs away

Travel
| | svglite is a great way for producing good graphics for the web but there's a small hack needed if you want to use web fonts with it.
| | hypertexthero.com
HyperTextHero: Copy and paste SVG code into Illustator for editable vector image
2.5 parsecs away

Travel
| | HyperTextHero's no hero but plays one on the web, improvising spontaneous sonic landscapes to make music, the language of the soul.
| | www1.chapman.edu
ASCIIsvg: Homepage
1.5 parsecs away

Travel
| | [AI summary] ASCIIsvg.js is a JavaScript library that simplifies creating mathematical diagrams on webpages using standard coordinates, offering an accessible alternative to SVG for educational use.
| | nguyenhuythanh.com
The HARM Stack (HTMX, Axum/AlpineJS, Rust, Maud) Considered Unharmful | Thanh's Islet
26.8 parsecs away

Travel
| Overview Generally, there are two ways of web rendering: the first is SSR, stands for Server-Side Rendering; the second is CSR, stands for Client-Side Rendering. Both come with different trade-offs. Someone has compared that to a cycle, where we first started with SSR, then moved to CSR/SPA as the client-side application state became complex. Because CSR has its problems, we (re)discovered SSR 1 with HTMX, or even NextJS SSR. There were many writing about issues of CSR and SPA 2 3, but I would summarize them essentially as a state synchronization problem between the client and the server that results in complexity 4.