3 ms·
I think React and GraphQL are pretty impressive in terms of how shitty they've made the developer experience at so many companies. GraphQL especially seems to a
by __loam 2y ago
I think React and GraphQL are pretty impressive in terms of how shitty they've made the developer experience at so many companies. GraphQL especially seems to attract the kind of people who love to misuse technologies built for massive orgs in companies with fewer than 100 employees.
- pcthrowaway 2y ago> GraphQL especially seems to attract the kind of people who love to misuse technologies built for massive orgs in companies with fewer than 100 employees. This is almost exactly how I feel about Kubernetes
- paddy_m 2y agoI have worked at companies with more kubernetes pods than customers. They loved graphql too.
- ajb 2y agoThere's actually a well-known effect in standards, that large orgs want to overcomplicate them, as having implemented a bunch of overcomplicated standards becomes part of their moat against competitors. This is definitely done deliberately; the most blatant example is Office Open XML but it's true of others too. They know that they have the staff to waste effort on it, and others don't. I'm not sure anyone is thinking 'lets open source our most dumb ideas to hobble potential competition' - but they would do it if they thought of it.
- chillingeffect 2y agoThat explains some of the experiences ive seen at small companies! From my pov it was "design-by-resume." People wanted to play w tech for their next job, with less concern for what the business needed.
- signatoremo 2y agoThis is the classic example of the quote: There are only two kinds of languages: the ones people complain about and the ones nobody uses
- __loam 2y agoCan we stop pulling this quote out every time someone brings up a legitimate pain point?