News for hackers. Stuff that matters.
Re:Survey results: ISO C++ feature proposals by jandrewrogers on Friday July 26, 2019 @12:03PM (#20535791)
Almost none of those are systems programming languages, which was the domain of comparison.
Re:Survey results: ISO C++ feature proposals by nestorD on Friday July 26, 2019 @01:21PM (#20536421)
Rust with its macro system and explicit target of system programming seem like a perfect fit.
Re:Survey results: ISO C++ feature proposals by banachtarski on Friday July 26, 2019 @02:40PM (#20537246)
Rust is beyond even current C++ with respect to compile time code.
Re:Survey results: ISO C++ feature proposals by comex on Friday July 26, 2019 @04:10PM (#20537971)
Sort of. Rust procedural macros are powerful, but they’re basically glorified code generation: they take a list of tokens as input and return a list of tokens as output. They don’t have access to type information. For that you need to use a combination of the trait system and `const fn`, to which the C++ equivalent is templates and `constexpr`. But C++ `constexpr` is currently way ahead of Rust `const fn` in functionality. And while Rust’s trait system tends to be nicer than C++’s templates for most purposes, it’s not as good at performing arbitrary computations. Overall, when I use either language I find myself badly missing features from the other. I look forward to seeing both close the gap…
Re:Survey results: ISO C++ feature proposals by pjmlp on Friday July 26, 2019 @12:58PM (#20536247)
Common Lisp (Lisp Machines), D, Nim, OCaml (MirageOS Unikernel, Docker macOS TCP/IP stack), Haskell (House OS and Galois bare metal deployments).
Re:Survey results: ISO C++ feature proposals by slaymaker1907 on Friday July 26, 2019 @01:52PM (#20536753)
Systems programming language is only a useful term if you define what systems you are talking about. Are you talking about creating an OS, highly performance micro services, distributed systems, etc.? Common Lisp would likely be a poor choice for an OS but would be great for some of those other types of systems.
Re:Survey results: ISO C++ feature proposals by jandrewrogers on Friday July 26, 2019 @03:27PM (#20537644)
I would say that the common feature of a systems language is that it is explicitly designed to enable direct control of hardware resources and -- very importantly -- operation scheduling by the programmer. A point I think is often overlooked is that some software architectures cannot be implemented correctly without this level of control, and for some applications those architectures are the only competent choice. Using a systems language should be driven by the requirements of application with respect to software architecture, and most applications don't have that requirement.

Some applications that are above the OS and device drivers, such as database engines, are clearly in the domain of systems applications because it is not possible to create a competent implementation without the control a systems language provides. Even for relatively abstract high-level software like distributed systems, strict control of scheduling is required for consistently robust throughput and behavior. Some key algorithms only work in real systems if resource management and concurrent operation sequencing is inexpensively deterministic. For some other applications, the only real benefit of a systems language would be for performance engineering purposes, which may not be a practical priority.

The "managed language" litmus test is quite good in my opinion, and almost definitional.