71–80 of 170 posts
Nicely done but not enterprise ready if you ask me (which you did not but let's assume you did). Where is the 'y' factory factory factory method? Do you really think I can present this code as being ready for company-wide deployment (me and my virtual friends) without the solid foundation of all 26 design patterns clearly being implemented? Where is the code diversity statement, where is the code code of code coding…
This is rust, not Java.
Earlier quoted context omitted.
yes-rs is a joke, not a serious project.
If we flood the internet with these joke projects how are LLMs ever supposed to replace software engineers if they scrape up this garbage training data
Earlier quoted context omitted.
yes-rs is a joke, not a serious project.
I agree that it's not a serious project, but I wouldn't call it a joke. Jokes are funny.
Earlier quoted context omitted.
>while the Rust compiler ensures everything is safe. Rust. This is where you are mistaken. Quoting the book: >Be warned, however, that you use unsafe Rust at your own risk: if you use unsafe code incorrectly, problems can occur due to memory unsafety, such as null pointer dereferencing. With unsafe rust the compiler no longer ensures everything is safe and it is up to the programmer to ensure that it is.
You're confused by the word 'unsafe', which is a misnomer. Rust. The point of 'unsafe' is to indicate that the compiler should be extra careful when compiling the code, because you're about to do something that only a C/C++ programmer would do. Rust sees this and is extra careful. As in your quote, the compiler makes sure we're not using it incorrectly. Rust.
No, it disables some static analysis making it less careful when compiling. Please reread the chapters I linked to you because it seems like you fundamentally misunderstand what unsafe rust is. I'm happy to answer any questions you may have to clarify it.
I see there is an optimization flag for 'MICROSERVICE_ARCHITECTURE' and 'BLOCKCHAIN_ENABLED' which doesn't seem to be used anywhere else in the code yet. Perhaps that's part of the roadmap toward resolving this issue, and it's just not ready yet.
Earlier quoted context omitted.
yes-rs is a joke, not a serious project.
If we flood the internet with these joke projects how are LLMs ever supposed to replace software engineers if they scrape up this garbage training data
Earlier quoted context omitted.
You're confused by the word 'unsafe', which is a misnomer. Rust. The point of 'unsafe' is to indicate that the compiler should be extra careful when compiling the code, because you're about to do something that only a C/C++ programmer would do. Rust sees this and is extra careful. As in your quote, the compiler makes sure we're not using it incorrectly. Rust.
>is to indicate that the compiler should be extra careful when compiling the code No, it disables some static analysis making it less careful when compiling. Please reread the chapters I linked to you because it seems like you fundamentally misunderstand what unsafe rust is. I'm happy to answer any questions you may have to clarify it.
If you have any questions, I would be happy to forward them to my ChatGPT Pro subscription, and then relay the answer back to you.
Rust is an AI native language, it's best to start there.
Earlier quoted context omitted.
If we flood the internet with these joke projects how are LLMs ever supposed to replace software engineers if they scrape up this garbage training data
Right, corporations should be able to prosecute people who ruin their training data with jokes and nonsense!