Author Topic: I get emacs, but WOW... the LISP learning curve ... and WHY LISP?  (Read 10347 times)

0 Members and 1 Guest are viewing this topic.

Offline sokoloff

  • Super Contributor
  • ***
  • Posts: 1803
  • Country: us
Re: I get emacs, but WOW... the LISP learning curve ... and WHY LISP?
« Reply #25 on: October 26, 2022, 10:06:47 pm »
The big “win” in a DSL is if you can enable non-programmer domain experts to use it without them thinking they’re doing “programming”.

If it feels like programming, I tend to lean towards just giving the user the full power of the programming environment.
 

Offline tggzzz

  • Super Contributor
  • ***
  • Posts: 23122
  • Country: gb
  • Numbers, not adjectives
    • Having fun doing more, with less
Re: I get emacs, but WOW... the LISP learning curve ... and WHY LISP?
« Reply #26 on: October 26, 2022, 11:07:34 pm »
The big “win” in a DSL is if you can enable non-programmer domain experts to use it without them thinking they’re doing “programming”.

If, and it is a big if, that ever works then the programmes are trivial. When the users ask for "if then else" statements, you need to specify variables, then scope and lifetime, then what constitute equality, etc.

Who was it that said something to the effect that "if you allow people to program in English, then you will find people cannot write English"

Quote
If it feels like programming, I tend to lean towards just giving the user the full power of the programming environment.

See above ;)
There are lies, damned lies, statistics - and ADC/DAC specs.
Glider pilot's aphorism: "there is no substitute for span". Retort: "There is a substitute: skill+imagination. But you can buy span".
Having fun doing more, with less
 

Offline brucehoult

  • Super Contributor
  • ***
  • Posts: 6398
  • Country: nz
Re: I get emacs, but WOW... the LISP learning curve ... and WHY LISP?
« Reply #27 on: October 26, 2022, 11:08:33 pm »
The big “win” in a DSL is if you can enable non-programmer domain experts to use it without them thinking they’re doing “programming”.

If it feels like programming, I tend to lean towards just giving the user the full power of the programming environment.

In a Lisp-like environment, there is no conflict between those two things. E.g. Scala with embedded Chisel DSL for chip circuit design, or Ruby with embedded Rails DSL for web site design.

You get the easy DSL, and you *also* have the full power of the programming language.
 

Offline sokoloff

  • Super Contributor
  • ***
  • Posts: 1803
  • Country: us
Re: I get emacs, but WOW... the LISP learning curve ... and WHY LISP?
« Reply #28 on: October 26, 2022, 11:12:15 pm »
Node-red has a few deployed use cases that I’d say are successful in allowing non-programmers to program things they couldn’t achieve in a text-based programming environment.
 

Offline westfw

  • Super Contributor
  • ***
  • Posts: 4639
  • Country: us
Re: I get emacs, but WOW... the LISP learning curve ... and WHY LISP?
« Reply #29 on: October 26, 2022, 11:29:34 pm »
Quote
I'm sure you remember why two of the most basic LISP functions are still CAR and CDR :)
Well, no.  I had to look it up.  I pretty much only go back to the PDP-10 era.
Those 36 bit machines with their 18bit address spaces were certainly convenient for LISP.  Byte-addressing, not so much :-(
 

Offline etiTopic starter

  • Super Contributor
  • ***
  • !
  • Posts: 1801
  • Country: gb
  • MOD: a.k.a Unlokia, glossywhite, iamwhoiam etc
Re: I get emacs, but WOW... the LISP learning curve ... and WHY LISP?
« Reply #30 on: October 26, 2022, 11:31:19 pm »
I'm now having a bash at "Racket", and wow, what a lovely dialect it is!
 

Offline tggzzz

  • Super Contributor
  • ***
  • Posts: 23122
  • Country: gb
  • Numbers, not adjectives
    • Having fun doing more, with less
Re: I get emacs, but WOW... the LISP learning curve ... and WHY LISP?
« Reply #31 on: October 26, 2022, 11:41:37 pm »
Quote
I'm sure you remember why two of the most basic LISP functions are still CAR and CDR :)
Well, no.  I had to look it up.  I pretty much only go back to the PDP-10 era.
Those 36 bit machines with their 18bit address spaces were certainly convenient for LISP.  Byte-addressing, not so much :-(

Luxury! I started on a 39-bit machine with a 13-bit address space :) (And a 576µs cycle time)
There are lies, damned lies, statistics - and ADC/DAC specs.
Glider pilot's aphorism: "there is no substitute for span". Retort: "There is a substitute: skill+imagination. But you can buy span".
Having fun doing more, with less
 


Share me

Digg  Facebook  SlashDot  Delicious  Technorati  Twitter  Google  Yahoo
Smf