3 ms·
> Examples: Clojure, Common Lisp, HTML, Make > Examples: UNIX, LISP, The Web, Emacs, TeX 1. Or just computer science. 2. Churn is not a problem. If you keep
by namelosw 7y ago
> Examples: Clojure, Common Lisp, HTML, Make
> Examples: UNIX, LISP, The Web, Emacs, TeX
1. Or just computer science.
2. Churn is not a problem. If you keep accepting the churn, you will learn them faster and faster, until you scan the doc and know most of the things, if it is churn. If it is not, it's something new (eg: Coq), then you have the ability to identify 'new but not churn', instead of just learning 'old and not churn' from a half-century ago (eg: Lisp).
3. Among the churns, there would be 'meta churn' like Haskell, Lisp, Erlang, and Rust. There are countless languages stealing Monad from Haskell, and Kubernetes patterns are very similar to Erlang OTP patterns.
4. Editors and IDEs are really irrelevant, I used Emacs a lot, I'm very fluent with Vi, but for some languages, I prefer Intellij and VSCode. Just use tools you feel productive.