I greped for "core", "memory manager", "thread", "threading", and "cache", in the pdf [1]. Am I missing something? I'll probably get flak for this, but this programmer looks for a modern systems language that directly addresses these concerns. "The fundamental problems of a systems-programming task or environment are hard limits on computational resources and a lack of safety protections. Systems programs have to dea…
One of the examples in the repository is an implementation of malloc. I tend to think of Go as an attempt to redefine what a systems programming language is (hence the "modern"). I don't think that there can be an established definition of what a modern systems language is, otherwise it would no longer be termed modern. Almost by definition theorists will differ on what the essential characteristics must be.
Right. And (imho) malloc is quite possibly an "old fashioned" way of looking at things:
function malloc(num_bytes: nat): @byte
> I don't think that there can be an established definition of [a] modern systems language
Key word is "modern" so here is an attempt to box that a bit: There are 2 possible dimensions to the notion of modern:
1 - it addresses new hardware realities
2 - it enables "progress" in dealing with matter rendered difficult by existing paradigms of system programming.
The realities of a modern system surely include: multi-core SMP; strong likelihood to be employed as distributed nodes; virtualization. So "modern" platforms and deployment patterns are not addressed.
Second, Deca, I gather, would delegate dealing with all this to some higher level (user level) framework built on top of the language. I don't see any progress in that critical front, either.