undefined | Better HN

0 pointsiamEAP6y ago0 comments

I'm personally in the same boat (and use a philosophically similar JS-based framework called SailsJS instead, right now)

For me: I need services that support the UI, as well as a public-facing API with basically the same data. I don't have the time/resources to build/maintain them separately, and my perception is that GraphQL and the wider ecosystem around it haven't yet reached the same level of ubiquity/maturity as plain-old REST.

A single, well-designed REST API that can be consumed by my own UI as well as public clients is how I'd prefer to handle it right now.

0 comments

1 comments · 1 top-level

Rapzid6y ago

Would have to agree. GraphQL is kind of a non-starter for every project I've worked on in the past few years, and a GraphQL ONLY framework is right out.

j / k navigate · click thread line to collapse