Twitter | Search | |
Ian Storm Taylor
Co-founder of Segment.
5,332
Tweets
521
Following
5,011
Followers
Tweets
Ian Storm Taylor retweeted
Darrel Miller Oct 13
If you are interested in GraphQL because it reduces network round trips then you should read this article. If you are designing an API to support batch requests, you should read this article.
Reply Retweet Like
Ian Storm Taylor Oct 12
Ever used the `fetch` API and have wished it had a `timeout` option? I wrote up an issue you might like…
Reply Retweet Like
Ian Storm Taylor Oct 12
Totally! That makes sense. And for the super low level API having that kind of detail is important. But as for as ergonomics, it's frustrating people seem to be treating timeouts for Fetch as "solved" now that we have AbortController. But the UX is not good at all.
Reply Retweet Like
Ian Storm Taylor Oct 12
Yeah definitely. Just would love to see some better ergonomics from the browser APIs themselves so we need fewer wrappers 😄 Hopefully we’ll get a `timeout` option in the fetch args.
Reply Retweet Like
Ian Storm Taylor Oct 12
Replying to @jaffathecake
Ah that makes sense, thank you! It seems unfortunate that it complicates the 90% case for a something that’s more of a 10% concern.
Reply Retweet Like
Ian Storm Taylor Oct 11
I was just wondering if you could explain… for the AbortController API, what's the need for the extra AbortSignal object indirection? Why not just merge the two into a single object? Thanks!
Reply Retweet Like
Ian Storm Taylor retweeted
Amelia Wattenberger Oct 11
Started a blog post I've been itching to write: ✨How to combine React + D3.js✨ Let me know if there's anything in particular that you struggle with, whether it's "how do I draw axes?" or "how the heck do I animate elements?!"
Reply Retweet Like
Ian Storm Taylor Oct 8
Replying to @devongovett
Nice, looking forward to when it's released! It would be so nice to finally have a single bundler that had reasonable defaults for both apps and libraries.
Reply Retweet Like
Ian Storm Taylor Oct 8
Replying to @devongovett
That is awesome! Great defaults. Does it have support for building UMD files (ideally max and minified) using similar quick config? Curious because I'd love to be able to replace microbundle for building libraries.
Reply Retweet Like
Ian Storm Taylor Oct 7
Replying to @estejs @typescript
`Predicate` is a great type utility idea. I love it!
Reply Retweet Like
Ian Storm Taylor Oct 7
I love seeing libraries get steadily better with simple features like this. Next.js has such good momentum. Especially when you realize that a new feature is a superset of an older one and the older one can be deprecated. That's one of the best feelings!
Reply Retweet Like
Ian Storm Taylor Oct 4
Replying to @benschwarz
It's funny because this is the natural and sane reaction to using GraphQL as a public API… to end up creating a set of "canonical" queries and mutations for your users, so that they aren't lost. And you end up in a similar place to REST, which is actually not a bad thing!
Reply Retweet Like
Ian Storm Taylor Oct 4
Replying to @MattMueller
Page-specific and REST sound like antonyms to me 😄 But you’re right. That’s probably a difference between a single person owning both, and a single company owning both.
Reply Retweet Like
Ian Storm Taylor Oct 4
Replying to @jorilallo
Definitely curious to hear your take as you keep going! I'm also unsure. From the client's perspective it's good—assuming they like GraphQL. But from the server's, although it introduces new capabilities, it also dramatically increases the upfront *and* maintenance burden.
Reply Retweet Like
Ian Storm Taylor Oct 4
Replying to @ianstormtaylor
The key here is *public* APIs. For private APIs where you control both the client and server, some of the fake benefits become real. And GraphQL is a lot more beneficial. But public APIs have much stronger contracts and expectations, and benefit less from powerful clients.
Reply Retweet Like
Ian Storm Taylor Oct 4
Replying to @ianstormtaylor
…the list of *fake* ones though, that seem good but actually just shift complexity: - Versioning (no diff) - Auto-docs (not legible) - Sparse fields (less reliability) - Errors (less interop) - Analytics (less interop) - Clients (small diff) - Mutations (less symmetry)
Reply Retweet Like
Ian Storm Taylor Oct 4
If you're building a *public* API, the real benefits you get from GraphQL aren't most of the hyped ones: + Batching (performant) + Relationships (convenient) + Schema (extendable) A small, useful list of *real* benefits. But…
Reply Retweet Like
Ian Storm Taylor retweeted
n.s.f.m.c. Sep 27
is it common knowledge that the H's crossbar in U-HAUL is a tow hitch? had i just never noticed this?
Reply Retweet Like
Ian Storm Taylor Sep 27
Replying to @nsfmc
Wow! That's kind of amazing. I never realized that either.
Reply Retweet Like
Ian Storm Taylor Sep 27
Replying to @MattMueller
Ohhhhh, multi-cursors for a single person. Totally different. That would be amazing :D
Reply Retweet Like