toreib.blogg.se

Runjs
Runjs















I can imagine that, at the time, this sort of interactive/live visual environment was revolutionary. The rest of it is "interesting" I suppose. The bit towards the end (around 5 min mark I believe) where he gives the IDE (is that what you call it?) an input + output and asks it what message would produce the result he wants is pretty damn cool. I watched the whole video, thank you for sharing!

#Runjs code

  • Show HN: Sunflower Editor – like adding console.log to every line of your code.
  • You need to manually trigger "cells", which return a single value/visualization, or add a bunch of print statements. Notebooks are also a worse experience for the same reason. Using an actual REPL sucks compared to being able to regularly edit a file in your editor and get all of this + more without being handicapped to a terminal buffer. This allows me to use an entire file as a visual REPL with instant feedback. In VS Code, I can use extensions to show realtime values next to every line of my program, and indicators of whether a branch/code path was ever hit. This is fine if you live in an age before graphical editors, but today we have tools with a better REPL-like experience. In a REPL, you're given a buffer to enter text into, and it evaluates it as you submit this buffer. I hear this amazement and fascination with REPL's that people have and I don't understand.
  • Any developer tools/subscriptions/packages that are worth buying paid/pro plan?.
  • Without you having to go to an external context like a debug window to see the bindings. Effectively animating the flow of data through your code. In fact, since a program is about binding values to the symbols in your code, when running your code, the IDE, enabled by the content-addressable code feature), could replace variables in the text with their bound values, successively. The REPL-driven development approach should ideally afford simply changing code in the code editor, detecting the change, and showing the result then and there, without you having to go to back-and-forth to a separate REPL-shell and copy-pasting / retyping code. But with the ability to see the content of the data structures within your IDE. Especially good for debugging: getting the exact program state from loading up an image of it that someone sent you. Some have described this as REPL-driven-development, or interactive-programming. But without being a whole isolated universe in its own right like a VM or an isolated image.

    runjs

    So the language should make such visualization and code-augmentation easy for tooling to support.

    runjs

    It shouldn't be necessary for the programmer to take the effort to visualize it in his mind (with the error-proneness that entails).

    runjs

    Since "An algorithm has to be seen to be believed", as D.E. Also, it should be possible to visualise/animate an algorithm. Ideally with example data, not only the data type. Structure he/she is working on, at any given time, in the code. Programmer should always be able to see the data No need to manipulate data structures in the human mind.















    Runjs