> Obviously not

Is it obvious? I haven't heard of new projects in non-memory-safe languages lately, and I would think they would struggle to attract contributors.

▲

jandrewrogers 4 hours ago | parent | next [-]

New high-scale data infrastructure projects I am aware of mostly seem to be C++ (often C++20). A bit of Rust, which I’ve used, and Zig but most of the hardcore stuff is still done in C++ and will be for the foreseeable future.

It is easy to forget that the state-of-the-art implementations of a lot of systems software is not open source. They don’t struggle to attract contributors because of language choices, being on the bleeding edge of computer science is selling point enough.

▲

ACCount37 2 hours ago | parent [-]

There's a "point of no return" when you start to struggle to hire anyone on your teams because no one knows the language and no one is willing to learn. But C++ is very far from it.

	▲	pornel 32 minutes ago \| parent [-]
		There's always someone willing to write COBOL for the right premium. I'm working on Rust projects, so I may have incomplete picture, but I'm from what I see when devs have a choice, they prefer working with Rust over C++ (if not due to the language, at least due to the build tooling).

▲

pjmlp 2 hours ago | parent | prev | next [-]

Game development, graphics and VFX industry, AI tooling infrastructure, embedded development, Maker tools like Arduino and ESP32, compiler development.

▲

ottah 6 hours ago | parent | prev | next [-]

https://github.com/tigerbeetle/tigerbeetle

▲

lmm 6 hours ago | parent [-]

Zig at least claims some level of memory safety in their marketing. How real that is I don't know.

▲

vlovich123 4 hours ago | parent | next [-]

About as real as claiming that C/C++ is memory safe because of sanitizers IMHO.

	▲	Ygg2 32 minutes ago \| parent [-]
		I mean, Zig does have non-null pointers. It prevents some UB. Just not all.

▲

gjajric 2 hours ago | parent | prev | next [-]

I have heard different arguments, such as https://zackoverflow.dev/writing/unsafe-rust-vs-zig/ .

▲

tomnipotent 3 hours ago | parent | prev [-]

I'm unaware of any such marketing.

▲

dwattttt 3 hours ago | parent [-]

Zig does claim that it

> ... has a debug allocator that maintains memory safety in the face of use-after-free and double-free

which is probably true (in that it's not possible to violate memory safety on the debug allocator, although it's still a strong claim). But beyond that there isn't really any current marketing for Zig claiming safety, beyond a heading in an overview of "Performance and Safety: Choose Two".

	▲	tomnipotent 2 hours ago \| parent [-]
		That's a library feature (not intended for release builds), not a language feature.

▲

mmooss 6 hours ago | parent | prev [-]

Out of curiosity, do the LLMs all use memory safe languages?

▲

lmm 6 hours ago | parent | next [-]

Whenever the public has heard about the language it's always been Python.

	▲	chasil 4 hours ago \| parent \| next [-]
		The language that implements Python's high-speed floating point has often been FORTRAN. https://fortranwiki.org/fortran/show/Python
	▲	pjmlp 2 hours ago \| parent \| prev [-]
		With lots of CUDA C++ libraries, among others.

▲

einr 4 hours ago | parent | prev [-]

Llama.cpp is called Llama.cpp, so there’s that…