"Frequently" Asked Questions

a.k.a. questions that the authors feel like answering



Q01: Why design another programming language?

It's true that there are too many programming languages in the world already. However, concurrency is one of the facets of programming language design that really can't be done in any other way. See, e.g., Threads Cannot be Implemented as a Library.

Q02: Why start with C?

C is no longer the dominant application programming language in lots of software domains. However, it has two properties that make it attractive for projects like this one:

Q03: Isn't it dumb to make a concurrent language that can't be run in parallel?

As discussed elsewhere on this site, interactivity and parallelism are very different topics. Part of the inspiration behind this project is that insisting on parallel execution is one of the ingredients that makes multithreaded programming so error-prone. There is really no reason to want interactivity and parallelism to be mushed together into a single language feature. One is for making software responsive to the real world, one is for speeding up CPU-bound algorithms. There is no reason to put the two in the same bucket.

Q04: Fine. Be a pedantic jerk. Parallelism and interactivity are different. I care about parallelism; what are you going to do for me?

For the time being, Charcoal doesn't have anything novel to offer on the parallelism front. My basic philosophy re: parallelism is that it should be done with processes instead of threads. Not sharing memory by default is a good way to avoid concurrency bugs. Maybe I'll work more on this problem elsewhere.

Q05: The world has existed happily with event handlers, threads, etc. for decades now; did anything change to create a demand for a new concurrency primitive?

I'm not sure. My sense is that with so much of the application development action going on in the web, mobile and embedded parts of the universe, there is genuinely more reactivity and interactivity compared to a decade or two ago. As circumstantial evidence, I point to all the experimentation with funky event handling and cooperative threading models going on in the "scripting" language space. In particular, my sense is that "regular Jane and Joe" developers are coming face-to-face with concurrency issues much more than in the past. I would love to know if anyone has actually studied these trends.

Q06: What is the endgame?

My ambition for Charcoal is Not that it become an independently successful programming language. It is a testbed for activities and that's it. I'm not using it to work on any other PL ideas. It is so closely related to C, that if the activities idea is wildly successful, it could be rolled into a future version of the C standard. Similarly, just about any other language under the sun could add activities.

Q07: Is there code available for this project?

Yes. My github name is benjaminy. Search for that and you should find the Charcoal repo. Be aware that the project is still in a very early and incomplete state.


Creative Commons License
Charcoal Programming Language by Benjamin Ylvisaker is licensed under a Creative Commons Attribution 4.0 International License