Claude.
Claude.
Happy to hear you were able to make it stick!
I simply can't get to used to motionsπ
nah π
peak @taylorotwell.bsky.social
I officially surrender.
Really wanted to be as cool and productive as y'all, but I simply can't get used to vim motions.
Sorry, I'm giving up for now π€· have to pick my battles.
Bouncing on and off this project has been a constant reminder of why it needs to exist.
When done with passion and kindness, public accountability is a powerful tool.
kumbaya.dev - Light a Fire. Gather Around. Build Together.
Coming soon. Hopefully π
#buildinpublic #indiehackers
@zed.dev Surely this revolutionary idea gets me a contributor badge? π
πππ
IMHO, Zed is better than Cursor in almost every way.
The only reason I even think about launching Cursor is that its autocomplete is simply on a different planet.
@zed.dev any roadmap items? π
enthusiasm is a magical source of energy πͺ
Integrated the official Laravel + Svelte starter kit into LaraStart (π v1).
If youβve been waiting for a sign to try this combo, this is the βomakaseβ setup I use daily π
github.com/n00ki/laras...
#laravel #svelte #buildinpublic
heard an idea on a podcast
made me think π€
built it. shipped it.
you can just do things
(thanks @aaronfrancis.com for spreading this energy)
let-time-in.dev
we obsess over making UI feel "fresh"
but there's beauty in things that gain character as they age
three divs
three birthdays
three stories of time
software doesn't age. maybe it should π€·
let-time-in.dev
@jasonfried.bsky.social on the @davidsenra.com podcast:
"Software doesn't age. It looks the same over time."
That made me think... what if it did? π
So I built a tiny utility that makes UI age like physical materials.
Give your div a birthday. Let time do the rest.
let-time-in.dev
π SvelteKit Omakase v5 is live!
The bigger revamp is underway, but still:
π Remote Functions
ποΈ Reorganized structure
π― Cleaner, consistent conventions
π€ Lean docs for AI-assisted dev
π§Ή ~1,600 LOC removed (remember when this was the whole flex? π)
somakase.dev
#svelte #sveltekit #buildinpublic
Data layer is coming together πͺ΅
Still early, but the fire is building π₯
kumbaya.dev
#buildinpublic #accountability
this excitement never goes awayπ
2026: the year of highly capable AI agents running bleeding-edge...bash scripts, XML, and markdown? π«’
Everything old is new again. boring tech always wins.
In the end, went with SvelteKit!
Even though it means bringing different solutions for more things and has some rough edges (remote functions still experimental, new forms API missing some essential features) - sometimes the "right" choice is just the one you're already productive withπͺ
SvelteKit has been my default go-to in recent years - it just feels right.
Laravel has a really compelling story - a holistic approach and a complete toolbox for pretty much everything under the sun.
TanStack Start - well, I mainly wanted to understand what all the hype was about π
Iβve spent the last few days building the same foundation three times: SvelteKit, TanStack Start, Laravel + Inertia.
Classic analysis paralysis - Saw it coming from miles away and fell in anyway.
Starting tomorrow, Iβm giving myself permission to be βwrongβ and committed πͺ
I believe that building in public should feel like gathering around a campfire, not standing under a spotlight.
What about you?
lighting the first fire π₯
kumbaya.dev - coming soon...
#buildinpublic #indiehackers #accountability
nothing wrong with Vue at all! Itβs an incredible piece of tech and honestly a great solution for the problems it solves. Svelte just takes a slightly different path to reach similar goals. Different solutions, both great π
I love Vue too! I can ramble all day about philosophy (compilerβdriven, no virtual DOM), performance (speed, bundle size), and ergonomics (syntax, state management).
But honestly, it mostly comes down to taste. Svelte just vibes π
Honestly, whatβs the excuse for not choosing Svelte at this point? π€
It's been a while, but I'm back experimenting with some exciting new features for SailKit π
Just shipped v0.3.4 in the meantime - no flashy features this time, but solid foundation work.
Stay tuned for what's next π
#svelte #sveltekit #email #opensource
sailkit.xyz
modern frontend frameworks might be lacking in some areas, but their DX and tooling story? absolutely unmatched in web development. I believe that ease-of-use is one of the key factors driving widespread adoption π οΈ
i used to love SvelteKit's "+" naming conventions. clean, clever, unmistakably Svelte.
but after exploring other ecosystems lately, coming back feels... off. not bad, just different than what I need now.
funny how you can appreciate something and still outgrow it.
VSCode versions are live π
github.com/n00ki/themes...
my raison d'Γͺtre β₯οΈ
2 years
I hate to admit it, but I'm starting to appreciate React's "everything is JS" nature.
Sure, HTML-first feels more intuitive and way less verbose, but there's something to the "forget templates, it's all just functions returning markup" story after all π