『dylan』

@huge_icons http://localhost:3000

Drop your project URL

@jh3yy @fabgaliano @screenstudio How do you like SwiftUI? Can imagine you doing some pretty neat stuff with it, the declarative syntax makes it feel very accessible coming from the web

@fabgaliano this was a jk btw, hence the drumkit 😅 it's all i've seen over the timeline, jus' grab @screenstudio and be done with it i reckon (i did have a look at building one in swift at one point though)

why is everyone building screen recorders? the last fad was speech-to-text apps, what's next?

@shadcn Idk if you were super early to the party but there’s been tabs the entire time I’ve used it 😅

@DylanDuff3 I did temporarily but there was no tabs. Switched back.

Send help.

@Baconbrix @YairDev Expo was a godsend, truly made working with RN an enjoyable experience, really appreciate the work you guys have been doing to reduce the work on our end for things like Liquid Glass & Widgets

@Baconbrix @YairDev I think native will always win out, there are trade-offs that inherently come with React Native as a whole so if cross-platform isn’t a concern, native will always be the lowest friction choice That said, having recently had to work on an android & iOS app…

best decision I've done building mobile apps is to use Swift instead of Expo can't even begin to describe how better the experience is

@laogui It’s because the people who cared about Arc felt abandoned by @browsercompany , the people who would have criticized this stopped caring a long time ago

Zen 这才是像素级抄 Arc，却没人骂，因为它开源且明确定位“Arc 的开源复制版”。 换成其他开源项目这么抄，绝对被喷。 敢承认自己是抄的，就能逃过一劫，好像是这个道理。😂

@SnazzyLabs @da_booyse Any references for what you consider to be “done right” genuinely curious :)

@da_booyse You don’t hate passkeys. You hate how devs implement passkeys. Passkeys are amazing when done right.

And most web devs don’t either. It pisses me off when Passkeys are used either as 2FA and/or in addition to keeping a traditional username/password WHICH DEFEATS THE ENTIRE POINT.

@grimcodes It makes me sad to see all the hate on this because whether it’s to one’s personal taste or not, it was them letting someone on the team have a bit of fun which all software needs more of these days imo.

god forbid we bring taste back 🫩

@ChristianSelig @elSchtaunko I use wolphin on my tv and it is great, Swiftin was pretty promising last time I checked it out and is OSS

@elSchtaunko Yeah Wolphin looks to be pretty beloved

I'm convinced Jellyfin would pass Plex if there just existed a good Apple TV app

@theo Because if I’m writing code my terminal is already open, and as much as people clown TUIs, I genuinely just prefer the simplicity of a single input/output interface. That said I do enjoy the work conductor has been doing and probably do need to give it more exploration

Are you still using the CLI versions of your preferred agent instead of desktop apps like Codex App, Conductor, or T3 Code? Tell me why below. Genuinely curious.

@paulswaney3 Your a weird dude

Young people massively underestimate how their public social media can kill high-paying job offers I have personally seen 5 offer letters pulled in NY over social media content. All were 300k plus total comp roles. Real cases If you are aiming for 85k forever, you are probably fine If you want bigger things, read this

the feedback every interaction designer gets in review: "can it feel more snappy?" or the sibling version, "can it feel more bouncy?" and you nod and go tweak something and bring it back and the pm still says "idk something feels off." this dynamic goes on for two weeks cause the stakeholder doesn't have the language for motion, and you haven't given it to them. here's what's actually happening. a spring has three variables — stiffness, damping, mass — and almost every complaint about "feel" maps cleanly onto one of them. "too slow" is almost always stiffness. "too floaty" or "too bouncy" is damping. "too lethargic" or "too heavy" is mass. when you walk into review with a slider for each and the pm can watch the press animation update from stiffness 180 / damping 16 / mass 1 to stiffness 400 / damping 32 / mass 1 in real time, the conversation stops being about vibes and starts being about the physical property they actually want adjusted. the review closes in ten minutes instead of two more rounds. but stiffness and damping aren't universal. they're a function of what the movement represents. a swipe card retains the momentum and angle it was thrown at, so stiffness 250 / damping 10 reads as physical. the same config on a press-scale or hover-scale feels jarring because a press is mechanical, not fluid — there's no throw, no momentum to preserve. press interactions want stiffness 250 / damping 25. satisfying, no overshoot. mass is the one most people reach for to "make it feel heavier" and then regret, because increasing mass makes things lethargic, not weighty. if you want weight, you want damping. mass only earns its keep on pendulum-like motion where you want a bit of residual wobble after the object comes to rest. edge case: this breaks for destructive actions. you don't want a nice spring there. you want friction. hold-to-confirm, a progress ring that fills over 1.5s, a commit that requires sustained intent — the whole point is that deleting should feel heavy to perform, not pleasant. so conceptual weight isn't only a spring problem. sometimes the right answer is "make the gesture harder," not "tune the spring harder." counter-argument i get a lot: "users don't care about damping, they care about how it feels." correct. which is exactly why you tune stiffness and damping — those are the variables that control how it feels. saying "users don't care about the numbers" to defend not learning the numbers is like saying "users don't care about javascript" to defend not knowing how state updates batch. the user experiences the output. the numbers are how you produce the output consistently, component after component, across a whole system, without re-litigating every animation in every review for the rest of your career. one more thing people get wrong. css linear() is technically a spring, but the values look like linear(0 0%, 0.005927 1%, 0.022466 2%) and the real problem isn't the ugly output — it's that linear() is not fluidly interruptible. if a user grabs the element mid-animation and the target changes, the motion snaps instead of smoothly arcing to the new target. for anything gesture-driven — drags, swipes, magnetic snaps, rubber banding — you want a real physics engine like motion/react so the spring retains velocity through the retarget. css springs are fine for decorative flourishes. they fall over the second a human interrupts the animation. if you can't state a spring as three numbers tied to what the motion represents, you're going to lose every motion review forever.

@landforce I reach for cowork when I need it to batch work that requires heavy research, hardly ever utilize it to write code usually just directories of markdown

If I use Claude Code is there any reason to ever use Cowork? it seems Cowork is just Claude Code without the dev tooling and with UI for the stuff you're doing.. Every time I use Cowork it seems like I should have just been in Code but Idk if I'm missing something or what

@wesbos What’s notepad++

Zed is aluminum Cursor is hexclad VS code is teflon Emacs is cast iron OpenCode is an air fryer

Carbon steel is the Vim of the pan world. Takes forever to get going, the people are insufferable, yet you know you are superior than every other normie who can’t figure it out

// AGENTS.md Never, ever, under any circumstances, ever, not once, no matter what, try to start the fucking dev server, it’s already fucking running.

@marclou why did it take this long to be a feature? ive seen this guy @'ing you for two days straight? it wasnt already an option? 100% vibecoded?

done

@theo Do you have CLI ? / is it in the pipeline, latest Anthropic crap has made me wanna shift

“Now that I moved to T3 Code, I don’t really have battery problems anymore”

@joshmillgate I don’t mean package the entire thing, more like a helper extension to extend functionality

@joshmillgate Could you also just package it as a chrome extension and allow users to bind animations to selectors ? I’d be fine installing a package but this may make it more versatile ?

In order to have custom animations on components for beautiful cinematic effects, it will need to be used in the codebase of an app (esentially npm package) Otherwise simple screenshot uploading is the only option (no animations on components) Which direction to head?