Pinned Tweet
So my friends, time for me to go then! We had some great time here on Twitter, I learnt a lot from y'all 🥰
I will prob shift focus to:
- projects
- higher-level engineering
- management
Please follow me onto LinkedIn: linkedin.com/in/vklepov
OK, the engagement on X has been just sad for the last year or so. Let's do it this way:
If you're still here, please like / repost / comment this. If we get 100 interactions, I keep sharing some front / web / manager stuff on X, otherwise we go to LinkedIn or someplace.
🧹 Time for a major cleanup in awesome-tiny-js! A custom size badge generator gives more realistic estimates:
- No excessive runtime injected for cjs-only libs
- sane transpile target (es2020, 95%)
Also, no downtime or caching issues!
github.com/thoughtspile/awes…
Added 5 great validation libraries to github.com/thoughtspile/awes…
- v8n
- superstruct by @ianstormtaylor
- banditypes by me
- valibot by @FabianHiller
- deep-waters
Know what I hate about modern webdev?
Every library and feature has talk talk about how awesome it is, not so much about how it works. Guess react hooks started this trend.
I call it devrel-driven development.
I sometimes wonder if our org has the largest svelte-kit codebase in the world. It's around 500kloc svelte + 600kloc ts + 300kloc graphql across 6 projects. Who can challenge this?
🤠 built stetson, a state manager for svelte.
- simple store with actions
- mutable state by default (immer-style)
- auto-batching for fewer updates
github.com/thoughtspile/stet…
HTML & CSS are not the most straightforward way to paint pixels. Why is web UI so popular?
1. Cross-platform out of the box
2. Updates are near-instantly delivered to users
3. No installation = better conversion
4. JS = easiest language to get started
I'm on a fence here. Want to publish a little lib for dealing with state in svelte, should I call it stetson or svenson? Stetson sounds like STATEson, and it's a nice hat. Svenson has half SVElte in it and we can say it's svelte's lost swedish brother.
43%Stetson
43%Svenson
14%*Svensson
7 votes • Final resultsNow, svelte 5. I had 3 major issues with svelte:
1. Awkward props syntax, hard to type
2. Special treatment for listener props
3. Different reactivity models in svelte and js files
All fixed in svelte 5!
Awesome 🥰
React team, not sure what they're doing any more. If they're solving someone's problems, they're not mine (meta's? Vercel's?)
First going for massive client-side updates with interruptible renders etc, now they're a server-first framework, all very incoherent.
Sad.
In a desperate attempt to please google i move my blog back to thoughtspile.github.io
I then proceed to meddle with api gateway and such to get redirects
So I was checking out some design course and they have this lovely section where they ask designers what they enjoy about their job
And a jira designer goes like "my work brings joy to people every day"
Now are you so sure about that one eh
Let's all admit that node has failed to turn JS into a top-tier backend language.
SSR / backend-for-frontend, yes go for it
Misc dev plumbing, ok very handy
LETS HIRE NODE DEVS TO BUILD OUR ENTIRE BACKEND, well maybe don't
Added 3 cool UI frameworks under 3 kB (2 are even ~1 kB) to awesome-tiny-js:
- vanjs ( by @taoxin
- superfine (stripped-down hyperapp)
- arrowjs by @jpschroeder
Great stuff!
github.com/thoughtspile/awes…


