Agile was the cool new thing years back and has been abused and misused and now, pretty much every dev company force it on their team but do whatever the fuck they want.

Agile should have a lot of traditional project management but doesn’t because it became the MBA wet dream of metrics. And when metrics become the target, people will do whatever they need to do to meet the metrics instead of actually progressing the project.

My hot take : lots of projects would benefit from a traditional project management cycle instead of trying to force Agile on every projects.

Make something free for it then? The stuff is open and the license makes it so that it stays that way legally (though, in real life, it’s different but that’s another discussion) and any and all other contributions made to the project stays open source.

Which are what guardrails are for. When something change, you don’t know the impact the change will have.

By having guardrails, you make sure to limit/eliminate potential critical issues.

What shell do you recommend?

Palantir could refuse to accept the mandate and the money, but they didn’t. So the governments are evil, and so is Palantir

The documentation is usually dog shit.

The corporate culture does not allow appropriate time for the documentation as it is considered something that cost money without a quantifiable gain.

It permeates in the FOSS space as well since writing good documentation is a skill and it is not fostered in corporations. So devs start great projects with terrible documentation.

The cat is out of the bag and long gone.

People got used to the simplicity of centralized services, and corpos made great efforts to make everything 1-click.

So when the average users need to do more than 1-click, they won’t use the software.

It would help if anti-trust laws were applied and these mega-corpos got broken in a thousand pieces. Centralized monolith services would have a harder time to thrive and give space to federation/decentralization.

Capitalism has distilled its parasitic behaviour down to a science to suck the life out of anything that dare to stand out, and leave its corpse dry, for the sake of more profits.

Boring is ok for 95% of the things.

It is how its done today.

Every semi-big or big corpos gamble their money trying to be the one coming on top and capture the market.

So it is not surprising to see that.

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.

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