|
14
|
1
|
{{{header(hello world, |
|
|
2
|
Richard Westhaver, |
|
|
3
|
ellis@rwest.io, |
|
|
4
|
Introducing The Compiler Company)}}} |
|
12
|
5
|
If we've spoken recently I may have mentioned this new venture I've |
|
|
6
|
been working on. Now is the time to elaborate on what I've been up to, |
|
|
7
|
and why. |
|
10
|
8
|
|
|
|
9
|
* The Compiler Company |
|
|
10
|
The name is a play on the phrase /Compiler Collection/, as in [[https://gcc.gnu.org/][GNU |
|
|
11
|
Compiler Collection (GCC)]] and emphasizes my approach to |
|
|
12
|
problem-solving involving compiler technologies. |
|
|
13
|
|
|
|
14
|
I recently registered as an LLC, but the purpose of the company is |
|
12
|
15
|
that of a company incubator, or /company compiler/ if you will. In |
|
|
16
|
other words, I intend for /The Compiler Company, LLC/ to be a hub for |
|
10
|
17
|
developing various interconnected products and services which can be |
|
|
18
|
operated and managed independently of each other. |
|
9
|
19
|
|
|
12
|
20
|
I (Richard Westhaver) am the sole owner and operator and will probably |
|
|
21
|
keep it that way for quite some time. My intention is to operate at |
|
|
22
|
minimal cost while I perform industry research and develop prototypes. |
|
|
23
|
|
|
13
|
24
|
To support the company's purpose, I am developing a suite of free and |
|
|
25
|
open-source software which is specifically designed for bootstrapping |
|
|
26
|
and operating =companies=. |
|
12
|
27
|
|
|
13
|
28
|
** Software |
|
|
29
|
|
|
|
30
|
The software provided by /The Compiler Company/ is a powerful |
|
|
31
|
development environment. It is the catalyst of engineering for every |
|
|
32
|
other software component I build and reflects precisely how I believe |
|
|
33
|
software should be developed. |
|
12
|
34
|
|
|
13
|
35
|
As a whole, I optimize for the following features in my environment: |
|
|
36
|
- early adoption :: integrate research, protocols, libraries, and |
|
|
37
|
hardware features from leading research orgs faster than anyone else |
|
|
38
|
- rapid development :: interaction, code introspection, tooling, and |
|
|
39
|
automation built for prototyping at massive scale |
|
|
40
|
- power :: using our environment should feel like cheating - macros, |
|
|
41
|
DSLs, and unmatched hackability |
|
10
|
42
|
|
|
13
|
43
|
*** Languages |
|
|
44
|
/The Compiler Company/ is above all, a =Lisp Company=. The most |
|
|
45
|
powerful software requires the most powerful language. |
|
10
|
46
|
|
|
13
|
47
|
Lisp isn't enough though. =Rust= is our imperative language of choice |
|
|
48
|
at the time of writing and generally suited for system-level software |
|
|
49
|
components. |
|
|
50
|
|
|
|
51
|
We make use of the Steel Bank Common Lisp compiler (SBCL) and the |
|
|
52
|
nightly Rust compiler toolchain. |
|
|
53
|
|
|
|
54
|
*** Operating System Support |
|
|
55
|
/The Compiler Company/ is a Linux Company. There may be minimal |
|
|
56
|
support for Darwin-based systems, but Microsoft Windows systems will |
|
|
57
|
never be supported by our software. |
|
10
|
58
|
|
|
13
|
59
|
One of the /anti-goals/ of our software is ~portability~. For all of |
|
|
60
|
the features we optimize for, portability becomes a burden, especially |
|
|
61
|
with closed-source OS kernels. We are also explicitly driven to reduce |
|
|
62
|
consumer dependence on these closed-source systems, especially in a |
|
|
63
|
distributed network. They are simply unfit for use with the software |
|
|
64
|
we produce. |
|
10
|
65
|
|
|
13
|
66
|
*** Core |
|
|
67
|
** Services |
|
|
68
|
|
|
|
69
|
** Companies |
|
9
|
70
|
* Next Steps |
|
11
|
71
|
We have a long way to go. The important thing is to keep up the |
|
|
72
|
momentum. Before the start of 2024 you can expect another update on |
|
|
73
|
some of the projects below. |
|
|
74
|
** the.compiler.company |
|
|
75
|
** infra |
|
|
76
|
** core |
|
|
77
|
** nas-t |
