3 ms·
All of these articles are kinda click baitey sugary snacks for junior developers in my opinion. It’s conflating too many concepts and introducing too many varia
by whalesalad 9y ago
All of these articles are kinda click baitey sugary snacks for junior developers in my opinion. It’s conflating too many concepts and introducing too many variables. A vanilla comparison of GraphQL versus REST -or- Python (not Django) versus Clojure would have been more interesting.
You can build anything with anything. It’s all data manipulation. Some languages have a more fruitful ecosystem of libraries or offer a more efficient syntax for your particular task.
To be honest, the way that graphql is handled by the author in Clojure looks kinda inefficient. You have a language that allows you to create your own dsl with abstractions and macros but you write a massive edn map of your types? What’s the difference between that and using any other language at that point?
Interesting insight but I hope folks don’t read this post and think: “wow we are wasting our lives with Django and REST”. The four technologies here all have value and merit in their own ways.
P.S. I use Clojure and Python on a daily basis at FarmLogs
- rlander 9y agoI agree with you that that wasn't the best comparison. As I wrote somewhere downthread, in a perfect world, I'd be comparing Clojure/GraphQL with Python/Graphene. But it is what it is and, even though the project I could compare to wasn't ideal, I still think we were able to draw valuable lessons for our use cases. It isnt't feasible to choose a technology just because it would be a better comparison. > Interesting insight but I hope folks don’t read this post and think: “wow we are wasting our lives with Django and REST”. God no! As the author, I hope to god no one thinks that after reading the article. We're mostly a Python shop and we love it, but sometimes it isn't the best choice.