3 ms·
Genuine question: What technologies / techniques are you using while your competitors flounder around with GraphQL?
by vosper 6y ago
Genuine question: What technologies / techniques are you using while your competitors flounder around with GraphQL?
- claydavisss 6y agoREST and JSON because arbitrary querying is a huge YAGNI. That said, the presence of GraphQL is a great signal that a team is infested with architecture astronauts, so I suppose it has its uses.
- mschuster91 6y agoTried and true server side rendering. Sure it will not look as snappy as a PWA... but I guarantee you that a seasoned team of Drupal developers can get up and running faster than a team of juniors fresh out of coding bootcamp, or even a team of senior-ish Javascript frontend devs who haven't heard about GraphQL yet, and much less have years of experience.
- jklm 6y agoThis feels like a strawman...I’m sure a seasoned team of GraphQL devs could getting something running faster then a team of veteran devs who are trying to use Drupal but have no experience.
- mschuster91 6y agoNo, it's not a strawman argument. Graphql was released in 2015, so even the most senior devs you can find have only five years of experience (ignoring people who have worked at FB before). Drupal however has a history dating back to 2001!
- vosper 6y ago5 years of experience in any frontend framework, including Drupal, is enough time to learn how to stand something up pretty quickly. I’ve been doing web apps for 15 years: the frameworks are not that complicated. And if we’re picking Drupal because of its age (and if not then why Drupal, of all things? What’s the overlap with GraphQL?) why not go back further and assert that someone who’s great with C and CGI could do even better?