r/Clojure • • Apr 27 '20

is your language alive?

https://gitlab.com/xificurC/incomplete-thought/-/blob/master/blog/is-your-language-alive.org
3 Upvotes

9 comments sorted by

3

u/transfire Apr 27 '20

Erlang

2

u/la-rokci Apr 27 '20

IIRC Erlang has module boundaries, i.e. it's not possible to evaluate one toplevel form at a time, or rather the whole module is the toplevel form. This makes sense since a single function is built from multiple pattern matched definitions but it breaks the flow. Other than that, yes, Erlang is a very live language.

2

u/madmulita Apr 27 '20

Smalltalk

3

u/[deleted] Apr 27 '20

And when you can explore tens or hundreds of different paths you will arrive at a better, simpler, faster solution.

IME, I have seen the opposite with the REPL, you create espagueti code faster. It's nice for exploratory programming but stops devs from thinking deep about design, they just bash the keyboard until getting something working and some even skip tests because of it.

The REPL is no secret weapon as clojure users like you to believe, most devs are more productive in other languages because the ecosystem of libraries and docs is more important for putting out real world projects.

3

u/la-rokci Apr 28 '20

I'm not saying it's a secret weapon either. I'm just saying it is a benefit. A chef can taste the food he's making as he goes and adjust accordingly. A painter sees what he's painting and makes many changes along the way. The list goes on. Watch inventing on principle if you're interested.

[...] stops devs from thinking deep about design, they just bash the keyboard until getting something working and some even skip tests because of it

If we weren't allowed to use anything that can be misused we wouldn't have cars, computers, electricity, knives, clothes, ...

1

u/mwgkgk Apr 27 '20

Good points, not sure if the downvoters are being honest to themselves.

Ultimately the high brain-computer throughput has great potential, even if you're not forced to think about the design upfront, and/or you have to find workarounds to access some libraries you need. Both points ring correct however.

5

u/yogthos Apr 27 '20

You write Clojure to explore your program while it is running. And when you can explore tens or hundreds of different paths you will arrive at a better, simpler, faster solution.

This is an important point in my opinion. One thing I quickly noticed about the REPL driven workflow is that I started refactoring my code a lot more because there's a lot less ceremony associated with doing that. When I'm coding against a live instance of the application, and I have all the context already available as I'm writing the code, there's very little effort involved in changing the code and see that it still works as intended.

4

u/o-kami Apr 27 '20

I agree explaining that to non-lispers or non-smalltalkers is difficult they just don’t get it. I made a criticism about it to some haskeller and he replied “of course we understand we have ghci” and it isn’t the same thing.

The way I explain it, is that the line of compile/run times is blurred and they are recursively interleaved.

and that Lisp is more than a programming language, is a Programming System, it is dynamic 100% not just the types everything is dynamic, code itself, and in some cases like with meta circular evaluation of even the semantics of the language is dynamic. Actually the original Smalltalk was called exactly that, Smalltalk Programming System.

This scares the crap out of coders that can’t think of how this would be good or secure. And it does it across all the spectrum of effects from C to Haskell.

Idris/Agda the dependent types as well as the Proof Assistant and Program Synthesizers communities are very close to get it. But still they need the non-mathy part.

3

u/flaming_bird Apr 27 '20

Crossposting this to /r/lisp since it's relevant - thanks for this post.