> It's bad because it means C keeps getting faster, so people keep writing C code. May I know why? Isn't compilation already at most optimal point?
-
-
-
that would imply they’ve solved P=NP. compilers are always going to have room for improvement
- 1 more reply
New conversation -
-
-
Just use
#rustlangThanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
Is your argument c=bad? I don’t get it
- 11 more replies
New conversation -
-
-
If ever there was a job for AI as it exists today, it’s writing the compiler for a specific chip
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
Should people not be writing c?
-
People should write Rust instead of C.
End of conversation
New conversation -
-
-
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
are there actually people starting new C projects outside of niche / embedded / legacy situations? I'm really interested in how this has a larger impact than silently and suddenly breaking the security of decades old code bases.
-
Yes, quite a few. Remember there's only a few languages you can write self-contained libraries in, that can be consumed elsewhere.
- 3 more replies
New conversation -
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.