Inspiring a future Clojure editor with forgotten Lisp UX - Shaun Lebron
Channel:ClojureTV · Length:35:31 · Published:2017-10-12 · Views:23438
Summary
Shaun Lebron surveys 50 years of Lisp editing history and forgotten innovations in structural editing. He argues future Clojure editors could learn from them, and covers ideas like Parinfer.
Why HN recommends it
HN cites it as a summary of known attempts at structural and Lisp editors.
The ones I'm familiar with are summarized in this talk — HN, 2019
Functional programming · Testing, debugging & developer tools · GUI, HCI & interface history
Subtitles (excerpt)
[Applause] hello my name is Sean I'm from Houston and I'm here to try to inspire you about what a future closure editor might look like by looking to the past particularly I want to look through the lens of the perception problem of parentheses I know that Ridge said in his previous talk that this is just a problem with programmers I'm I sort of agree with them but as somebody who comes from a design from a background of game design I feel like if there are experiences that can get people past that problem then it won't be a problem anymore and people will start understanding the value proposition of closure and lisps in general so I'm going to first talk about what that perception problem is then I'm going to talk about the history of what people have tried to do to solve this problem and then at the last half of the talk I'm just going to jump into a demo and show you guys what what tools that I've developed to try to to try to fix this problem this is a four dimensional tesseract it's conceptually simple but it's visually jarring right like how so what kind of experiences can we use to sort of learn this complicated thing and sort of get over our fear of that there these are scenes from games and
On Hacker News
Using a Lisp with Parinfer makes the parens automagic without taking away the benefits they provide. [LINK] [VIDEO] — AlexSolution, 2019-10
That's a great suggestion. Which attempts are you familiar with? The ones I'm familiar with are summarized in this talk: [VIDEO] — cellularmitosis, 2019-03
This is called 'projectional editing', an idea that to my knowledge goes back to the 60s. A projectional editor shows you both the original source code, and alternate representations (or, 'projections') of it. Given the right plugins and config, these alternate projections could happen to be more intuitive to grasp/edit than the original source code. One plugin could, for example, remove all the … — AriaMinaei, 2017-10
Related videos
- Ruby Conf 12 - Y Not- Adventures in Functional Programming by Jim Weirich · Confreaks · 53:21
- RailsConf 2014 - All the Little Things by Sandi Metz · Confreaks · 38:47
- The Soul of Erlang and Elixir • Sasa Juric • GOTO 2019 · GOTO Conferences · 42:02
- "Simple Made Easy" - Rich Hickey (2011) · Strange Loop Conference · 1:01:38
- "Making Impossible States Impossible" by Richard Feldman · elm-conf · 25:06
- William Byrd on "The Most Beautiful Program Ever Written" [PWL NYC] · PapersWeLove · 1:31:05
- "Testing Distributed Systems w/ Deterministic Simulation" by Will Wilson · Strange Loop Conference · 40:20
- 🚀 TDD, Where Did It All Go Wrong (Ian Cooper) · DevTernity Conference · 1:03:55
- Bret Victor - Inventing on Principle · Rui Oliveira · 54:20
- The Value of Values with Rich Hickey · InfoQ · 31:43
- Bret Victor The Future of Programming · Joey Reid · 32:55
- Why Isn't Functional Programming the Norm? – Richard Feldman · Metosin · 46:09
- Maybe Not - Rich Hickey · ClojureTV · 1:03:28
- Solving Problems the Clojure Way - Rafal Dittwald · Clojure/north · 1:02:26
- Lecture 1A: Overview and Introduction to Lisp · MIT OpenCourseWare · 1:12:55
- Debugging Under Fire: Keep your Head when Systems have Lost their Mind • Bryan Cantrill • GOTO 2017 · GOTO Conferences · 52:34