The case against a C alternative

#106 · 🔥 217 · 💬 374 · one year ago · c3.handmade.network · lerno · 📷
Like several others I am writing an alternative to the C language. The C language is not just the language itself but all the developer tools developed for the language. Is the language even addressing the real pain points of C? It turns out that people don't always agree on what the pain points with C is. Worse, what if the language omits crucial features that are present in C? Features that C advanced programmers rely on? This risk is increased if the language designer hasn't used C a great deal but comes from C++, Java etc. If the language can't easily call - or be called - by C code, then anyone using the language will have to have to do extra work to do pretty much anything that is interfacing with outside code. The problem is that C have practically no checks, so any safety checks put into the competing language will have a runtime cost, which often is unacceptable. In the end, all that matters is whether using a language can produce more tangible value to developers than C for at least a large subset of what C is used for.
The case against a C alternative



Send Feedback | WebAssembly Version (beta)