Replies: 23 comments 3 replies
-
this is a bad suggestion |
Beta Was this translation helpful? Give feedback.
-
while rust might not look the best programming language it is very good compared to java and almost on par in performance with c. Any gains in speed with c will only happen if some expert works on the project. |
Beta Was this translation helpful? Give feedback.
-
C (:rocket:) is:
Therefore, this project needs to be written in C (:rocket:), as in its current state of using Rust, it is full of CVEs and memory leaks. Switching to C (:rocket:) will magically fix all these issues :rocket: |
Beta Was this translation helpful? Give feedback.
-
C is the most memory unsafe language that will ever exist because you control memory yourself and c programming takes a lot of time just make sure memory is being handled correctly. The main reason people use languages like C++ and Java is because you don't handle memory yourself the language does. |
Beta Was this translation helpful? Give feedback.
-
Also switching to c will not be magical. It will take like 3-4 months of progress to do that.Also many libraries that stevenaralla uses are in rust to write the project in c it would require rewriting those too. And while there maybe issues in rust those are going to be solved by their respective devs. If this project was written with C a lot of code might have security issues and other things b/c of poor coding that might not get identified for years. |
Beta Was this translation helpful? Give feedback.
-
Rewrite it in C (:rocket:) and rewrite the libraries in C (:rocket:). We can not let this unsafe Rust code loose! We're just letting the CVEs fly. C (:rocket:) is completely immune to CVEs as it is memory safe :rocket:. This project being written in Rust and not C (:rocket:) should be a CVE in and of itself! |
Beta Was this translation helpful? Give feedback.
-
Have you ever programmed anything in C? |
Beta Was this translation helpful? Give feedback.
-
Yes, I have programmed many things in C (:rocket:) It's completely memory safe (:rocket:), secure (:rocket:), minimal (:rocket:), configurable (:rocket:) and fast (:rocket:)! |
Beta Was this translation helpful? Give feedback.
-
write in c, write in c. https://www.youtube.com/watch?v=1S1fISh-pag |
Beta Was this translation helpful? Give feedback.
-
stop with the rockets, rust is a good modern language and not everybody can handle C that is why languages like rust,go are used they might have issues but so does C. In the end these CVEs will not effect normal users. They are special cases. Also as stated by the dev this is a hobby project so asking a rewrite in the first place is illogical. C is only as much memory safe as much memory safe you write it. A C rewrite can have large issues that will further drag this incomplete project into mud. |
Beta Was this translation helpful? Give feedback.
-
Rust is the one dragging this project down in the mud. C (:rocket:) would fly this project into the sky :rocket:. Every CVE is a user-end bug, and C (:rocket:) has none! Rust is inherently non-memory safe and CVE prone no matter how you write it! C (:rocket:) is inherently 100% memory safe (:rocket:) and immune to CVEs no matter how you write it! |
Beta Was this translation helpful? Give feedback.
-
if anything, it should be Zig instead of C ;P all in all, good troll, 11/10 |
Beta Was this translation helpful? Give feedback.
-
Why not java?? minecraft is written in java Or C++ bedrock edition has a lot of bugs though |
Beta Was this translation helpful? Give feedback.
-
Did you even ready my reply?? |
Beta Was this translation helpful? Give feedback.
-
@offbeat-stuff dude. they're trolling lmao |
Beta Was this translation helpful? Give feedback.
-
It was fun though |
Beta Was this translation helpful? Give feedback.
-
Stop misgendering me. My pronouns are sneed/sneed (formerly chuck/chuck). |
Beta Was this translation helpful? Give feedback.
-
C may be unironically better than Rust for some of what I'm trying to accomplish with this project, specifically #446 🕸️ Web support. I find this other project very interesting: https://github.com/satoshinm/NetCraft. It is written in C and already has web support years ago thanks to Emscripten's superior support for C as compared to Rust. However it isn't as featureful. Steven was further along in gameplay functionality when this project forked from it, compared to when NetCraft forked from Craft — but we are much further behind @satoshinm in supporting the web platform, and it isn't as straightforward to port as with C. At one point in time, Rust was seemingly on track to becoming the language for the web. Native wasm32-unknown-unknown target thanks to the LLVM toolchain. There is/was(?) even a Rust and WebAssembly working group https://rustwasm.github.io but it fizzled out or they stopped blogging in 2019. Cargo package support for the web is hit-or-miss. Had this project been written in C using glfw or SDL, we may have already had web support by now. Rust's memory safety doesn't matter as much when targeting WebAssembly, though as a modern modern language it can be more pleasant to program in compared to C. No free lunch. Not planning to rewrite in C, myself, but if anyone else wants to I'm all for it. |
Beta Was this translation helpful? Give feedback.
-
https://rustwasm.github.io/ |
Beta Was this translation helpful? Give feedback.
-
This discussion is the funniest thing I have ever seen on this site |
Beta Was this translation helpful? Give feedback.
-
stupid apologist. |
Beta Was this translation helpful? Give feedback.
-
rewrite in jai |
Beta Was this translation helpful? Give feedback.
-
Beta Was this translation helpful? Give feedback.
All reactions