Racket: Why I Think It’s a Great Language, and Why I’m Not Using It Anymore
Channel:Leandro Facchinetti · Length:8:45 · Published:2021-01-03 · Views:19285
Summary
Leandro Facchinetti explains why he thinks Racket is a great language and why he stopped using it. He describes his backstory and experiences with the Racket community.
Why HN recommends it
Mostly cited critically, as evidence of problems in the Racket community, rather than recommended.
Programming language design · Functional programming · Software practice, open source & careers
Subtitles (excerpt)
hi my name is lender fakinetti and in this video i want to talk to you about a programming language called racket why i think it's a great language and why i'm not using it anymore first to counter my admittedly clickbaity title i want to give you a summary i used to use racket almost exclusively for a couple of years a few years ago and i think it's a great language probably the best designed language i have ever seen it allows you to express ideas about code in a way that is clear and precise and compact but i'm not using it anymore because i no longer buy into its premise which is something called language oriented programming i just think that maybe racket is too out there it's too different for you to be able to communicate effectively with other programmers also unfortunately i had some bad experiences with people in the record community especially people up top who help design and build the language and help shape its community but more on that later let's begin with some backstory i first heard about racket when i was a phd student i was interested in typography and then this colleague which was also a phd student said hey you should read this book it's called practical typography and i think you will
On Hacker News
You're probably thinking about this video: [VIDEO] Leandro submitted it to HN but it didn't get any traction: [LINK] — jboynyc, 2021-06
The bottom line is: 1) DrRacket consumes 0.7 GB od RAM for very little functionality, in comparison to Visual Studio 2) The performace was even worse but than Racket core team switched to excelent Chez scheme, being unable to produce such a quality compiler 3) If by any chance DrRacket was written in C, it would consume 300Kb of max memory, considering how little functionality this `development e… — dytyramb, 2022-06
There are some very valid reasons [1] why we should stay away from Racket: toxic community, toxic people... And come on: no one has ever really used Racket to write some decent nontrivial web application, documentation is awful (and, please, don't count HN here, cause HN is written in Arc). [1] [VIDEO] — dermal, 2021-05
There are some people who completely gave up of Racket just because of him (take a look of this video: [VIDEO] ). And, speaking of ego, just take a look at the author list on the cover of this book: [LINK] Notice the font size of his name, versus the font size of the students who actually wrote the book and everything will be clear to you! — wsylex, 2021-03
I think using Racket should be avoided because of its problematic community. I've had disgusting experiences interacting with people from Racket community in the past, but so far I thought I was the only one. Unfortunately, it doesn't seem that way. Recently, a computer Scientist Leandro Facchinetti described in his video his ugly experiences with top people in Racket community. The experience wa… — yaleL, 2021-02
Related videos
- Ruby Conf 12 - Y Not- Adventures in Functional Programming by Jim Weirich · Confreaks · 53:21
- How Python was Shaped by leaky Internals, Armin Ronacher, Flask framework · Видео с мероприятий {speach! · 49:55
- 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
- 🚀 TDD, Where Did It All Go Wrong (Ian Cooper) · DevTernity Conference · 1:03:55
- 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
- Conway's Game Of Life in APL · Dyalog · 7:47
- Lecture 1A | MIT 6.001 Structure and Interpretation, 1986 · MIT OpenCourseWare · 1:12:55
- Crockford on JavaScript - Volume 1: The Early Years · YUI Library · 1:42:08