From b0c78b80cf1479d3b52958bbf8305b188ae165bf Mon Sep 17 00:00:00 2001 From: Mitchell Vitez Date: Fri, 25 Nov 2016 16:59:22 -0500 Subject: [PATCH] Fix broken link --- src/pages/blog/announce/repl.elm | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/pages/blog/announce/repl.elm b/src/pages/blog/announce/repl.elm index 02bf7a25c..d87fc78dc 100644 --- a/src/pages/blog/announce/repl.elm +++ b/src/pages/blog/announce/repl.elm @@ -123,7 +123,7 @@ into existing codebases. That is all great, but for some reason we still had folks on [the list][repl-request] asking for a good old fashioned [Read-eval-print-loop](http://en.wikipedia.org/wiki/Read%E2%80%93eval%E2%80%93print_loop). My initial feeling was “Don't you see! -[REPLs are so 2000 and late](http://vimeo.com/46555107#t=0m47s)” +[REPLs are so 2000 and late](https://youtu.be/4m48GqaOz90?t=54)” but I was missing the bigger picture. When it comes to exploring functions deep inside a large codebase, a REPL is