Visualize a life compressed into blocks of one week and grouped be decade. The simple data file is written in YAML. This could be useful to help write one’s autobiography.
Most items appear in the timeline at the time they were created.
If an item attribute can be updated, such as by completing a to-do, a small update line appears at that time in the timeline.
If an item is scheduled for a future date or time, it appears there instead, and a simple update line appears at the time it was created and / or scheduled.
I see updates appear in my timeline when she schedules something. This is a very helpful transaction or record; I now know she set up an appointment for something I’m going to with her, or that she set up a meeting in the future, without any kind of extra “notification” feature, and without having to check future dates regularly for updates.
The more you hit “review later”, the longer it takes for the item to return, allowing items you’re less interested in to “float away” from you without requiring more destructive or detailed actions.
you can’t edit an existing note. Instead, you build on past notes using replies: you can reply to any past note with a new one that goes into your timeline now, forming a thread.
Much easier to compile buckets for ideas when you don’t need to label them—this is why people can write so much on micro-blogging platforms.
Instead of striving to be the fastest or smallest or whateverest, we explicitly aim to be the framework with the best vibes.
HTML, The Mother Language
There’s a subtle line between something feeling magical, and something feeling like magic. We want Svelte to feel magical — we want you to feel like a wizard when you’re writing Svelte code. Historically I think Svelte went too far into magic territory, where it’s not 100% clear why things work a certain way, and that’s something that we’re rectifying with Svelte 5.
So when we design things we need to think about the people who haven’t read the docs in a while, if at all, and don’t care about things like fine-grained rendering or configuring their build tool. This means that things need to be intuitive, that we shouldn’t need to worry about manual optimisations like memoisation, that we should have as few APIs as possible, and that things need to be discoverable — for example you should be able to hover over a rune and get a link to comprehensive documentation.
[Musicians can play until they’re 98 years old and beyond, but nobody wants a YouTuber doing that.]
[Not making an industry money puts you in a somewhat adversarial relationship.]
[The YouTuber career inevitably ends in burnout.]
[YouTubers have no elders, only peers, and this is isolating. Musicians have those who have been doing it longer than them, and a community in the real world to engage with.]