> Content from your issues, discussions, or private repositories at rest. We use the phrase “at rest” deliberately because Copilot does process code from private repositories when you are actively using Copilot. This interaction data is required to run the service and could be used for model training unless you opt out.

Sounds like it's even likely to train on content from private repositories. This feels like a bit of an overstep to me.

On the documentation, you install the NPM package via Anthropic: https://sprites.dev/api (on this page, if you select Node)

npm install @anthropic-ai/sprites

Is there some relationship between Anthropic and Fly.io that I didn't hear about?

I noticed the same thing, I suspect it's hallucinated. It seems like the correct package is @fly/sprites --https://www.npmjs.com/package/@fly/sprites

Dang, I just got one and it’s my favorite iPhone I’ve ever had.

For what it's worth, very happy with React and excited to keep the inertia going. "Good enough" in this case is quite good.

Looks like a lot of great improvements, but wanted to put in one vote in favor of keeping the capability of having a JavaScript-forward configuration/usage approach, rather than requiring a CSS-forward approach.

For us, one big benefit of using Tailwind has been that we can avoid spending a lot of time thinking about CSS and CSS tooling, and being able to configure everything via JS has helped in that regard.

That's exactly why critics of Tailwind (like myself) have been so frustrated…Tailwind shouldn't mean you avoid spending time "thinking about CSS". CSS should be a principal and respected pillar of a website's architecture, every bit as vitally important to reason about and understand as anything JS-related. Tailwind v4 promoting CSS-first configuration and customization, and allowing design token usage in vanilla CSS, knocks down a major complaint we've had regarding the framework.

Very cool to combine documents and tasks in this way! Jumping between Google docs with checklists and tickets in Linear can be a bit of a drag.

Thanks! Yes, our strategy is to integrate the minimally-sufficient set of pieces into one coherent experience, to eliminate exactly that need for jumping around between different apps.

Seems like something that will continue unless people vote with their feet and switch to a different platform.

Probably. Though they can also change their settings.

While I agree with you, at the same time I think we need to recognize that most people are very uncomfortable with switching platforms. There's a lot of opportunity costs to most people. People tend not to be long term thinkers and aren't considering the consequences of their actions. For example, look at how many people here on HN -- where tech literacy is high as well as capabilities -- complain about Google's domination of the internet yet at every turn are quick to go after Mozilla and Firefox. The main alternatives are still Chromium based browsers. Same is true about Apple's walled garden. The sad truth is that things won't change unless we can convince the __average__ person, not __a__ person. Hell, I can't even get the most paranoid big brother boomer to use Signal despite it being rather trivial. I just don't know anymore tbh.

If you’re rendering multiple pages concurrently on the server, it’s nice to be able to know, for example, the current user without having to pass it down as a prop through the whole tree.

Context is a really nice way to do this.

Pretty disappointing to see all of these stories being dropped from the front page.