I made a tool to help us visualize how many generations of life on Earth it took to get to you. From the LUCA (Last Universal Common Ancestor) bubble to modern Human (some scrolling required!)
80% there. The next step would be to generate many more versions of that picture. Even if you go back into the 80s, the hairstyle should change. If you go back into the 1800s, you probably don’t have the bright colors in the shirt. If you go back earlier, it might not be cotton but hemp. Etc. I think with generative AI it should be possible to slowly morph the one person from today in today’s clothing all the way back to Lucy, one picture at a time. Then, the effort of scrolling would actually be worth it!
Demonstration of Svelte 5 Custom Elements to build reusable, interactive components (Custom Elements) that are host framework agnostic (once built), integrate seamlessly with any web application and do not require a module system (as demonstrated in this server-rendered ASP.NET MVC page). By compiling Svelte components as browser-native Custom Elements (part of the Web Components standard), we can achieve clean encapsulation of logic and state while maintaining standards compliance and framework independence.
I've been using Svelte's custom elements (web components) to make components that slot into pages on an existing .net / alpine.js site. It's been a great dev experience and results in really portable components. Each component is it's own bundle (achieved via separate vite configs - you can also organise to bundle groups of components work together). Each of the tools in the tools section is a svelte custom element https://www.appsoftware.com/tools/utilities/calculators
Agreed ownership of your notes is imperative. You do need some structure though. Try Logseq. I adopted Obsidian after Roam, but missed the low friction structure that Roam offered. But Roam was not secure and was proprietary. Logseq is the best of both worlds, is plain text based with minimal structure (markdown-ish) and is Git friendly. It's a work in progress, and needs a few files adding to .gitignore to minimise merge conflicts (pages-metadata.edn for one).
I/O Content is an API centric Content Management System (CMS) designed for use with any platform or device type. I/O Content makes managing and retrieving content and media simple, featuring custom content types, API queryable content fields, CDN and on the fly image manipulation.
