Pinned Tweet
In times of technological acceleration, planning based solely on what’s possible today limits potential. Instead, set a bold vision and iterate relentlessly toward it.
Our vision is to make websites more relevant, timely, and deeply connected to their communities—while remaining memorable and unique. Autonomous Websites are the transformative technology that will make this a reality.
We’re already making strides on this journey, delivering innovations that pave the way. Within the next 4-5 years, we’re committed to fully realizing this vision.
Visitors ≠ Users.
Yes, new technologies have transformed the browser into a full blown runtime, and the line between *website* and *web app* is really blurring.
But they aren't separate technologies so much as separate postures. The crucial distinction is in the visitor's head!
An app is an experience you've (on some level) agreed to learn. A website is an experience you have agreed to *glance* at.
I got so into Suno recently, and initially I was expecting to invest time and mental energy in learning my way around. I use Ableton already, so I know these tools take some learning.
I spent time in their UI, I explored, I tolerated some level of confusion. Up to a point, at least, and the moments of frustration came slowly.
On a website, they would've come in seconds. A visitor isn't trying to get value immediately, they are trying to verify "am I in the right place?".
If the website doesn't answer that in a second, they bounce. Different psychology and behaviour entirely. Which posture you optimise and design for decides which one you've built.
Think of a storefront. The window is arranged to be scanned from the street in a glance. Once you get inside and commit you accept some orientation and effort, but you don't want that from the window.
Expecting a visitor (glancer) to be a user (learner) is one of the most common website design failures.
And as browsers become more capable runtimes, this distinction becomes more critical. You can now build almost anything in the browser, the technical barriers are melting away.
But the psychological ones are as strong as ever. Blur the distinction, and you can lose both. Too complex for visitors to parse, too shallow for users to invest in.
Web developers and designers, what makes websites still relevant?
So let me get this straight.
Tech leaders keep telling people they will lose their jobs for AI
People’s children don’t have proper schools and education
and we blame immigrants for that.
Did I put it right?
People look at strikes in France and see it as chaos - I see it as a sign of human values in this society, that people have a say.
I also see a lot of people mocking Europe for slow reactiveness, and questioning their priorities, like the famous eco-friendly bottle cap.
But could this friction be an advantage?
I see a world where Europe builds AI that actually respects humans, and Mistral seems to be steadily closing the gap to the frontier. I see Europe and France having real say in what the AI future looks like, leading in innovation while staying human.
Perhaps the traits that people mock Europe for will be the same things that make AI more trusted and aligned in the long run. Maybe Europe will benefit from the last mover advantage.
AI watchers out there - plausible or wishful thinking?
Someone just rebuilt most of the Adobe suite in Rust, open source and free. Photo editing, vector, video, RAW, PDF, motion graphics, page layout. All of it!
Does this mean Adobe is "dead", as some say?
Of course not. Adobe users don’t stay because they love the subscription. It's the muscle memory, systems, compatibility, plugins. Code itself is becoming a commodity, perhaps, but community and taste aren't.
Is this enough to win that Adobe community? Is there an edge we’re not seeing yet?
Curious what designers think.
AI gives us all the state of the art, but that's already in the past... Are you using AI to just implement the past, faster?
Sadek Drobi retweeted
Opus5: "Rotate your $$KEY$$ — one of my commands printed it in full into this transcript."
Claude, are you serious, I thought you knew about security ?
I've been seeing a new anxiety on the feed and in conversations. It's something like:
"If I build something good that uses AI, won't the model provider just build it as a feature? Is my product just a temporary trick destined to be absorbed?"
Both of these are culture and habits, and skipping them kills the compounding.
Assume that OpenAI can, if they want, eventually copy what you do or make you a feature.
Remember in Java, your code would "improve" without rewriting it?
As compilers advanced, the same source programs benefitted - purely from better optimisation. You got better code for "free" essentially.
I think something similar is becoming possible with AI...
From these the better model can upgrade the implementation from the same spec, improving and adapting to new requirements without losing the intent.
The role of the engineer shifts from writing code to writing and managing the precise conditions for the code to write itself.







