SvelteKit 3 is a wonder. Congrats to the team. So excited for Async Svelte & Remote Functions to cook.
I built a tiny app, it built & deployed in 15 seconds end-to-end, it’s instant, and fx + opus figured it all out effortlessly.
https://t.co/LFoUKMKLSV
Alright. I want you to read this.
Earlier today, I released a new component.
What you see is the finished result.
What you don’t see are the days of planning, research, testing, designing, simplifying, throwing ideas away, and trying again before I felt it was ready.
Within hours, it had been copied and ported to another framework by pointing an agent at my code.
Of course, it’s open source. They were allowed to do it.
And I’ve been around long enough, with multiple successful products, that I don’t care.
But what if this was someone’s first product?
What if they spent months building it, launched on Friday, and by Monday it had been cloned by agents, repackaged, and made free?
What happens when your second product is copied?
Your fifth?
Your tenth?
What happens when every new idea immediately becomes the next prompt?
What happens when your roadmap, your changelog, and your launch announcements become someone else input prompts?
What happens when models become good enough to copy bigger ideas?
What happens when “just execute better” stops being the answer?
What happens when “just build bigger” or “think wider” stops being enough?
What happens when both ideas and execution become cheap?
What happens when the creator pays the full cost of creativity but everyone else pays nothing to reproduce it?
What happens to creativity when AI makes copying effectively free?
What happens to the will to create when AI makes copying effectively free?
Look, copying is not new.
Copying at this speed, cost, and scale is.
People will tell you to think bigger.
But nobody starts "bigger".
Every one of us here started by making something small.
You keep going because, somewhere along the way, the work is rewarded.
Maybe people use it.
Maybe they pay for it.
Maybe they simply recognize the thought, effort, and care that went into it.
Copying once demanded effort.
You had to study the work and understand it to copy it.
That effort created appreciation for the person who made it.
Not anymore.
Creativity begins with small steps.
If we make those first steps feel pointless, we don’t just lose small products.
We lose the people who might have gone on to build the big ones.
We are uniquely positioned here.
We get to use and experience this life-changing technology before almost everyone else.
How we use it will set the default everywhere else.
That default will spread to writing, design, music, research, and every other field where someone still has to take the first creative risk.
We can use AI to build great things.
Or we can use it to strip every new idea for parts.
We decide.
I strong agree that if you are writing code by hand you can and should most certainly see what you can generate to aid you.
if your code is that important, why not create as much automation as possible around it for validation? Seems like a very simple argument.
Also I think its LLMs current best use case. Its what they are the best at right now. "I just got done doing 'mansplain what you did' and I want you to review it and tell me what I have missed, what could be a logic flaw."
Even that alone will surface 1 or 2 things I have done wrong almost with every single change I make.
New skill: /animation-vocabulary
Helps you get better animations from an AI by telling it exactly what you want by using the right words.
"morph", "rubber-banding", "layout animation", and more.
In light of what happened, I'm doubling down on skills like /improve.
A frontier model got pulled. If it happened once, it's gonna happen again. Fable today. 4.9 tomorrow or maybe gpt 6 one day.
So, treat intelligence as borrowed. Drain intelligence when it's available. Build a catalog of plans today. Then implement later with a cheaper, open source, or a model you control.
Build the backlog now.
https://t.co/rqHw0fPv4G
Say goodbye to svelte.config.js - you don't need it anymore!
The newest version of SvelteKit allows you to configure everything via its Vite plugin, and VS Code, svelte-check and SvelteKit itself can all read from it.
On file less cluttering your project root.
To get good animations from an AI you need to get good at telling it what you want:
- "stagger this list of items"
- "make this animation direction-aware"
- "spacial consistency", "crossfade", "layout animation",
I made a motion vocabulary for this:
https://t.co/ExAxpr31no
Just published a super-simple media folders plugin on https://t.co/anDrWAEkxV https://t.co/6aTm9GOxic to be honest, I was amazed, how fast the plugin was reviewed and approved. Good job!