3 ms·

> In reality, of course API versioning is needed. I’d recommend not picking a technology that is versionless by design if you think you’re going to need it. Al

• JohnHaugeland 4y ago
  > I’d recommend not picking a technology that is versionless by design if you think you’re going to need it. I mean, I don't pick GraphQL, and this is just one small part of why. Every place that I've ever worked that's attempted to adopt GraphQL has rapidly given it up. . > Also I’d dispute that versioning is needed as a rule. The IEEE once measured peoples' expectations regarding how necessary versioning was, and got a response of something on the order of 40%. There was an uproar, and a whole bunch of people on both sides of the topic tried to call bullshit. Some middle manager somewhere sent in a letter that said approximately "how about you write a follow-up article where you bin the responses by years of experience?" The rest of the story writes itself.