> static types often reduce to a bunch of optionals, forcing you to null check every field
On one end, you write / generate / assume a deserialisator that checks whether incoming data satisfies all required invariants, eg all fields are present. On the other end, you specify a type that has all the required fields in required format.
If deserialisation fails to satisfy type requirements, it produces an error which you can handle by eg falling back to a different type, rejecting operation or re-requesting data.
If deserialisation doesn't fail – hooray, now you don't have to worry about uncertainty.
The important thing here is that uncertainty is contained in a very specific place. It's an uncertainty barrier, if you wish: before it there's raw data, after it it's either an error or valid data.
If you don't have a strict barrier like that – every place in the program has to deal with uncertainty.
So it's not necessarily about dynamic / static. It's about being able to set barriers that narrow down uncertainty, and growing number of assumptions. The good thing about ergonomic typing system is that it allows you to offload these assumptions from your mind by encoding them in the types and let compiler worry about it.
It's basically automatization of assumptions book keeping.
I know everyone says that this is a huge issue, and I am sure you can point to an example, but I haven’t found that types prevented a lot of issues like this any better than something like Erlang’s assertion-based system.
Where does the stereotype 'thesaurus = synonyms + antonyms' come from?
I'm not a native english speaker, and I never heard that idea besides in, I'd guess, Friends TV show.
I've used thesauruses since my childhood for exactly the task of looking up meanings, explanations, perhaps some etymology baked in.
For English, I always use WordNet, it is quite good and works offline on Android.
For my basic level of Chinese, Outliers dictionaries are so far the best I have found, but that's mainly due to my heavy reliance on the etymology provided there.
Well, I guess I got carried away a bit. Back to my question, where thesaurus=synonyms+antonyms comes from?
It's very unusual for a thesaurus to contain meanings (beyond the category head/name) and etymology, let alone explanation. Such things are usually found in a dictionary instead.
So it's more a question for you: where did your unusual idea of "thesaurus" come from? As one of your examples you mention dictionaries, so that's especially confusing.
The word comes from Greek, θησαυρός - "a store, treasure, storehouse, treasury".
> The usage of "thesaurus" in English for a kind of book dates back to the first one by Peter Mark Roget in 1852
To nitpick, though of interest: The usage meaning a book of words organized by their senses indeed dates to Roget's use in 1852, as the parent comment says. An earlier usage is more generally a 'treasury' of knowledge (in book form): there was a Thesaurus Linguæ Romanæ et Britannicæ ... in 1565, a Thesaurus Linguæ Latinæ compendiarius ... in 1736, and John Stuart Mill in 1840 wrote about "A thesaurus of commonplaces for the discussion of questions."
I did in fact look at Etymonline for "thesaurus" before I made my comment and therefore chose my words carefully, but not clearly enough. Yes there were books before Roget's that contained the word “thesaurus” (treasury) in their title, including at least one dictionary. But none of these earlier books caused the word “thesaurus” to start to mean a particular kind of book, which it does in English following Roget — and that kind of book is precisely one that contains synonyms and antonyms, and usually does not contain meanings or etymology. So the comment by folex remains weird — for one thing, it uses “stereotype” where “meaning” would be more appropriate.
> Yes there were books before Roget's that contained the word “thesaurus” (treasury) in their title, including at least one dictionary. But none of these earlier books caused the word “thesaurus” to start to mean a particular kind of book ...
FWIW, OED has a separate sense for, "A ‘treasury’ or ‘storehouse’ of knowledge, as a dictionary, encyclopædia, or the like." Is that a particular kind of book or a general concept? I don't know.
Its usage extends past Roget - e.g., (1862) "In a complete thesaurus of any language, the etymology of every word should exhibit both its philology and its linguistics." and (1906) "This work is one of five thesauri published under the auspices of Kang Hsi, the second Emperor of the present dynasty."
And to be complete, a newer usage dates to 1957, "A classified list of terms, esp. key-words, in a particular field, for use in indexing and information retrieval.".
> I did in fact look at Etymonline
Etymonline is the admiral work of one person. If you can get access to the OED (and if you love etymology, etc., it's essential), you'll generally find much more, and much more reliable work done by teams of professional over ~150 years.
Etymonline's About page is incredible - I'm going to submit it:
> the comment by folex remains weird — for one thing, it uses “stereotype” where “meaning” would be more appropriate.
Not weird at all - folex says they don't speak English natively. Stereotype makes sense in a way, but is not the word a native speaker would choose. I'm the same in some languages.
folex's question is maybe the most interesting part of the discussion.
I'd assume from the earlier meaning of "thesaurus" which comes from "treasury," or as it exists in my mind, treasure chest.
> The meaning "encyclopedia filled with information" is from 1840, but it existed earlier as thesaurarie (1590s), used as a title by some early dictionary compilers, on the notion of thesaurus verborum "a treasury of words." The meaning "collection of words arranged according to sense" is attested from 1852 in Roget's title.
I'm not sure stereotype is the correct word here. But even setting that aside, a thesaurus being a referential work containing words grouped by similarity is the CONVENTIONAL definition.
Everyone of my friends and family had one growing up. It wasn't completely uncommon as a young child to glaze your eyes "beautiful mind style" to suss out repetitious or excessive duplicate word usage in your hastily prepared 5-paragraph MLA format essay and then run it through the nearest Merriam-Webster thesaurus.
However, I'd recommend Murderbot series, it is full of humour and shares atmosphere of Bobiverse and this personal approach to characters, as well. Highly recommend.
I am not a native speaker of English so maybe that's why. Typically anything that has lots of humor and makes the reader laugh or be amused frequently -- I think of as comedy. Is there a more nuanced distinction to what is usually called a comedy in literature / movies?
I tried to think of some other examples. Trevor Noah's biography 'Born A Crime' came to mind. I would not explicitly describe it as a comedy myself - because a 'biography' is descriptive enough as well as non-fiction by definition so any humor is mostly not made up. If it were not a biography through -- it would probably go into the comedy bucket in my mind. Maybe I am just mis applying terms here.
Yes, Bobiverse and Murderbot are very close in spirit, and if you like one you are very likely to enjoy the other. Also both have great audio narration.
This is what I am missing as well. I'm a pre-sales technical architect that keeps looking for use-cases where I am able to leverage this technology. 75% of my work is in draw.io and PowerPoint.
That use case is very LLM unfriendly, because you want very specific and precise structure of output, but the LLM knows lots of stuff that is absolutely not what you want at all.
On one end, you write / generate / assume a deserialisator that checks whether incoming data satisfies all required invariants, eg all fields are present. On the other end, you specify a type that has all the required fields in required format.
If deserialisation fails to satisfy type requirements, it produces an error which you can handle by eg falling back to a different type, rejecting operation or re-requesting data.
If deserialisation doesn't fail – hooray, now you don't have to worry about uncertainty.
The important thing here is that uncertainty is contained in a very specific place. It's an uncertainty barrier, if you wish: before it there's raw data, after it it's either an error or valid data.
If you don't have a strict barrier like that – every place in the program has to deal with uncertainty.
So it's not necessarily about dynamic / static. It's about being able to set barriers that narrow down uncertainty, and growing number of assumptions. The good thing about ergonomic typing system is that it allows you to offload these assumptions from your mind by encoding them in the types and let compiler worry about it.
It's basically automatization of assumptions book keeping.
reply