From db6d6a6ddb614d7be25a00966602ce0b73d99b4c Mon Sep 17 00:00:00 2001 From: "Mario T. Lanza" Date: Tue, 28 May 2024 11:06:54 -0400 Subject: [PATCH] edit copy --- adopting-the-clojure-mindset.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/adopting-the-clojure-mindset.md b/adopting-the-clojure-mindset.md index 78d8fa19..6f480112 100644 --- a/adopting-the-clojure-mindset.md +++ b/adopting-the-clojure-mindset.md @@ -1,8 +1,8 @@ # Adopting The Clojure Mindset -Most languages have reference types and value types, mutables and immutables. JavaScript is no different, but it suffers gaps when it comes to value types. It has only the basics, like strings and numbers but in recognizing the deficit aims to fill some of its gaps—[records and tuples](https://github.com/tc39/proposal-record-tuple) and [temporals](https://github.com/tc39/proposal-temporal). +Most languages have reference types and value types, mutables and immutables. JavaScript is no different, but has gaps in its value types (e.g. [records and tuples](https://github.com/tc39/proposal-record-tuple) and [temporals](https://github.com/tc39/proposal-temporal)). -Understand, however, while functional programming does better when a robust set of value types are present, it's not seriously hindered when they're not. It can treat reference types as value types. +And while functional programming does better when a robust set of value types are present, it's not seriously hindered when they're not. It can treat reference types as value types. Briefly, recall that command-query separation wants query functions to return a value but not command functions. The stark absence of a return value calls it out as a command.