Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

C is an amazing language. If you want to integrate into another language via FFI you basically have 0 other options.

That being said, it’s too easy to do something wrong in C. The desire to use Rust isn’t because C is stale, rather it’s too hard to write C correctly.



"amazing language"

ye ye, sure it is

uses physical pathes instead of logical namespaces for includes

average code base could be summed in such a way: everything is fucking "int" or its cousin - such a great tool for system modeling!

basic concepts as for $current_year are still non-trivial in C - like strings

when opening non-trivial codebase my VS Code goes crazy.

Maybe I do have high standards after using C# for years, but holy shit, writing Rust is 10 times better experience for me than using C.


My desire to write Rust is for both reasons. C tooling is awful, the language offers insufficient abstraction capabilities, and, finally, is unsafe.


Rust and C++ both have C FFI boundaries that the compiler can inline across. What more do you want?


Well for one, I don’t want to add another language to my tool chain. Many languages can compile C directly. For instance in Swift or Go you can add C source files directly to your project and have them compile as part of your Swift or Go build. You can’t do that with Rust or C++.

C is the lingua franca of the software development world.


Er....




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: