changelog shortlog graph tags branches changeset files revisions annotate raw help

Mercurial > org > docs / ulang.org

changeset 1: 087da4ed0df6
child: 7895e9b82917
author: ellis <ellis@rwest.io>
date: Wed, 01 Nov 2023 21:32:38 -0400
permissions: -rw-r--r--
description: ulang
1 #+TITLE: ulang
2 
3 This document defines a *U-Language* as described by the late great
4 Haskell Curry:
5 
6 #+begin_quote
7 Every investigation, including the present one, has to be communicated
8 from one person to another by means of language. It is expedient to
9 begin our study by calling attention to this obvious fact, by giving a
10 name to the language being used, and by being explicit about a few of
11 its features. We shall call the language being used the
12 U-Language. [...] There would be no point in calling attention to it,
13 if it were not for the fact that language is more intimately related
14 to our job than of most others.
15 #+end_quote
16 
17 There is a natural reader/writer relationship that exists in countless
18 places, but is rarely examined because it is rarely necessary. However
19 there is a wide array of significantly complex code and prose projects
20 out there which would benefit greatly from such an investigation.
21 
22 I would also like to humbly clarify on our interpretation of a *job*
23 as Curry puts it. We all have the same job really - to be curious, and
24 to solve problems. It is the *problems* I would like to shine a light
25 on, if just for a moment, because it's important. Just as Curry thinks
26 of languages, we can think of problems. There exists the *problem of
27 problems* which is the subject of our investigations. This *U-Problem*
28 is what we are solving for at all times. In this light, we can view
29 the *U-Language* as a means of bringing both the /reader/ and /writer/
30 as close as possible to the *U-Problem*.
31 
32 For convenience, our *U-Problem* is undecidable, but we model and
33 solve for it using /computers/, or more abstractly machines. Thus, our
34 *U-Language* helps bring the /reader/ and /writer/ closer to
35 our /machines/ as well as expedite communications.
36 
37 - /Why do we need a U-Language?/ ::
38  To bring both the /reader/ and /writer/ closer to our *U-Problem*.
39 - /What is our U-Problem?/ ::
40  Undecidable, but we use /computers/ as a model of the
41  *U-Problem*.
42 - /How do we solve our U-Problem?/ ::
43  With /computers/, by developing accurate models and finding optimal
44  solutions.
45 
46 * Key Words
47 * Abbrevs
48 * Conditionals
49 * Operators
50 * Expressions
51 * Links
52 * Timestamps
53 * Macros