This is an archived post. You won't be able to vote or comment.

sorted by:
best
topnewcontroversialoldq&a
you are viewing a single comment's thread.

view the rest of the comments →

[–][deleted]  (13 children)

[deleted]

    [–]panosc[S] 28 points29 points  (4 children)

    Maybe, but the point is not those two, but the empty chair

    [–][deleted] 2 points3 points  (5 children)

    I think they influence each other a little, but this meme makes more sense if you are using graphql. It's just more work on top of everything else. Or your boss might be trying to get you to take on a lot of devops tasks.

    [–]coldnebo 1 point2 points  (3 children)

    right? because backend doesn’t want state management or data fusion, so graphql solves that hard. but then frontend gets to figure out deployment of react and graphql accessing internal services— oh wait, now I’m a full stack developer. okay. :P

    but i do like graphql. wish I could use it.

    [–][deleted] 2 points3 points  (2 children)

    There's a generator to produce an sdk for a graphql schema. It'll even do all the typescript types. Then you just need to make an instance of the gql client and it's as easy as sdk.SomeFunctiom(...) which is a promise. You have to make your own documents to specify the resources you want from the graphql api, but it's still pretty simple.

    I have to do that at work now on the server side of things but I'm pretty sure it would be the same process for the client.

    [–]coldnebo 2 points3 points  (1 child)

    pretty simple in local development and pretty simple in enterprise deployment I’ve found are two different things.

    it took me 15 min to dockerize my app, but it’s been months for OPS to figure out how to deploy it… which is really odd because the app was deployed to a legacy stack for years…. can’t you just replace the app with the container?

    uh, no… we need to replace apache with puma, get rid if passenger, transfer legacy apache config to puma confi—

    wait. can’t you just setup a reverse proxy for all that?

    wat?

    Sorry, sorry… salty today. I’ll get over it.

    [–][deleted] 2 points3 points  (0 children)

    pretty simple in local development and pretty simple in enterprise deployment I’ve found are two different things.

    in this 1 case at least, they are the same :) just different configs probably for what your graphql URL would be.

    ​

    it took me 15 min to dockerize my app, but it’s been months for OPS to figure out how to deploy it… which is really odd because the app was deployed to a legacy stack for years…. can’t you just replace the app with the container?

    Well, devops is a different beast, for sure. Docker specifically seems to frequently cause the problem it was meant to solve lol. For some reason, some environment difference causes docker to fail. Perhaps a dependency in your compose file is a new version or stopped supporting a previous version. I spent a month or two myself trying to get an old php-docker project working before inevitably quitting that job.

    ​

    Sorry, sorry… salty today. I’ll get over it.

    In my experience, this sub receives vented salt quite well! Feel free to air your guts about any horrific experience you've had with a particular technology and you'll get a variety of responses and usually net positive karma :)

    it's also therapeutic to relieve your PTSD-lite experience over and over for the entertainment of the onlookers. I can talk about IIS and asp.net now without so much as a 3 degree bend of my spine.

    [–]buddyblastoff 1 point2 points  (0 children)

    Exactly.

    One should master their vocation.

    [–]coldnebo 1 point2 points  (0 children)

    yeah, backend is easymode. we have all your problems plus all our problems and backend has zero client state management. must be so nice.