Are Rust macros akin to the C macros? Basically an inline replacement of a code section?

Lots of your point apply to any language it seems. I should have specified new projects I guess.

But the points you’ve made are good nonetheless

I interface with low level communication protocols, mostly uart, so it fits my use case. But it is nice to see the hurdles people encounters. It tells a lot about the language.

I know Rust superficially. I use it to create simple tests for my embedded projects, so mostly just serial terminal with keyboard inputs.

It works a lot better for me than python because Rust is a lot closer to C than python.

So I cannot comment on Rust shortcomings. I was interested in knowing for what kind of projects Rust wasn’t good.

I am glad for your comment because I work with mcus and embedded solutions in C, so Rust, in that case, wouldn’t be neccesarily safer than C.

I will have to look into it. I need to do 30h of training every two years, so I will learn Rust regardless, but I was thinking about eventually switching to Rust for embedded projects. Might just keep Rust as my scripting language because it is easier for me than Python

I come from embedded C, so what you describe doesn’t feel alien to me (minus the security vulnerabilities haha)

I much prefer working with Rust restrictions than a higher level language without hard types because I am used to it.

Where would you say Rust isn’t the right solution?

We always hear how great Rust is, but I’d be curious to know where it isn’t.

A production code should never have any warning left. This is a simple rule that will save a lot of headaches.

Every AI company CEO/C-suite is gambling that they won’t be left holding the bag.

Either AI fails and CEO/C-Suite made their money already, or AI succeeds and they carved an early lead in the market and gamble even more.

Workers are only there to build the biggest stack of chips possible before it gets cashed out.

Sometimes, people do that. But using 0/1 is explicit enough since you can refer to a line as ‘1’ or ‘0’ for high/low on the hardware as well

I am a lazy dev (not really, clients always want fast code), so I use the provided HAL libraries 99.9% of the time.

But I have seen code where someone would write something like

gpio_write(PIN_X, true) 

and it always stood out to me.

I am working with C in embedded designs and I still use 1 or 0 for a bool certain situations, mostly lines level.

For whatever pea-brained reason, it feels yucky to me to set a gpio to true/false instead of a 1/0.

LLM are prediction engine. They don’t have knowledge, they only chain words together related to your topic.

They don’t know they are wrong because they just don’t know anything period.

LLM are just sophisticated text predictions engine. They don’t know anything, so they can’t produce an “I don’t know” because they can always generate a text prediction and they can’t think.

My uneducated kernel take. Flexibility is acceptable and desirable in small projects or low impact projects.

When the majority of the internet and a good chunk of PC are dependent on your project, predictability and stability is much more important than flexibility.

Cable TV was originally paid for so that channels wouldn’t need to play ads to be profitable. We know how this ended.

Steaming services were originally paid for so that they wouldn’t have to run ads to nlbe profitable. And we’re almost back to where cable TV is. Soon, all plans will have ads no matter how premium is a plan.

Fuck that noise

Let’s be real. A company comes in and offer you a life changing, fuck you money that covers the rest of your life.

Very few people can resist that, me included.

I always use stdint.h so that my types are compatible across any mcu. And it makes the data type easily known instead of guessing an i t size

In embedded, if you are to the point that you need to optimize the bools to reduce the footprint, you fucked up sizing your mcu.

I might be wrong, but the Material 3 UI feels a lot closer to iOS.

I agree with you, I’d rather have a crazy snappy phone instead of nice animations and effects, but we are in the minority. This doesn’t sell.

Just look at any website. UI graphics are king, and usability is at the lowest it can be.