Hot of the press, I wrote a blog post on replicating https://t.co/Nc9w86t14h using Cloudflare Workers and KV Storage. #cloudflareworkers#performance#frontend
https://t.co/WzevFu754I
RT for more reach and this is my first post🙈
I am surprised to see the preact 10 results in https://t.co/L9G7Nu9953 ... I wasn't expecting it to beat every metric in that benchmark, but at the same time didn't expect these numbers. @preactjs folks thoughts on this?
🚨🗣 Egypt's Coach Hossam Hassan couldn't control himself after full-time:
"I will say what's on my mind regardless of the consequence, this was clearly a rigged match and the whole world saw it"
"And I want to say one more thing, if they want them [Argentina] to win so bad, why call everyone to come and participate?"
I think @cursor_ai frontend sourcemaps were public for short period, did anyone manage to extract source code? It had some interesting code.
Lazy me didn't do it. I saw stylex, protobuf dot generation, code to sync ui spinners animation timeline etc..,
Fork your dependencies, trim them to only your use case, never update unless it breaks for your users. I’ve been vocal about this for 10+ years. I’ve always said that updating is way riskier than latent bugs (which can be tracked and CVEs monitored).
If you are updating a dependency, it’s on you to analyze every single commit in the full transitive set of dependencies. If you dont see anything compelling, dont update!
I remember at HashiCorp once in awhile an engineer would try to update a dep or replace a DIY lib with an external one and id always ask “show me the commit we need.” Dont update for the sake of it.
Feeling pretty swell about this mentality with all the supply chain attacks happening.
This is literally insane
guy had 5 BTC locked in a wallet for 9 years
dumped his old college computer into Claude as a hail mary
Claude found the wallet file, debugged btcrecover's password logic, decrypted the keys, converted to WIF, recovered the funds
We are so unbelievably early
@ryanflorence I guess Stripe's sail design system does something similar ... I think they have `overrides` prop which allows overriding themes, events, behaviours, etc
USERS care if code is messy.
They care if the app is buggy. Or slow. Or if the UX is frustrating. Or if important features are missing or broken.
These are downstream effects of messy, unmaintainable code.
when software had a soul
there was a moment around 2005 when using a Mac felt like touching something alive.
the dock bounced. the genie effect swooped. exposé scattered your windows like cards on a table. none of it was strictly necessary. all of it felt like someone cared – not about metrics, but about the feeling of using a machine.
software back then had texture. it had a philosophy. you could feel the person behind it. someone made a decision to make that icon beautiful, to animate that transition just so, to write that error message with a little warmth. apps had personalities. some were weird. some were over-designed in ways that would make a modern PM flinch. but they were alive.
the web was the same. personal sites were genuinely personal. blogs felt like letters. forums had regulars. you knew who made what. the internet had neighborhoods, and each one felt different.
nothing was optimized for scale. things were made by people who loved what they were making.
somewhere along the way, we traded all of that for growth.
A/B tests flattened the edges. design systems standardized the personality out. everything got faster, smoother, more consistent – and somehow less interesting. the quirks were removed because they didn't test well. the warmth got cut because it wasn't measurable. we optimized our way into a world of things that work perfectly and feel like nothing.
now every app looks the same. every interface follows the same patterns. every product speaks in the same calm, frictionless voice, siloed in their own little islands. the humanity got rounded off.
and then came AI agents. and the speed got inhuman.
now you can generate an entire product in an afternoon. ship a feature before lunch. spin up ten variations before anyone's had their coffee. the gap from idea to code is basically zero.
which sounds incredible. and it is. but there's a catch.
when making things are too easy, the slop comes for free too. mediocre things don't look obviously bad – they look fine. they work. they ship. they pass review. and now there are infinite of them. the internet is filling up with software that functions but means nothing. interfaces that are correct but feel dead. products made by agents, reviewed by no one, shipped into the void.
this is the thing that keeps me up at night. not that AI will replace people who care. but that it will drown them out.
here's what I still believe: the best things are made by people who couldn't help themselves. someone who lost sleep over an icon. who rewrote the same line of copy twelve times. who added an animation nobody asked for because it made the thing feel right. that obsession – that's not inefficiency. that's the whole point.
AI doesn't make that irrelevant. it actually makes it rarer and more valuable. taste is not a markdown skill. caring is not a parameter. the weird, specific, "soul" thing you put into something – that can't be programmed into existence.
the path forward isn't to make more slop faster. it's to finally give people with real vision the tools to make the thing they always imagined but couldn't build alone. the designer who had the idea but couldn't code. the kid who saw something nobody else saw. the person who cared too much about something most people wouldn't notice.
if we get this right, we don't get a faster factory. we get a renaissance. more strange, personal, opinionated software made by teams of people who care and mean it.
that's still possible. but only if the people who care get the space and tools to actually express themselves – and don't just hand the wheel to the agent and walk away.
Dear recruiters,
If you are looking for someone with :
Java, Python, PHP;
React, Angular, Next.js;
PostgreSQL, Redis, MongoDB;
AWS (S3, EC2, ECS, EKS);
Unix system administration;
Git & CI with TDD;
Docker & Kubernetes
you’re not hiring a Full Stack Developer.
You’re hiring an entire IT department.
If our business would be the first to be competed away by vibe coded apps, why are we seeing such rapid customer growth (exceeding 50%) right now? And why don't we see vibe coded email or spreadsheet or accounting app or messaging apps yet?
My own personal R&D project is to enable huge gains in programmer productivity by _combining_ compiler technology with AI. Our goal is to enable a quantum leap in programmer productivity while being able to provide security, privacy and compliance guarantees. Without those guarantees, vibe coding just piles up tech debt faster and faster until the whole thing collapses.
Of course, for people like Garry Tan, tech debt is to be pawned off on unsuspecting acquirers.
Let me make a bet with Garry Tan: we will outshine and outlast his vibe coding companies!
Hey @derrickreimer , I have been poking around Savvycal on how you use Elixir/Inertiajs and noticed you have prefix for ids along ulids. Wondering if you store prefix also in the db or is it handled by app (Ecto to output with prefix)?
200 Matches
2354 Runs
152 wickets
94 catches
When history speaks of courage in Yellove,
it will echo your name. 💛⚔️
Thank You, Ravindra Jadeja! 🫡
#WhistlePodu#ThalapathyForever
Animating layout isn't always bad. Global CSS variables are a performance killer. Hardware accelerated blurs can crash sites.
Surprised? We go into all this and more, in the first Web Animation Performance Tier List: https://t.co/SqBbeA5rDc
I don't know how Remix 3 will work out for large scale apps only time will tell. But, it is a great fit for embeddable/widget apps!!! #remixjs
Aside from that, the best part is I can test my logic without renderer 😘