It depends on your needs. I have minis that cost <100$ and have others that cost 500$. My cheapest mini has currently 3TB of backups of my personal things, so it serves my needs very cheaply. I don't need a GPU so it keeps the costs down.
I read somewhere that someone was using anonymous currencies to buy life saving medicine from "non traditional" markets because they were much much cheaper. Let me see if I find the article
It was a bit tongue in cheek I know. I have a very similar setup, but why being judgemental with such a simple thing? It seems like a waste of time and energy. You need those to tweak the setup instead.
You keep coming up with insults or inflamatory comments instead of answering the points, when I'm just trying to have a discussion of ideas. I don't understand why I am being unhinged when I even agreed with you partially.
I'm not a Rust programmer, I just play occasionally with it on pet projects. The languages I'm most experienced in are C++ and then C, I have no "horse in the race" of Rust, and I don't see c/c++ going away anytime soon, I just see what the language improves on them
You are not very consistent, first you imply that not "being a shitty programmer" is the fix for security issues in C. And then you say that any programmer can and will make mistakes...
Again you refuse to see my argument: yes I agree that viewing Rust, or any other language, as being a panaceia is wrong and following the hype. But Rust is provably better than C w.r.t to memory safety issues because it, provably, finds memory issues during compile time. I'm not discussing other types of security issues.
Yes C needs all that "freedom" with memory due to its low level use cases, but Rust is proving that it can also cover those cases (with the unsafe keyword) and cover the opposite cases where you want more strict memory usage and safety, so much so that you see now operating systems and firmware being developed in it. I won't argue and compare performance as I don't know enough.
You could argue that Rust by providing the "unsafe", keyword can and will have memory issues, but IMO the fact that you need to enclose unsafe operations in a scope allows for more focused reviewing and auditing
Ahah, I'm pretty sure many of the programmers on Linux et al, that worked on code with CVEs are still better programmers than you will ever be. The fact is that a lot of projects are just complex and they are hard to reason about on languages like C.
To me it feels like people romanticising their hobbies/escape activities. If they started doing it as work soon enough they would have lots of pain points and stress. Sure you don't have CVEs or libraries to update but the deadline for that chair or cabinet you were commissioned is coming and you can't just get the damn thing right. At the same time you have another customer complaining that you need to check some other stuff you've made that isn't working right .. see where I'm going?
I know a lot of people in the trades and they have very similar or analogous pain points as me in software.
Doing it as a hobby though? It's amazing. I don't really need a car anymore but I've been learning how to fix mine and it has been great
Gotta love user reported bugs. I had one that reported a product of ours crashed only on Mondays. We spent a total of 5 minutes thinking of a cause and appointed customer support for a Friday morning. Lo and behold the app still crashed.
In this case the app only crashed on Mondays... because that's when this user actually used the application
That's because Rust solves lots of issues caused by C, of course they are going to twist that knife and use it as a selling points. Humour is not bad, I've done lots of C and C++ and am not bothered a bit by it.
It doesn't reduce the importance of the language at all, just sheds some light on safer languages, Rust or not.
It's exactly the people that can have a choice who should be helping those who can't, don't you agree?
The fight for open software and hardware wouldn't be made by going around paraplegic people and bothering them about it, but by discussing it with the vendors and legislators.