djmashko2

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?

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.

Role: Founding engineer, joining two technical founders

Location: New York or USA remote

Flipturn is a funded early stage startup working on increasing adoption of commercial electric vehicles (EVs) -- vans, buses, trucks, etc. The two technical founders are ex-Stripe, Samsara, and Apollo GraphQL, with a track record of delivering products from zero to product-market fit.

We've found that vehicle fleet managers are excited about EVs, but need a lot of help to make it through the whole process of evaluating and buying EVs. A lot of these revolve around planning and simulations, and can be significantly improved with software!

The commercial vehicle industry hasn't been saturated with software tools, and so this is a unique opportunity to work in a very greenfield environment where you can make a big impact on a huge industry -- over 12 million commercial vehicles are sold each year.

If you're interested in a super early stage role an have wanted to contribute to reducing emissions and fighting climate change, this could be the perfect opportunity!

Please email me at sashko@getflipturn.com if you're interested and want to chat.

would this make it possible to install Postgres from NPM for local development? could make it much easier to build/run an app vs. installing Postgres on the machine directly, or running in a Docker container.

FWIW on Mac you can copy-paste a file between devices using the iCloud paste thingy.

Things! The todo list app. It's the most elegant app I've ever used. feels like it just works, and I can rely on it 100%.

(Hi! I work at Stripe on the JavaScript SDK)

What types of features / compatibility are you looking for?

I'd be interested in seeing this exam!

There are plenty of uses for Twitter unrelated to debate or discussion. Sharing news, building a community, posting about your day, etc.

That would be amazing actually - I frequently run into situations where some combination of colors doesn’t have enough contrast in my editor.

Hi! I work at Stripe on the Dashboard.

You can delete all of your test data by clicking a button in Settings > Data (/account/data). We also recently launched a feature that lets you delete multiple customers at a time, and hope to expand that to more different types of objects soon!

Thanks for the feedback, keep it coming :)

(disclaimer: I worked at Meteor/Apollo for about 5 years)

I love the callout to how this is continuing the vision for improving application development started with Meteor -- it really does feel that way to me. Apollo, supported by GraphQL is IMO really delivering on the vision of making a lot of aspects of client-rendered app development much more straightforward than they have been in the past.

I write them down in Things and group them into projects, makes them easy to search and organize!

If I'm using Safari as my default browser, does it make sense to switch to Firefox just to support them? Interesting that Safari is not coming up in any of these articles as a third competitor, but maybe the fact that it's limited to Mac means it has very small market share.

As some anecdotal evidence, I get about half of my Medium views from people browsing the Medium app/feed. That's definitely been the number one reason I've stayed on the platform.

Perhaps someone should develop a platform that creates the same discoverability, but while allowing people to retain control of the content?

Apollo Client contributor and user here - which abstractions are you referring to?

Open source lead at Apollo here.

Syrus is correct that it will have about the same performance as Node in these particular benchmarks.

We are working on performance improvements for Apollo Server 2.0, but they are targeted at a totally different use case. Our experience working with hundreds of companies using GraphQL in production has indicated that the CPU execution time of the query is almost never the bottleneck when it comes to GraphQL.

The real thing you want to watch out for is the time it takes to call underlying APIs and databases, which will absolutely dwarf the actual time spent in the CPU. In this case, Node's non-blocking architecture helps a ton, and taking any action that prevents repeated calls (like basic caching) is critical.

In AS 2, we're going to introduce some features that make caching underlying data calls even easier, which we think is going to have the biggest impact on people's response time with GraphQL.

Open source lead at Apollo here:

The most important thing about the persisted queries approach highlighted in that article, compared to traditional REST architecture, is that the queries live in your _client_ codebase. So the frontend developers write the shape of the data, rather than backend folks hardcoding it in like with endpoints.

I would say that at the current moment only a small minority of GraphQL users (based on our experience) are using persisted queries, and running in production without that is just fine with good performance and security. A simple approach like query timeouts, or discarding queries based on complexity, goes a long way here.

One really neat thing is that the clients are based on the MIT-licensed Apollo Client. So we hope that everyone using GraphQL can easily get these benefits! Check out the code on GitHub: https://github.com/awslabs/aws-mobile-appsync-sdk-js/blob/25...

(Disclaimer: I work on the Apollo team)

Note that "forever" here means "for as long as this specific browser tab is open", both for GraphQL and for Redux.

Jonas Helfer gave a talk about this: https://www.youtube.com/watch?v=coU6OmISOBM

You're in luck, there are libraries that can do it for you! https://github.com/stems/join-monster

And even a system that generates your whole schema: https://github.com/postgraphql/postgraphql

Plus, the Graphcool framework allows you to bring your own DB: https://github.com/graphcool/framework