djmashko2

There’s only one “the platform” but there were tons of competing libraries to do things like css, components, etc. The competitive landscape just produced better results. For me, Tailwind is nicer to use than regular CSS, and React is nicer to use than web components.

For me - I don’t enjoy it personally.

> 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.

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

Having seen a lot of negativity around it, just want to say that the iPhone Air is the most exciting iPhone to me in a while -- I've been waiting for a big but still light option, but with the top-of-the-line CPU and a decent camera, for a long time. Will be curious to see how it pans out in the market, but I imagine I'm not the only one.

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.

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.

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

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.