C is fun to me because the syntax is easy to understand and straight to the point. C is also great for learning low level coding, I find Rust so confusing
Rust requires you to unlearn some of the C and CPP habits. And so it’s like learning a language that approaches things differently. That is pretty fun to see how another language solves a problem etc.
I think rust is a very fun and interesting language tbh. But you are free to not like it, that’s all good man. That’s why we have different languages.
After getting into rust, for me, you need to convince me to use C or Cpp, they have their niches for sure, but rust allows that too like embedded programming etc.
This checks out. I tried some Rust coding challenges and couldn’t get my stuff to compile mostly. When I see the solution it seems straightforward but also not intuitive.
Yeah, there’s a lot a cool ways to chain ways to process things and all. Its like building a muscle, I’ve noticed with time and practice (sometimes just repetition after seeing the answer if that works for you) and things get more intuitive. Cause theres a lot of thought on why a pattern is a certain way, and on C you could use teh same hammer for everything. Here you have different tools in a way.
The first picture isn’t what people write, even though it’s technically compilable, it’s not what C is.
The second is a normal syntax, pretty simple to understand if you write enough code.
C is very simple language at it’s core, and it allows for it to be used in a very complicated systems.
The if statement not requiring brackets caused this bug. Rust fixes these issues with pattern matching and mandatory curly braces in if body statements
Yeah, it’s not optimal, I don’t think anyone argues that it is. It has a bunch of ways to shot yourself in the foot, no questions about that, people were writing books about that for decades. Not like there is an optimal language that doesn’t allow you to make some stupid mistakes.
But also, a lot of that non-optimality is what gives it advantage. Well, that and enormous amount of legacy code and expertise.
Sometimes you need to pass around raw pointers without caring about memory ownership, and for that situation it’s optimal. I’m glad you have your mandatory curly brackets, but sometimes I just want my microcontroller to blink an LED and for that I’m in turn glad that I can be as quick and dirty as my filthy mind allows me.
And for serious projects we’re all MISRA compliant anyway, and it mandates curly brackets for ifs and proper cases for switch.
Let’s not get too abstract. Just because Rust made its own mistakes doesn’t mean it didn’t fix the mistakes I pointed out
Serious projects have huge memory safety issues that don’t exist in Rust. More than half of security CVEs are due to the nature of C. Rust just has fewer bugs like Heartbleed because it doesn’t let you do a buffer overrun
That’s because serious projects basically don’t exist in Rust. Yet, probably, Rust seem to be a good language that people like, so those are to follow, but for now they’re rare.
Or don’t, if we discover that Rust has some other issue that only happens when the project grows old enough.
Personally, I’m sticking to the devil I know, the one that has almost 60 years of accumulated knowledge and best practices.
Rustls can already replace OpenSSL, but maybe that’s not serious enough for you. Sure, the ring backend embeds assembly for the crypto operations, but that’s the point:
You can have a safe interface for interacting with potentially unsafe code. Do all of the memory allocation and string manipulation stuff in Rust and call out to crypto in assembly
Yeah, it’s not serious enough for me. It will become serious if it actually replaces openssl, or at least actually is in use by any significant numbers. Until then, it’s a project that can potentially maybe sometimes be used by someone maybe, which by definition isn’t serious. Like any other project, it needs time under pressure, it needs to mature with use, be supported for some time, accept patches and changes, and sustain constant prodding by people who would like to break your stuff.
OpenSSL is a standard for almost 3 decades, Rustls is cautiously maybe being pushed in experimental branches.
It’s like that with everything Rust related really. We are at a phase where enthusiasts enthusiastically trying to convince someone to consider their new toy, which means we can’t really compare it with decades old projects that were scrutinized and stress-tested by millions of people.
What part of Rust is fun?
C is fun to me because the syntax is easy to understand and straight to the point. C is also great for learning low level coding, I find Rust so confusing
Rust requires you to unlearn some of the C and CPP habits. And so it’s like learning a language that approaches things differently. That is pretty fun to see how another language solves a problem etc. I think rust is a very fun and interesting language tbh. But you are free to not like it, that’s all good man. That’s why we have different languages. After getting into rust, for me, you need to convince me to use C or Cpp, they have their niches for sure, but rust allows that too like embedded programming etc.
This checks out. I tried some Rust coding challenges and couldn’t get my stuff to compile mostly. When I see the solution it seems straightforward but also not intuitive.
Yeah, there’s a lot a cool ways to chain ways to process things and all. Its like building a muscle, I’ve noticed with time and practice (sometimes just repetition after seeing the answer if that works for you) and things get more intuitive. Cause theres a lot of thought on why a pattern is a certain way, and on C you could use teh same hammer for everything. Here you have different tools in a way.
Yes, C syntax is easy understand
The first picture isn’t what people write, even though it’s technically compilable, it’s not what C is.
The second is a normal syntax, pretty simple to understand if you write enough code.
C is very simple language at it’s core, and it allows for it to be used in a very complicated systems.
Nobody is arguing C is complex. The argument is that it’s not the optimal syntax.
For example, case statements needing breaks can cause logical issues with incorrect merges.
How about this
https://en.wikipedia.org/wiki/Unreachable_code#goto_fail_bug
The if statement not requiring brackets caused this bug. Rust fixes these issues with pattern matching and mandatory curly braces in if body statements
Yeah, it’s not optimal, I don’t think anyone argues that it is. It has a bunch of ways to shot yourself in the foot, no questions about that, people were writing books about that for decades. Not like there is an optimal language that doesn’t allow you to make some stupid mistakes.
But also, a lot of that non-optimality is what gives it advantage. Well, that and enormous amount of legacy code and expertise.
Sometimes you need to pass around raw pointers without caring about memory ownership, and for that situation it’s optimal. I’m glad you have your mandatory curly brackets, but sometimes I just want my microcontroller to blink an LED and for that I’m in turn glad that I can be as quick and dirty as my filthy mind allows me.
And for serious projects we’re all MISRA compliant anyway, and it mandates curly brackets for ifs and proper cases for switch.
Let’s not get too abstract. Just because Rust made its own mistakes doesn’t mean it didn’t fix the mistakes I pointed out
Serious projects have huge memory safety issues that don’t exist in Rust. More than half of security CVEs are due to the nature of C. Rust just has fewer bugs like Heartbleed because it doesn’t let you do a buffer overrun
That’s because serious projects basically don’t exist in Rust. Yet, probably, Rust seem to be a good language that people like, so those are to follow, but for now they’re rare.
Or don’t, if we discover that Rust has some other issue that only happens when the project grows old enough.
Personally, I’m sticking to the devil I know, the one that has almost 60 years of accumulated knowledge and best practices.
Rustls can already replace OpenSSL, but maybe that’s not serious enough for you. Sure, the ring backend embeds assembly for the crypto operations, but that’s the point:
You can have a safe interface for interacting with potentially unsafe code. Do all of the memory allocation and string manipulation stuff in Rust and call out to crypto in assembly
Yeah, it’s not serious enough for me. It will become serious if it actually replaces openssl, or at least actually is in use by any significant numbers. Until then, it’s a project that can potentially maybe sometimes be used by someone maybe, which by definition isn’t serious. Like any other project, it needs time under pressure, it needs to mature with use, be supported for some time, accept patches and changes, and sustain constant prodding by people who would like to break your stuff.
OpenSSL is a standard for almost 3 decades, Rustls is cautiously maybe being pushed in experimental branches.
It’s like that with everything Rust related really. We are at a phase where enthusiasts enthusiastically trying to convince someone to consider their new toy, which means we can’t really compare it with decades old projects that were scrutinized and stress-tested by millions of people.