Everday features plus concept demo with NextJS app router like parallel routing, route interception, pagination, infinite scrolling with swr and music streaming! Find it here https://t.co/MknHv6Q9NI
AI makes it so easy to polish rough edges and smooth out your product experience. Yet pretty much every piece of software is falling apart.
Why? The devs building them don't care.
Software built by people detached from the users has never felt worse.
Since most of @elonmusk's products use TanStack in some way, I think it's reasonable for me to want a 1:1 trade-in value on the Y I just bought a few months ago so I can upgrade to the YL.
Let's keep Open Source *free! 😉
Really excited about this one: a new, free @convex course just went live on Database School 🎉
We build a full helpdesk app from scratch over 38 videos. It was a blast to make.
Database, auth, realtime, optimistic UI, AI replies, Resend. All of it!
https://t.co/XRdP9L939Y
@trq212 I respectfully request a review of my account suspension.
I have always intended to use the platform responsibly and in compliance. At this time, the suspension is significantly impacting my work because I urgently need access to imp data stored in my account.
Boohoo not cool man
> Register many names similar to Tanstack
> Create a README to make it look like one
> All created just a year ago
> Ransom $10k from Tanner
> Publish malware to steal .env
This is not an accident, this is an intentional malicious behavior
Shame on you @SH20RAJ for making the job of Open Source maintainers harder than it already is
I sincerely hope your employer know what you did and that you shouldn’t be trusted or get blacklisted on your future employment
Open source isn't dying because of AI.
It's dying because we all fucking suck.
Users. Maintainers. The whole ecosystem. All of us.
We fucking suck as users.
We use OSS to do our jobs. To build products. To make money. Our employers depend on it. Our startups run on it.
But the second a maintainer mentions compensation? We lose our fucking minds. "It should be free." "That's not the open source way."
Meanwhile we're extracting value from someone's unpaid labor every single day.
We file issues like we paid for a support contract. We demand timelines. We get snippy when our bug isn't the priority.
We're not customers. We're guests. Start acting like it.
We fucking suck as maintainers.
We wanted the GitHub stars. The conference talks. The Twitter followers. We wanted to be the person who "owns" that thing everyone depends on.
But now people actually depend on it and we're annoyed.
"Talk is cheap, show me the code."
So someone does. They spend hours on a PR. We ignore it for months. Close it with no explanation. Or we screenshot their issue and mock them publicly for not reading our minds about what we actually wanted.
We invited contributions then punished people for contributing.
We don't want to maintain projects. We want to be admired for maintaining them. Not the same thing.
We suck at this together.
Both sides want the benefits without the responsibilities.
As users we want free, maintained, high quality software but won't contribute a damn thing. Not money. Not code. Not even basic respect.
As maintainers we want the status of running critical infrastructure but won't communicate, won't collaborate, won't treat people like humans.
We all know this shit doesn't work. And yet here we are.
Okay Josh, what do you suggest then?
If we use OSS and profit from it, we contribute something. Anything. Money, docs, triage, kindness. We stop expecting infinite free labor.
If we maintain OSS and we're burnt out, we say so. Archive it. Hand it off. Ghosting is worse than walking away.
And if we can't treat each other with basic respect? We don't get to participate. Full stop.
Open source runs on people. On us.
None of us owe each other a god damn thing. But we could choose to stop being assholes and do better anyway.
I get a lot of questions about how we made markdown parsing fast on the @v0 mobile app.
The answer: we do less work on the client.
v0 doesn’t parse markdown strings in React Native. Instead, the server parses MDX and streams a JSON tree to the client.
During message streaming, the server sends JSON patches for each chunk. The client applies the patch to its local cache using jsondiffpatch.
We even modified the jsondiffpatch protocol to send the diff for string fields inside any JSON.
Finally, the client recursively loops over the JSON tree and renders custom components for each MDX element.
Can someone please recommend a Netflix show that's actually addictive, the kind that makes people stay up all night and finish season one in one sitting?
We did it. shadcn/ui just hit 100K stars ⭐
🏆 2× Project of the Year
📦 1M components installed every day
✨ The UI for AI
🌐 Used by millions
Massive thank YOU. Truly.