A Case for Clojure and GraphQL: Replacing Django

by rlander on 10/14/2017, 5:20 PM with 55 comments
  • by dizzystar on 10/14/2017, 7:05 PM

    Outside of very special circumstances, I don't think it is a good idea to replace Python code with Clojure code. In fact, judging from my own contracting experience and seeing the many mistakes made by first-time Clojure programmers, I more often than not suggest moving from Clojure to anything else.

    The problem with using esoteric languages is multi-fold. First, you have to trust that the original programmers actually know the language enough to not create a massive disaster. Are they comfortable working without a framework, are they knowledgeable about all the issues that arise from building closer to the metal, so to speak? It seems to me that the answer is "no" more often than "yes."

    Once this happens, you end up in a read-only code situation, and this is a problem because they leave the project with tons of bugs and downright stupid decisions. You are then left in the position to ask 15 people if they can make dollars or sense of anything written, and if you are fortunate, you will get one "yes." I joke that I know all 50 Clojure programmers in the US, and sadly, that's not much of an overstatement. If you want your code to exist, and you aren't a real somebody, then good luck. If you aren't located in SF, LA, or some other city that attracts talent, definitely do not use Clojure or any other esoteric language!

    Of course, I didn't read the article, as it isn't loading at all.

  • by lilbobbytables on 10/14/2017, 9:42 PM

    One concern I have with Graphql is security and access to data.

    I'm sure there are plenty of ways to control it, but I'd wager that most will be ignored outside of basic ACL’s.

    Often times certain user types should only have access to certain fields in data or be able to query it in certain ways.

    Too often I see apps where the developers just assume they have full control since they're making the interface, while it's trivial to watch the API calls and intercept or modify them.

  • by douglaswlance on 10/14/2017, 7:47 PM

    You can implement GraphQL using django-graphene pretty easily. Django Rest Framework + graphene is fantastic for auth and easily maintained endpoints.

  • by ivan_ah on 10/14/2017, 7:03 PM
  • by jefurii on 10/14/2017, 6:59 PM

    Error 502 Bad Gateway

  • by rburhum on 10/14/2017, 7:35 PM

    503 Service Temporarily Unavailable

  • by douglaswlance on 10/14/2017, 7:46 PM

    You can use GraphQL with Django.

  • by Areading314 on 10/14/2017, 6:13 PM

    Error establishing database connection

    lmao