21–30 of 202 posts
car and cdr are accessors for the fields of a basic data-structure; nothing academic about that. The very origin of the names is rooted in systems work, not academics.
(caddr x) provides a shorthand for (car (cdr (cdr x))), which is a pragmatic thing.
You know, like #(* % %) instead of (lambda (x) (* x x)).
> I saw the CARs and CDRs and CADDADDRs and thought it was all just academic baloney; interesting but not truly useful. car and cdr are accessors for the fields of a basic data-structure; nothing academic about that. The very origin of the names is rooted in systems work, not academics. (caddr x) provides a shorthand for (car (cdr (cdr x))), which is a pragmatic thing. You know, like #(* % %) instead of (lambda (x) (…
Can someone explain me why they always (OK let's say almost always) use math formulas to show what you can do with a programming language ? I'm a desktop application programmer, not a mathematician. I don't need to print the first 25 squares of integers or Fibonacci whatever. In fact I think the hardest math I did at work was using modulo to get even and odd numbers ... Show me how you parse a csv file, how do you co…
Extracting two columns out of a excel sheet: (->> (d/load-workbook file "Questionnaire.xlsx") (d/select-sheet "Sheet1") (d/select-columns {:A :item :B :price}))
How do you manage errors? What happens if Questionnaire.xlsx or Sheet1 doesn't exist ?
> I saw the CARs and CDRs and CADDADDRs and thought it was all just academic baloney; interesting but not truly useful. car and cdr are accessors for the fields of a basic data-structure; nothing academic about that. The very origin of the names is rooted in systems work, not academics. (caddr x) provides a shorthand for (car (cdr (cdr x))), which is a pragmatic thing. You know, like #(* % %) instead of (lambda (x) (…
i thought CAR and CDR were named after IBM (?) assembly language on an old machine. https://en.wikipedia.org/wiki/CAR_and_CDR
The most annoying phrase was "less code, less time, less...". Uncle Bob thought us to be explicit, help the reader understand the code and be verbose with the variables etc. Now he loves a Syntax that says #(25 % %)... Aaaalright, try to get a new company member understand a big code base with this massive oneliners. I doubt that this is the right language for enterprise projects.
So it's ok to say #(25 % %) because we both speak the same language and we know what it means, the intent is clear.
But it's not okay to call your variables a, b, c, because that's meaning, not syntax, and I can't understand your intent from those variables.
Massive one-liners probably fall into the latter, but I don't think he's advocating those.
Earlier quoted context omitted.
It's an alias given to an imported module name. In Python it might be: import really_long_name as rln rln.foo()
I know that part :) What module is it referencing?
Can someone explain me why they always (OK let's say almost always) use math formulas to show what you can do with a programming language ? I'm a desktop application programmer, not a mathematician. I don't need to print the first 25 squares of integers or Fibonacci whatever. In fact I think the hardest math I did at work was using modulo to get even and odd numbers ... Show me how you parse a csv file, how do you co…
Can anyone give a pro/cons analysis of a ML variant versus of a Lisp variant. Let's say F# versus Clojure? One of the general arguments in Lisp vs the world is that lisp is more concise. F# is really concise. It has datastructures as intrinsic part of the language syntax (just like Clojure, i.e in F# [|,,,|] is an array and in Clojure [...] is a vector, so more or less the same thing). Furthermore, the type inference…