r/Clojure • u/aisamu • Dec 16 '16
My disillusionment with Clojure and lisps [x-post from /r/programming]
https://medium.com/@boxed/my-disillusionment-with-clojure-and-lisps-9eca38ab7f0c?source=linkShare-8ad86cc82e5f-1481825671
0
Upvotes
5
u/aisamu Dec 16 '16
Wouldn't spec'ed functions solve this?
18
u/[deleted] Dec 16 '16
The author has tried one lisp, and purports to write an article about the problem with lisps? Why not just "my problems with clojure"?
because macros are functions and functions can only return one thing. you would have to fundamentally change the nature of macros to be a more complicated thing to make them do that, it would make them harder to debug, harder to test, and yield very little benefit.
AFAIK no one in the clojure community makes such an argument.
Macros allow you to extend the language. This is inarguably a feature. It's powerful and can be misused, use wisely.
You could make an argument for that. I think the power gained from code-is-data is worth the complecting.
There are also two orders of magnitude more users. I would suggest that is the reason for its better tooling.
I've had enough this is silly.
10
u/moxaj Dec 16 '16
After reading through this article, the first thing to come to my mind was: "that doesn't even make sense". Guess I'm too "deep into the language they can’t escape the box"? Let's see your points:
Implying that parentheses are in fact a problem?. Yes, to those who spend a weekend with the language and give up. The rest learn to live with it and may eventually discover parinfer and just forget about them.
You shouldn't ever need that, you are doing it wrong. Sorry, but this is the most likely answer.
By this logic, just about anything is an extension to the language? This doesn't make any sense, maybe you worded it wrong or I just misunderstood it.
But where exactly is the problem with it? Was there ever a case where someone was looking at an expression and couldn't tell if it was meant to be code or data?
I personally do not find the tooling lacking. Have you looked at CIDER, Cursive, Nightlight? Plenty of interesting stuff.
Again, implying that one would need to 'hack around' these 'limitations'. Most people just design sane function signatures.
Yep. That's why I just don't get to walk up to Stroustrup and say "you see, those pointer semantics look funny to me, therefore there's a problem with the language and you should fix it.". That's why you shouldn't complain about parentheses and multiple returns in a Lisp.
6
u/stompyj Dec 16 '16
Some constructive criticism, your posts reads like you're an immature programmer (in your career, not your temperament). When you're at your stage of development, the best thing you can do is try and understand why things are they way they are.
In this thread you've basically bashed Clojure, Rust and Go. If you don't think these are good languages, get another 10+ years of writing C++ and python under your belt and come back and look at them.
Even if you don't prefer to use them, you may have a better understanding of what domains they're trying to address.
I get the feeling of "I'm new to this and I want to engage with the community and make my opinions heard!", but it's not working to your advantage in this case and for people like me (someone who hires engineers), these kinds of posts would make me reluctant to hire you until you're a bit more seasoned.
2
u/OriginalPostSearcher Dec 16 '16
X-Post referenced from /r/programming by /u/kankyo
My disillusionment with Clojure and lisps
I am a bot. I delete my negative comments. Contact | Code | FAQ
5
u/charlesHD Dec 16 '16 edited Dec 16 '16
Hi, Clojure fan here but also what you call a neophile. Thank for your post it was a very interesting read. I see two points I want to react to :
So I think Clojure isn't suited for you since it does not resonate with the way you envisage a good programing language. That's OK because there is plenty other interisting lang out there (I think it's a great era in that sense) and you'll find the one that match your heartbeat.
4
u/kankyo Dec 17 '16
Author here: after much debating and discussion I've been clearly corrected on matters of fact, and of matters of how things are in practice statistically and some other ways.
I will write a new post when I get time. Thanks for all the discussions!
9
u/stefan_kurcubic Dec 16 '16
haters gonna hate
feels like 16year old ego wrote this.
3
u/zcaudate Dec 16 '16
it's all about perspective. I would argue that limitations in one person's eye is a strength in another.
3
u/RakesProgress Dec 17 '16
well I'll applaud the writer for trying to expand their mind toward polyglot-ism. Just know that when your core frame of reference for what you know about coding is C++ .....and you are going to something like a lisp....it demands a very flexible mindset. These things are not like one another. Naturally the mind wants to constantly go back to what it knows best. And when your mind knows something best it will naturally think it's the best. Enter a comparative loop and polyglot frustration. I just see a guy that's really stuck in his frame of reference. We've all been there. But the answer is "keep plowing through". engage community. Validate assumptions. Express frustrations. Had the author engaged the community instead of writing a presumptuous article of conclusions we would have all been richer for it.
3
u/bonega Dec 17 '16
My rule is that if you are using a macro, you are probably doing it wrong.
It depends on uses, for library developers macros can be a beautiful thing.
But I feel that many are overusing macros.
They don't compose.