<JotaiProvider>
Quote this with the parent provider of: <QueryClientProvider/>
1
Austin K retweeted
Guy builds something he likes and shares it with the community: Normal people: "Oh this is cool I think I'll try it" Linux community: Ego hurt, complains it's not Arch enough, whines about download size and bloat
Governor Cox: Let's bad policies to encourage people to move to Utah even though we don't have the infrastructure to support it. Also Governor Cox: Oops we don't have the infrastructure to support this many people. Time for some really bad top down housing policies!
This will usher in Utah's full transformation to California. Centralized control over local zoning means communist tower blocks in your backyard. Please contact your Utah state legislators and say HELL NO!
DHH being based as usual
Replying to @dhh
You can call Omarchy a distro, a remix, or a dotfiles dump for all I care. Whatever your fragile nerd ego needs if you must demean newcomers who didn't honor your silly rites and rituals. I'm just going to keep pushing Linux to a new audience by shipping a great system.
1
"Cracked" developers are really just people with a high coding IQ. Cracked Devs > Senior Conventional Devs Finding cracked developers is hard because only a cracked developer can identify another cracked developer.
1
2
Me when someone tells me Typescript is worse than JavaScript because types "slow down development"
1
Oops I accidentally created Next.js
2
Genuinely a great stack though. 10/10 would recommend
1
Oops I accidentally created Next.js
2
1
3
Spent a couple of hours today getting typescript to play nice with hmr without losing type information in a monorepo. Typescript is my passion
1
3
Friends don't let friends use python for their backend
hate to say it.... but i regret building this backend in python. shoulda gone ts all the way.
1
1
3
Not true for me lol
2
Mind blown 🤯
📢Introducing ArkRegex📢 a drop in replacement for new RegExp() with types ⬇️
3
I want whatever you're smoking if you think that Skia gets even close to RN in native performance and feel. Skia is genuinely the worst looking, worst performing rendering engine that I've ever had the displeasure of using
thats why #Flutter is better than #ReactNative 1) Flutter renders its own UI with Skia -> same look & feel on iOS & Android 2) RN still depends on native views & JS native sync 3) Flutter’s toolchain = one stack (Dart + DevTools) RN = Metro + Xcode + Gradle + Pods + config
2
Some of my favorite directives: "use client" "use server" "use workflow" "use react" "use ligma" "use cache" "use cache:remote" "use tanstack" "use 67" "use types" "use context" "use props" "use jsx" "use eslint" "use prettier" "use ai" "use timezones:local" "use php" "use rsc"
3
4
Austin K retweeted
You're a JavaScript dev. You just pushed a new feature to production. An hour later, the Slack messages start. TypeError: Cannot read properties of undefined (reading 'name') Your stomach drops. You passed the wrong prop. Or an API response changed slightly. Or you misspelled 'user.firstName' as 'user.fName'. And your entire app crashed for 10,000 users. This is the exact moment 90% of JS devs just accept that "this is fine." For months, I avoided TypeScript. I thought it was for enterprise nerds who missed Java. I loved the "freedom" and speed of JS. I thought, "I'm a good dev, I can just be careful." I was wrong. I was just learning about TypeScript, and the "aha!" moment hit me hard. I was expecting a chore. What I got was a superpower. Here was my journey from skeptic to believer. Level 1: The Editor Gets a Brain I used to 'console.log(props)' just to remember what was in it. - My new workflow: I define an 'interface User { ... }'. Now, in my component, I type 'props.user.' and VS Code instantly shows me a list of 'firstName', 'lastName', and 'email'. It's not just autocomplete. It's my editor becoming a co-pilot that knows my entire codebase. Level 2: The End of "Oops" (The "Contract") I used to write 'function greet(user) { ... }' and then accidentally pass 'greet("Harsh")'. It breaks at runtime, when the user clicks the button. - My new workflow: I write 'function greet(user: User) { ... }'. I try to pass it a string. A fat red squiggly line appears. I just fixed a production bug before I even saved the file. This isn't boilerplate. This is a contract that protects me from myself. Level 3: The "Wait, what?" Features - Teamwork: The backend team changes an API response. They don't just "tell me on Slack." They update the shared 'types' file. The second I pull from git, my editor tells me exactly what broke. - New Devs: A new dev joins. I don't spend 3 days explaining our data. I just point them to the 'types' folder. They're productive on day one. Level 4: The "God-Mode Refactor" (This is what sold me) This is the real magic. - My Problem: I need to rename 'user.email' to 'user.emailAddress' across a 50,000-line codebase. - My old workflow: "Find & Replace." Close my eyes. Pray. - My new workflow: 1. I go to my one 'User' interface. 2. I rename 'email' to 'emailAddress'. 3. My entire codebase instantly lights up with red squiggles. It's not a list of errors. It’s a perfect, automated to-do list of every single file I need to fix. I can refactor a massive app with 100% confidence. I thought TypeScript was a cage. It's not. It's a suit of armor. It lets you move faster and safer because you're no longer afraid of breaking things.
Austin K retweeted
They’re calling it “Java Developer”
91
140
27
3,427
One of these has legible text and the other is an accessibility nightmare
iOS 26 (Liquid Glass) vs Android 16 (Material 3 Expressive) Which one looks better here?
Maybe manual reactivity isn't so bad...
With all this Remix v3 hype I think I'm doubling down on Ripple. I don't really understand what Remix v3 does that gets everyone so excited
4
3