Ken Kunz
@kenthropic.com
Outie: Creating software for humans. Principal Frontend Engineer with cross-functional Product/UX background. Svelte evangelist / co-organizer Svelte Chicago. Husband, dad, climber.
Innie: MDR Frontend Lead @ Lumon 🎈
Innie: MDR Frontend Lead @ Lumon 🎈
3/3 Glad you're enjoying Runed FSM! I didn't work on this version directly, but provided some inspiration with my svelte-fsm library (Svelte 3/4 store-based API). You have @gazit.me to thank for Runed FSM implementation 😄.
November 9, 2025 at 10:01 PM
3/3 Glad you're enjoying Runed FSM! I didn't work on this version directly, but provided some inspiration with my svelte-fsm library (Svelte 3/4 store-based API). You have @gazit.me to thank for Runed FSM implementation 😄.
2/3 If you need the FSM (and shared context) to be available from more than one component, extract it to a svelte.ts module and export the FSM and shared state from there.
For example:
github.com/kenkunz/svel...
For example:
github.com/kenkunz/svel...
github.com
November 9, 2025 at 10:01 PM
2/3 If you need the FSM (and shared context) to be available from more than one component, extract it to a svelte.ts module and export the FSM and shared state from there.
For example:
github.com/kenkunz/svel...
For example:
github.com/kenkunz/svel...
1/3 I've generally found that context doesn't need to be built into the FSM API itself. Your "surrounding context" (enclosing lexical scope) is your context – the FSM has access to whatever is defined there.
November 9, 2025 at 10:01 PM
1/3 I've generally found that context doesn't need to be built into the FSM API itself. Your "surrounding context" (enclosing lexical scope) is your context – the FSM has access to whatever is defined there.
Runed FSM (like its predecessor svelte-fsm) does not support parent/child states. I've considered adding this, but (a) haven't had bandwidth, and (b) have been hesitant without seeing more use case examples (w/in a Svelte app context).
Can you share more about your use case?
Can you share more about your use case?
November 9, 2025 at 8:09 PM
Runed FSM (like its predecessor svelte-fsm) does not support parent/child states. I've considered adding this, but (a) haven't had bandwidth, and (b) have been hesitant without seeing more use case examples (w/in a Svelte app context).
Can you share more about your use case?
Can you share more about your use case?
Wait… you found Svelte 2.x code?!
😜
😜
November 5, 2025 at 6:14 PM
Wait… you found Svelte 2.x code?!
😜
😜
Mad props to @allozaur.bsky.social for leading dev on the new llama.cpp WebUI and championing Svelte/SvelteKit for the project! Also kudos to @hf.co for sponsoring this open source work 💪 #Svelte #SvelteKit #OpenSource #HuggingFace
github.com/ggml-org/lla...
github.com/ggml-org/lla...
SvelteKit-based WebUI by allozaur · Pull Request #14839 · ggml-org/llama.cpp
Overview
This PR introduces a complete rewrite of the llama.cpp web interface, migrating from a React-based implementation to a modern SvelteKit architecture. The new implementation provides signif...
github.com
November 5, 2025 at 5:07 PM
Mad props to @allozaur.bsky.social for leading dev on the new llama.cpp WebUI and championing Svelte/SvelteKit for the project! Also kudos to @hf.co for sponsoring this open source work 💪 #Svelte #SvelteKit #OpenSource #HuggingFace
github.com/ggml-org/lla...
github.com/ggml-org/lla...
Way to sneak this post onto the Svelte feed 😆.
November 5, 2025 at 3:04 PM
Way to sneak this post onto the Svelte feed 😆.
3/ SEO: While invalid markup isn't likely to directly affect SEO, it can be impacted due to #2.
November 5, 2025 at 12:20 AM
3/ SEO: While invalid markup isn't likely to directly affect SEO, it can be impacted due to #2.
2/ Rendering bugs: Invalid markup can cause browsers to restructure the DOM unexpectedly, leading to layout inconsistencies, forced reflows, and layout thrashing.
I've personally had to debug this with anchors nested inside anchors.
I've personally had to debug this with anchors nested inside anchors.
November 5, 2025 at 12:20 AM
2/ Rendering bugs: Invalid markup can cause browsers to restructure the DOM unexpectedly, leading to layout inconsistencies, forced reflows, and layout thrashing.
I've personally had to debug this with anchors nested inside anchors.
I've personally had to debug this with anchors nested inside anchors.
1/ Accessibility: Screen readers and assistive tech rely on proper semantic structure.
November 5, 2025 at 12:20 AM
1/ Accessibility: Screen readers and assistive tech rely on proper semantic structure.
Option 7: "ROT13 Types"
All type annotations must be written in ROT13 (`shapgvba nqq(k: ahzore, l: ahzore): ahzore`).
All type annotations must be written in ROT13 (`shapgvba nqq(k: ahzore, l: ahzore): ahzore`).
November 3, 2025 at 6:46 PM
Option 7: "ROT13 Types"
All type annotations must be written in ROT13 (`shapgvba nqq(k: ahzore, l: ahzore): ahzore`).
All type annotations must be written in ROT13 (`shapgvba nqq(k: ahzore, l: ahzore): ahzore`).
Option 6: "Irascible Types Only"
Type annotations that get progressively more hostile the longer you ignore type errors. ("Again with the `any`? Really?" … "This is why we `never` have nice things." … "Oh how your variable names suck. Let me `enum` the ways.").
Type annotations that get progressively more hostile the longer you ignore type errors. ("Again with the `any`? Really?" … "This is why we `never` have nice things." … "Oh how your variable names suck. Let me `enum` the ways.").
November 3, 2025 at 6:42 PM
Option 6: "Irascible Types Only"
Type annotations that get progressively more hostile the longer you ignore type errors. ("Again with the `any`? Really?" … "This is why we `never` have nice things." … "Oh how your variable names suck. Let me `enum` the ways.").
Type annotations that get progressively more hostile the longer you ignore type errors. ("Again with the `any`? Really?" … "This is why we `never` have nice things." … "Oh how your variable names suck. Let me `enum` the ways.").
A preview of the presentation materials for your consideration and wellness. Please enjoy each image equally. #svelte #severance #praisekier
October 23, 2025 at 3:42 PM
A preview of the presentation materials for your consideration and wellness. Please enjoy each image equally. #svelte #severance #praisekier
Yes – Rich previously addressed this here: bsky.app/profile/rich...
I can take this one! Yes, there are - we haven't fleshed it out yet but the idea is to ship a low-level 'resource' primitive in Svelte that Kit's `query` extends from. We'd also ship a higher-level function (name TBD) that takes a URL and returns a resource that fetches that URL and calls .json()
October 14, 2025 at 3:10 AM
Yes – Rich previously addressed this here: bsky.app/profile/rich...
It's _your_ meetup too, @evbogue.com! @mikerourke.bsky.social and I are merely your humble organizers 😊.
September 30, 2025 at 6:54 PM
It's _your_ meetup too, @evbogue.com! @mikerourke.bsky.social and I are merely your humble organizers 😊.
Thanks for the shoutout! Grateful to my co-organizer @mikerourke.bsky.social, as well as @8thlight.bsky.social for hosting and @storyblok.com for sponsoring. Can't wait to see everyone there! 🙌
September 20, 2025 at 3:53 PM
Thanks for the shoutout! Grateful to my co-organizer @mikerourke.bsky.social, as well as @8thlight.bsky.social for hosting and @storyblok.com for sponsoring. Can't wait to see everyone there! 🙌