For me - I don’t enjoy it personally.
574 karma · joined December 24, 2013
Sounds like it's even likely to train on content from private repositories. This feels like a bit of an overstep to me.
npm install @anthropic-ai/sprites
Is there some relationship between Anthropic and Fly.io that I didn't hear about?
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.
Context is a really nice way to do this.
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.
What types of features / compatibility are you looking for?
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 :)
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.
Perhaps someone should develop a platform that creates the same discoverability, but while allowing people to retain control of the content?
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.
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.
(Disclaimer: I work on the Apollo team)