REPL Driven Development

Table of Contents

1. REPL Driven Development

  • ↑ Faster feedback loop speeds up development
  • ↓ Hard to setup in some languages/environments (compiled languages, hardware devices)

1.2. Attempting REPL-Driven Development in Python

1.3. REPL Python programming and debugging with IPython   process

1.7. Marimo

1.9. I’m Re-Imagining the Command Line Interpreter - YouTube   process

1.9.2. Translate what you do in nix shell (imperative) to nix

1.14. scrapscript

Scrapscript is best understood through a few perspectives:

  • it’s JSON with types and functions and hashed references
  • it’s tiny Haskell with extreme syntactic consistency
  • it’s a language with a weird IPFS thing

Scrapscript solves the software sharability problem.

Modern software breaks at boundaries. APIs diverge, packages crumble, configs ossify, serialization corrupts, git tangles, dependencies break, documentation dies, vulnerabilities surface, etc.

1.14.1. scrapscript

1.20.

1.21. Static Types vs Dynamic Types

  • Statically and dynamically typed scripts

    For more than a decade I’ve preferred F# or Haskell for ad-hoc scripting. Note that while these languages are statically typed, they are low on ceremony. Types are inferred rather than declared. This means that for scripts, you can experiment with small code blocks, iteratively move closer to what you need, just as you would with a language like Python. Change a line of code, and the inferred type changes with it; there are no type declarations that you also need to fix.

Author: Julian Lopez Carballal

Created: 2024-09-16 Mon 06:15