kcrwfrd_

Tangential but does anyone an have opinion on Base UI vs React Aria?

Trying to decide between the two atm.

It’s not math but I’m using AI to help study and learn DSA. I’m finding it helpful.

But yeah you need to make attempts to apply what you’re learning and answer questions on your own. You can’t simply watch problems being solved (whether by an AI or a person) and retain it.

Honestly I get awful results using this skill. The output is way better when I simply ask it to review the changes on my branch compared to origin/main

Yes

I catch so much shit when I read the code. I’ll take this into consideration when I’m no longer catching poorly made slop all the time.

We are doing this on my team (I am the frontend engineer) and honestly I really miss the old way of doing things.

Written specifications are being reduced in favor of these working prototypes, and now there’s this extra cognitive burden of reading the code and trying to determine what were the intended changes, and what’s the slop that needs to be tossed aside.

We also have to figure out, should we take over this generated PR and make any needed changes? Or do we start over from scratch? There’s often a sense of friction either way.

There have been times where a bunch of unintended changes were generated and I took time to port them over on my reimplementation, and then later on it’s “oops! Sorry! We didn’t mean to change that.”

I get it’s empowering but it does take away from some of the joy I used to find in my work and replaced it with some headaches.

It’s really common that you can arrive on a view from different places.

For example on instagram you might click through to a post from the explore page or from someone sending it to you via DM. In either case pressing the back button rendered in the app, or swiping back, will take you back to where you came from. It feels natural and seamless. Although I guess there are other ways to skin that cat than history.back()

But I agree with you when there’s a clear hierarchy. Like on a job ad a “back” button should just be a normal link to the index of job openings.

Yes you could, or even just a vanilla DOM event handler on a button click.

The problem is that you cannot introspect the browser’s history with the history API. So you have to hack your way around that if you want the “go back in history if possible, otherwise navigate to fallback url” behavior. Which I guess is easier if you’re in a react SPA. Or if you’re fully a MPA and can just check document.referrer

There’s a brand new Navigation API that does let you introspect history entries from the same origin, which perfectly addresses the issue.

I wrote a polyfill in order to take advantage of the navigation API for this exact problem: https://github.com/kcrwfrd/navigation-ponyfill

They are actually speaking to trying to make an in-app back button use the history stack so that it _doesn’t_ “break” your browser’s back button.

The problem with just calling history.back() with no fallback is it will bounce users out of your app (back to Google or wherever they came from) and PMs won’t like that…

As someone who went through that same journey, agreed.

Compared to previous paradigms, React lets you compose complexity and rich interactivity really, really well. Even for all its flaws.

I’ve also been writing CSS professionally for nearly 20 years and am a big fan of tailwind.

The ergonomics in my day to day work are quite nice. To me, the better boundary of abstraction shifted to components, rather than the html/css/js “separation of concerns” that some of the older folks still like to parrot.

However, take a look at the markup and styling for the https://maps.apple.com/ web property.

I can’t deny that it’s quite beautiful and easy to holistically understand. Especially when it comes to the responsive styling—which is when I tend to find tailwind most awkward.

It’s my favorite example of “traditional” CSS structure in recent memory that has given me some pause when it comes to Tailwind.

In case anyone else is going crazy trying to find this setting, it’s called slide to type

Aphex Twin, Selected Ambient Works 85-92

Boards of Canada

Mr. Robot Original Soundtrack

I think they have rotating specials. These are pre-made, cheaper, and smaller. When you have a membership this is the one you get for free (once a month).

They used to have a “Dr. Paul's Raw Animal-Based Smoothie” that I looooved, but unfortunately they stopped making it. Still sad about that one :(

For a human this advice is true. But what if a computer can near-instantly calculate a perfect swerve within the performance envelope of the car and driving conditions?

What was the verdict on the smoothie?

I despair at not being able to easily send a window to another space with a keyboard shortcut on macOS.

Yabai supports this perfectly (especially combined with instant, animation-free space switching) but it requires disabling system integrity protection--which is a non-starter on a work computer.

Aerospace solves it with their own spaces implementation.

I was able to put together a hammerspoon script that does the job decently enough for my purposes: https://gist.github.com/kcrwfrd/6f3dcaec0e08e0e77b2884588a34...

Still no support for multiple inputs

It looks like a nice display, but that’s a deal killer for me.

I just pay for the sync.

I like that I can have some vaults that sync to both my personal and work laptops and other vaults that only sync to one or the other.

It’s awfully convenient without any vendor lock in since I can just take my plain markdown files and leave anytime.

Maybe Claude knows that they've been trying to increase their step count and lose some weight

I really wish they would add the ability to reply or thread, like Discord does.

Along with syntax highlighting.

The article on the average pilot and aircraft cockpit design is fascinating.

Now I’m entirely invested, what was the problem causing the crashes? How did they solve it?

Yes I literally worked on a PWA with this exact feature.

I believe you can see it working on TikTok web as well.

You just can’t have the first video unmuted on initial load, although I wonder if this can be relaxed when user installs a PWA.

I drive like this too, but I think we’re a small minority. Especially here in LA.

Haha I did the same with our product manager and designers. One of our designers just got her first (tiny) PR merged this week.

I am somewhat fearful of having created a monster, but at the same time I think it’s good to knock down barriers to knowledge and learning. All else equal, I think a designer or PM with some exposure to code is better than one without.

What I’m fearful of are 10k line PRs and pressure from product to “just ship it.” Past a certain threshold a PR will be really tough to review, to the point that it would be preferable for an engineer to have handled it from the start.

I think we will need deeper integration between figma and the codebase/storybook. Shared color palette definitions, integration of storybook components with figma components, stuff like that.

The Figma MCP that you can use to handover to your agent and simply say “implement this” is already pretty impressive.

Tbh I like the far left way more than the rest. It is simple, clear, and distinctive.

Dead middle is decent too.

I run a 42” 4k at 1:1 pixel ratio and I agree. It’s a little too big, but it does nice double duty for gaming and watching tv.

5120x3200 in 30” would be awesome.

Dan Abramov just posted about this happening to him: https://bsky.app/profile/danabra.mov/post/3mca3aoxeks2i

I've been working on a polyfill for the new Navigation API: https://github.com/kcrwfrd/navigation-ponyfill

I've been super hyped about it. My main goal at first was supporting `navigation.canGoBack` and the `currententrychange` event simply so that I could implement perfect back buttons with (almost) zero edge cases. This is surprisingly very tricky with the older History API.

Today I just opened a PR with support for `entries()` and `currentEntry`: https://github.com/kcrwfrd/navigation-ponyfill/pull/33

Once that lands I'll be able to start thinking about implementing full-blown navigations with it, with cool stuff like navigation interceptors and whatnot. That would actually enable framework router implementations wholly based off the Navigation API, rather than simply patching some enhanced capabilities for use with a router based on history.pushState / history.replaceState.

I find this fun and whimsical, but surely it’s an accessibility nightmare.