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.
Same, and I use portainer to manage my docker compose stacks.
I can bring down a container without bringing down the whole stack of services.
Yeah, I opened the website thinkint it would be the github list with a better search, but it’s 95% AI crap
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.
Pogs are the civilized upgrade of throwing rocks together. Fuck yeah it should come back. It is ingrained in our DNA
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.
I am not sure if it is still applicable, but with the 3-2-1 rule, that should work good enough. 3 copies of your data on two different medium with one off-site backup.
So the data with it’s local backup that is copied to an off site backup. Which is probably your case (I assume that your offsite backup is a copy of your local backup).
Bring back community servers, so the developers can keep their official servers and people that want to play on community servers can do that do.
It’s a solved problem that publishers tells you is hard to do in the name of money.
Don’t look harder into it.
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.
I had a rough morning and your comment made it worst.
In GrapheneOS, Settings -> Battery -> Charging Optimization.
You’ve used Windows for so long that you don’t remember how it was when you first started using it.
This isn’t different than what you are doing with Linux. The flow gets better and better and you will acquire the experience needed to navigate the issues. It takes time, that’s all.