Warp, although it’s not open source.

Thanks for posting. It is heart warming/breaking to watch.

Probably right. But,

> We will not fare any better than Ukraine relying on tech like this.

Ukraine is faring amazing well, aren’t they?

Russia controls a fraction of the territory, has suffered a million casualties, and lost many many armored vehicles and combat aircraft.

> So, it's wining by losing?*

Russia wanted to wipe Ukraine off the map, literally. By simply existing Ukraine is winning.

That's not winning, that's just not losing yet. What a ridiculous thing to claim.

Ok, moving the goal posts works then.

A bit like Putin's war goals.

No, it is carrying out a highly effective asymmetric war. Russia has vastly more resources, but proportionately, Ukraine's forces are being far more effective than Russia's.

Worked reasonably well for the North Koreans and North Vietnamese.

It's a fairly impressive result for the country that was expected to collapse in a week or two.

Unlike many comments here, I love Warp.

Don’t use or pay for any AI features. But it’s really nice having a terminal with multi-cursor and keyboard shortcuts like an editor.

Yea all the AI features seem like a huge distraction to Warp. I hope they don't kill the terminal.

Is there a terminal that offers this same experience,? All the comments here seem to be people crapping on it without trying it. it's really great for someone who develops but spends maybe only 5 percent of their time in the terminal for minor tasks

Good write up, and the author certainly seems to really know their stuff.

I still like using Next, though. Some nitpicks:

> Elements that could change need to be inside a client component, but data fetching cannot happen on the client components, even during SSR on the backend. This results in awkwardly small server components that only do data fetching and then have a client component that contains a mostly-static version of the page

That's one way to do it.

I like flipping it, though - most of the page is a server component, with awkwardly small client components that sprinkle in just enough JS for things that need interactivity (such as optimistic updates from the above quote).

> Since the App Router starts every page as a server component, with (ideally) small areas of interactivity, a navigation to a new page has to fetch the Next.js server, regardless of what data the client already has available!

This is true, and something that Remix v1/v2 did a lot better than Next.

Probably referring to the collaboration tools. Zed has a bunch of stuff around remote pair programming with people.

Can't agree that Tailwind is popular because it forces you to setup a centralized config file (although I guess that is nice).

It's because, as ugly as a long line of inline classes can be, it's easy to know exactly what styles are being applied to an element. Especially when there are more than 1 or 2 devs writing styles.

... do people not know about browser developer tools?

Unless a project has really messed up, it is trivial to see what styles are being applied to any element.

Ah yes, so much easier to poke through the styles in the dev tools than to just put your eyeballs on the css class in the file.

Cool article!

I can hear Sean Carrol saying, though, that:

1. We know general relativity isn’t complete, because it doesn’t take quantum mechanics into account.

2. We can’t say whether this is right because we don’t know the quantum theory of gravity.

But I don’t actually know what I’m talking about.

Could be. Although people sometimes accuse my own blog posts of being AI-generated (they're not, just my shitting writing).

What was Remix got merged into react-router, since Remix eventually was mostly a wrapper around RR + a server.

Now my read is they’re rebooting the Remix name to go their own way on the framework.

As a current Next and prior Remix dev, my rec is both are good in their own way. I wouldn’t hesitate to use react-router if it’s what you want to do.