REPL vs CLI: IDE wars

Post by vmladenov » Fri, Jul 02, 2021, 12:28 AM UTC

theshadowknows wrote: post #90

pjmlp wrote: post #44

Earlier quoted context omitted.

And I recommend trying out Smalltalk.

As a hobby I want to learn a lisp. Where should I begin? :)

Post by ebeip90 » Fri, Jul 02, 2021, 1:26 AM UTC

drran wrote: post #83

aidenn0 wrote: post #59

Earlier quoted context omitted.

"man set" can't provide that information trivially without knowing your shell; dash/bash/ksh/zsh will all be subtly different. However, if you are running bash, "help set" is fine. FWIW, I really don't like pipefail as a default (e.g. piping to "head" causes random pipefails) and -e also has some confusing semantics. Also either failglob or nullglob are more important than either and -C is useful for some scripts as…

> (set -e; echo hi); echo $? It works in my shell. :-/ It looks like you forgot to insert `false` command. You are pointing to the problem with -e not working in subshell/deep functions, because of POSIX. Right? It's described in bash documentation: http://www.gnu.org/software/bash/manual/html_node/The-Set-Bu... > I think just defining a die() function and using it after any command that must succeed is more verbose,…

    An error occurred on ./test:18
    Frame 1 (./test:21)
    18           false
    19       }
    20
    21   >>> a

    Frame 2 (./test:6)
    3        source TRAPERR.zsh
    4
    5        a() {
    6    >>>     b
    7        }
    8
    9        b() {

    Frame 3 (./test:10)
    7        }
    8
    9        b() {
    10   >>>     c
    11       }
    12
    13       c() {

    Frame 4 (./test:14)
    11       }
    12
    13       c() {
    14   >>>     d
    15       }
    16
    17       d() {

    Frame 5 (./test:18)
    15       }
    16
    17       d() {
    18   >>>     false
    19       }
    20
    21       a

Post by AceJohnny2 » Fri, Jul 02, 2021, 3:37 AM UTC

massysett wrote: post #89

AceJohnny2 wrote: post #67

Earlier quoted context omitted.

Off-topic, but Bash's manpage is awful and a great demonstration of the limitation of manpages. Not that the content is bad (it's great!), but as OP (and you) demonstrated, finding relevant information is close to impossible in the humongous document. In Bash's defense, its manpage is a concession to people's habits, and its documentation really rests in its Info page. Except that doesn't seem to be popular either (I…

Contrary to typical GNU practice, the bash info manual states that it is intended as a “ brief introduction” and that the man page is the definitive reference on shell behavior: https://www.gnu.org/software/bash/manual/html_node/index.htm...

Post by utxaa » Fri, Jul 02, 2021, 4:18 AM UTC

tsimionescu wrote: post #80

utxaa wrote: post #69

Earlier quoted context omitted.

i get the magical aspect of repls in scheme and CL. not in clojure. not sure why. so i don't like clojure, but i feel like i should ?? why is that?

As I said, I think Clojure is significantly iimpacted in how much dynamic reconfiguration it can handle by compiling down to the JVM. Still, personally I have little to no experience with Clojure, so I can't really comment too deeply.

Post by kinjba11 » Fri, Jul 02, 2021, 5:51 AM UTC

blacktriangle wrote: post #3

tomconnors wrote: post #2

This post could be summarized as "write as much of your project's tooling as you can in the project's main programming language and the project's main programming language should be Clojure" and I agree wholeheartedly.

I think their point is bigger than that. Historically one of the major points against using Clojure to write your tooling was the slow startup times which are just painful from the CLI. It looks like the clj-exec idea linked to in the article is the secret sauce that makes moving to writing your tooling in Clojure a workable idea, since now you have a unified calling convention for both calling tooling from the REPL…