jason quense

@thdxr This is more or less how we store opencode messages, just json columns and hoist the stuff we really want to index or access at a glance

second question - would you be mad if every table was id | data (json blob)

@amitpr @zachbruggeman @tryramp @opencode @modal @CloudflareDev yeah this is always a challenge. Part of if is unavoidable which is why speed matters a ton. Supervision is less a problem if it's quick. We also limit agent paths that lead to wasted or inconsistent behavior by handling them out of band, like PR creation.

@zachbruggeman @tryramp @opencode @modal @CloudflareDev Curious how much "handholding"/human supervision this agent requires (if at all), including code review and iterating on features. This is one area in which I've found background or cloud agents to fall short: human supervision is harder.

The craft of engineering is rapidly changing. At @tryramp, we built our own background coding agent to accelerate faster. We call it Inspect. It wrote 30% of merged frontend + backend PRs in the past week. It’s powered by @opencode, @modal and @CloudflareDev. It runs fully in the cloud, and starts in seconds, letting every builder work at the speed of thought, no setup required. Today, we’re open sourcing the full blueprint so anybody can build their own Inspect. Just give our spec to your current coding agent, and let it build your new favourite.

One of my favorite parts of building @tryramp is that we aren't afraid to build things ourselves if we think it'll be better. Inspect is better! Check out how we're enabling all of ramp to help build with us.

What happened to @codesandbox it's gone from a super convenient in-browser editor and scratchpad to a bloated mess that almost never works. I have completely stopped recommending or using it.

I'm hiring designers for @tryramp. Who should I talk to? If I hire them, your bonus would be enough to buy 50 @figma Creator Micros. No DMs, no Freelancers, must be US-based → app.liftoff.xyz/kQlk07

@bramus Lesson learned!

@monasticpanic 🫠

So, umm, we inadvertently broke `linear()`, `cubic-bezier()`, and `steps()` in certain cases in Chrome 128 😬 It’s broken in the case where you have whitespace after the opening `(` Broken: `linear( 0, 1)` Not broken: `linear(0, 1)` issues.chromium.org/issues/3616521…

@bramus We were using a complex linear() with new lines

@bramus Ugh we noticed this broke in the dev build a while ago and never filed an issue bc I just assumed someone would notice and it'd not make it into stable 😬

@rickyfm @sebmarkbage more digging uncovered that the component was remounting for an instant. It was unexpected that suspending would trigger the render but ultimately never the effects. It's cool that it can tell when the suspend is done that it's not needed anymore and just bail!

@monasticpanic @sebmarkbage effects run after your component commits, if something suspends, it doesn’t commit, so the effects aren’t run

hey @sebmarkbage hard to get find an answer for this, Will React ever start to mount a component, run a render, then bail without running effects? Suspense is involved...

@kenwheeler @RosserJobs Idk man I did this got a 50k bump and stayed happily for 3 more years at a gig

@RosserJobs if you were happy you wouldve stayed, if they were gonna pay you the same, why werent they

You are making $160k. You accept a new job at $180k. Current employer offers $200k to stay. What do you do?

@andrewingram I've been meaning to test this more, but the answer seems to be "definitely yes", according to anecdata in GitHub issues on Intl libs. Convincing enough that react-intl still does it.

Does anyone know if the overhead of instantiating things like Intl.DateTimeFormat is high enough to justify caching the instances for each combination of locale and options?

@kentcdodds @acemarke @KomangJelte @rossipedia @sebmarkbage @TkDodo Tbf tho, they also released Lazy without preloading, and suspense in general, like 4 years too early. long enough for fun experiments to inadvertantly become "patterns" by default

@kentcdodds @acemarke @KomangJelte @rossipedia @sebmarkbage @TkDodo IIRC it was something like "don't use this for data fetching, if you must use a framework like Relay that knows how to do it correctly"

@_cristianvr_ @TkDodo @mattpocockuk @sophiebits Making this change without adding Lazy.preload was a huge miss. It's already stupid this API doesn't exist we have so much weird code to hack in on

@TkDodo @mattpocockuk @sophiebits Maybe they'll add a .preload to lazy components to compensate

Now I definitely need to blog about the React 19 changes around suspense and sibling pre-rendering. I haven't seen anyone so far apart from the react core team who thinks this is the right tradeoff. v19.0.0 isn't out yet so maybe there's a slim chance to get them to reconsider

@TkDodo IDK this behavior was always a crutch, it never solved the problem of waterfalls unless you pushed every single suspension to a leaf, which is not a feasible or desirable way to structure components. render initiated fetching was always a thing they said was wrong

For no reason: found is a production ready SPA router that handles data fetching out of the box and with a TON of optional knobs to match your use cases 4catalyzer.github.io/found/

@sebmck (I am ofc open to PRs/feedback if you feel so inclined)

@sebmck I'd be interested how `yup` compares, similar API tho i wouldn't have a ton of hope there as this is not a thing i've ever tried to optimize for, beyond basic perf tweaks.

Zod is really nice but it has zero memoization. It loves bound instance functions. z.number().int().positive() allocates 81 functions (4 kilobytes of memory). Is there an alternative with a similar API that is better about initialization performance?

@kenwheeler Always nice when my toil is appreciated

used yup today, nice work @monasticpanic