Almost every "safe" language is itself written in C though. That's the key; use C very minimally for the bottom layer, and then build on top of abstractions. Or write C like LISP; build an inner safe DSL, and then use that. That's been our approach.https://twitter.com/glyph/status/1120524418906824705 …
-
-
+1 to that. I think if I’m to restate my position, people should think _really_ carefully about starting new projects in C today. I think ericb@ had a good quip about the tooling gap and new systems catching up, but I can’t seem to recall what it was.
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.
rust and we've used it for our Firecracker VMM and other systems softwares. It's probably safer overall, but there's still a tooling gap in terms of code analysis, and we'll be maintaining C things for a long time to come.