Launch HN: Scaphold.io (YC W17) – GraphQL Backend as a Service
I don&#x27;t buy into the GraphQL hype. Actually it is a rehash of older technologies like RDF &amp; SparQL, but marketed to a newer generation who didn&#x27;t know that old things exist. I&#x27;d wager that the 20-something &quot;engineers&quot; who designed it didn&#x27;t give a shit about prior art either.<p>I&#x27;m sure that Facebook employees think it solves a lot of problems for them. But I&#x27;m not convinced that a single vendor technology is going to be viable on the web. Web standards come about through standardization processes, with multiple stakeholders reviewing and revising drafts. Facebook one day puts up the GraphQL spec out of nowhere and defines the &quot;standard&quot; by themselves, based on their own implementation.<p>A little history: Facebook tried to subvert HTML with FBML, a proprietary markup language designed for use within the Facebook ecosystem. Long story short, it didn&#x27;t work out. The various SDKs and APIs by Facebook have been notoriously unstable.<p>People tend to excel at short-term thinking, kudos to Facebook for that, and lack the foresight for long-term thinking, except for a few visionaries. The architecture of the web has lasted a few decades already, it will outlast a single vendor specification.