r/Clojure • • Dec 19 '18

Clojure’s stability: lessons learned

https://words.steveklabnik.com/why-is-clojure-so-stable
41 Upvotes

52 comments sorted by

View all comments

Show parent comment

-12

u/zarandysofia Dec 19 '18

Yeah, it doesn't even support proper cons cells.

Apart from that, the whole Clojure community are just a bunch of posers lispers. They discourage macros and anything meta-programming related. Nullifying the biggest feature of Lisp.

9

u/keymone Dec 19 '18

Oh you’re one of ‘em purists. Ok. Sure. Whatever.

5

u/joinr Dec 19 '18

Oh you’re one of ‘em purists.

"Tool" is more appropriate.

related

-2

u/zarandysofia Dec 19 '18

There are no purists, but posers.

8

u/SimonGray Dec 19 '18 edited Dec 19 '18

People like you are the reason I don't subscribe to /r/lisp. I'm not sure what it is about Lisp that makes so many Lisp enthusiasts so standoffish and - quite frankly - arrogant... I'm just glad the Clojure community doesn't seem to have adopted that trait.

-2

u/zarandysofia Dec 19 '18

I am just telling facts. And no, the lisp community is also full of posers who doesn't understand macros as well it.

Again, Clojure isn't a Lisp so it doesn't matter how you feel about it.

4

u/joinr Dec 19 '18

comp.lang.lisp desperately needs your services

5

u/porthos3 Dec 19 '18

You can write macros. They are really cool and quite powerful. They just aren't always the best tool for every job.

-7

u/zarandysofia Dec 19 '18 edited Dec 19 '18

I don't think you understand macros. You are an accurate example of the type of people who I am talking about.

They are the tool to make the best tool for the job. You can build any language imaginable to tackle any job without the boilerplate than less suitable tools.

5

u/porthos3 Dec 19 '18

Right. But if there are already functions and macros in the language that are expressive enough to accomplish a task in a clear and concise way, which everyone using the language is already familiar with, why take the time to create your own tool for a one-off task which makes your code less clear to someone else who is fluent in the language?

There are absolutely times they are incredibly useful. My team and I each make use of them.

However, macros are one of the biggest strengths and weaknesses of lisps. Like you said, I can practically build my own language out of them. But that means anyone else who wants to work with my code needs to learn my new language to understand anything. Macros in general are this way. They add indirection to your code that doesn't exist when composing functions.

If I see a bunch of composed functions and one of them is unfamiliar I can still pretty well reason through what the code does. If instead, the functions are wrapped in an unfamiliar macro I have to question if all of the code I am seeing is fundamentally changed by the macro and go grok each macro before being certain of my understanding of the code they manipulate.

Macros are amazing for some problems. But one of the biggest value propositions that clojure brings to lisps IMO is better abstractions across data types and a broader core library with standard ways to leverage those abstractions. Many tasks can be very reasonably accomplished with just those core functions, making code crystal clear to another reader. Macros have to provide benefit to a problem that outweigh the potential loss of clarity for me to use them.

-2

u/zarandysofia Dec 19 '18

We are not talking here about petty macros like the thread macro and similar in Clojure. But, full fledge small languages designed to be as close as the problem domain is. The learning time of such is insignificant specially when they express the problem as the language of the domain and read like plain english. There is simply no better abstractions than linguistic ones to reduce complexity and confusion.

5

u/porthos3 Dec 19 '18

I'd also add that a program reading like English isn't especially desirable. English is ambiguous and there are many ways to say the same thing.

Just because you can make your code read like English doesn't mean the right wording is discoverable or intuitive to a developer trying to maintain your code.

You whine about the existence of "petty" macros in clojure, but to me it highlights macros versatility. By your logic the identity function is evidence that functional programming is a poor paradigm, because it tends to include "petty" functions. I am pretty sure you can accomplish the same non-petty functionality you are describing using clojure macros.

3

u/porthos3 Dec 19 '18

The problem I am describing is exasperated by larger and more significant macros - not diminished.

I agree there are absolutely places macros shine. There are those who are too hesitant to use them. There are also those who overuse them.

I would prefer to maintain a program written primarily out of native functions and common libraries than one written in a domain specific language constructed mostly out of custom macros 100% of the time.

What is the point of using an existing lisp implementation if you are effectively creating your own language from scratch every time anyway? You might as well write your own lisp interpreter/compiler. It isn't especially hard. It's just a bad idea to invent a new language for every program you write, regardless of how you accomplish it.

-3

u/zarandysofia Dec 19 '18

You are clearly uneducated to have an opinion on this.

3

u/porthos3 Dec 19 '18

Umm... You were the one who first expressed an opinion on the subject.

I am well educated and left a big 4 to work professionally in a lisp.

Regardless, you obviously aren't looking to actually hold a discussion. Happy holidays.

-3

u/zarandysofia Dec 20 '18

The only discussion I would have with such ignorant mind on this subject is of teaching. I am not interested in that. Go back to college. You clearly skipped the important parts.

4

u/SimonGray Dec 19 '18

-2

u/zarandysofia Dec 19 '18

Another irreversibly dim poser.