logo

drewdevault.com

[mirror] blog and personal website of Drew DeVault git clone https://hacktivis.me/git/mirror/drewdevault.com.git

A-new-systems-language.md (4724B)

    

  1. ---
  2. title: We are building a new systems programming language
  3. date: 2021-03-19
  4. formats: [html, gemtext]
  5. ---
  7. It's an open secret: the "secret project" I've been talking about is a new
  8. systems programming language. It's been underway since December '19, and we hope
  9. to release the first version in early 2022. The language is pretty small —
  10. we have a mostly complete specification which clocks in at 60 pages. It has
  11. manual memory management, no runtime, and it uses a superset of the C ABI,
  12. making it easy to link with libraries and C code. It should be suitable almost
  13. anywhere C is useful: compilers, system utilities, operating systems, network
  14. servers and clients, and so on.
  16. <!--
  17. Hello, clever reader :) I was too lazy to make a dedicated build of Hugo with a
  18. fake name for the language. Since you bothered to check, head to
  19. https://harelang.org for the rest of the details. Please keep it to yourself!
  20. -->
  21. ```hare
  22. use io;
  24. export fn main() void = {
  25. 	const greetings = [
  26. 		"Hello, world!",
  27. 		"¡Hola Mundo!",
  28. 		"Γειά σου Κόσμε!",
  29. 		"Привет мир!",
  30. 		"こんにちは世界！",
  31. 	];
  32. 	for (let i = 0z; i < len(greetings); i += 1) {
  33. 		io::println(greetings[i]);
  34. 	};
  35. };
  36. ```
  38. We could compare our language to many other languages, but let's start with how
  39. it compares to C:
  41. - More robust error handling via tagged unions
  42. - Improved, Unicode-aware string support
  43. - Memory safe array, slice, and pointer types (and unsafe versions, if needed)
  44. - Direct compatibility with the C ABI for trivial C interop
  45. - A simpler, context-free, expression-oriented syntax
  46. - A standard library free of the constraints of POSIX or the C standard
  48. Our language currently supports Linux on x86_64 or aarch64, and we plan on
  49. expanding this to the BSDs, Haiku, and Plan 9; as well as i686, riscv64 and
  50. riscv32, and ppc64 before the release.
  52. I plan to continue keeping the other details a secret until the release &mdash;
  53. we want the first release to be a complete, stable, production-ready programming
  54. language with all of the trimmings. The first time most people will hear about
  55. this language will also be the first time they can ship working code with it.
  57. However, if you want to get involved sooner, there's a way: we need your help.
  58. So far, we've written most of the spec, the first of two compilers, and about
  59. 15,000 lines of the standard library. The standard library is what needs the
  60. most help, and I'm seeking volunteers to get involved.
  62. The standard library mandate begins with the following:
  64. > The <span style="color: transparent">xxxx</span> standard library shall provide:
  65. >
  66. > 1. Useful features to complement <span style="color: transparent">xxxx</span> language features
  67. > 2. An interface to the host operating system
  68. > 3. Implementations of broadly useful algorithms
  69. > 4. Implementations of broadly useful formats and protocols
  70. > 5. Introspective meta-features for <span style="color: transparent">xxxx</span>-aware programs
  71. >
  72. > Each of these services shall:
  73. >
  74. > 1. Have a concise and straightforward interface
  75. > 2. Correctly and completely implement the useful subset of the required behavior
  76. > 3. Provide complete documentation for each exported symbol
  77. > 4. Be sufficiently tested to provide confidence in the implementation
  79. We have a number of focus areas for standard library development. I expect most
  80. contributors, at least at first, to stick to one or two of these areas. The
  81. focus areas we're looking into now are:
  83. <dl>
  84.   <dt>Algorithms</dt>
  85.   <dd>Sorting • compression • math • etc</dd>
  87.   <dt>Cryptography</dt>
  88.   <dd>Hashing • encryption • key derivation • TLS • etc</dd>
  90.   <dt>Date & time support</dt>
  91.   <dd>Parsing • formatting • arithmetic • timers • etc</dd>
  93.   <dt>Debugging tools</dt>
  94.   <dd>ELF and DWARF support • vDSO • dynamic loading • etc</dd>
  96.   <dt>Formats & encodings</dt>
  97.   <dd>JSON • XML • HTML • MIME • RFC 2822 • tar • etc</dd>
  99.   <dt><span style="color: transparent">xxxx</span> language support</dt>
  100.   <dd>Parsing • type checker • hosted toolchain • etc</dd>
  102.   <dt>Networking</dt>
  103.   <dd>IP & CIDR handling • sockets • DNS resolver • HTTP • etc</dd>
  105.   <dt>Platform support</dt>
  106.   <dd>New platforms and architectures • OS-specific features</dd>
  108.   <dt>String manipulation</dt>
  109.   <dd>Search, replace • Unicode • Regex • etc</dd>
  111.   <dt>Unix support</dt>
  112.   <dd>chmod • mkfifo • passwd • setuid • TTY management • etc</dd>
  113. </dl>
  115. If any of this sounds up your alley, we'd love your help! Please [write me an
  116. email](mailto:sir@cmpwn.com) describing your interest areas and previous systems
  117. programming experience.
  119. **Update 2021-03-20**: We're targeting the first release in early 2022, not 2021.