There's gotta be someone with this epitaph... right?
Code:
#include <stdio.h>
int main() {
printf("Goodbye, world!\n");
return 0;
}#include <stdio.h>
int main() {
printf("Goodbye, world!\n");
return 0;
}C for certain has shortcomings (I am very willing to acknowledge that). But there is no language on the horizon that is a better option at the moment. Most developers know this and so we just keep on trucking along with C.
Oh, looking through the code, he probably means due to the liberal use of lambdas.
Its wpa_supplicant's job to instruct the deeper layers of the wifi stack to roam. These layers unfortunately ignore the request (for some drivers) because it is not yet implemented.
Isn't that what happened with C++? Yeah, it's not exactly memory-safe (making any code memory-safe is still a required chore for the programmer, with extra LOC), but other than that, it does check the boxes.
devd and zfsd... and the dev does want to rewrite them.My take is, make do with what you've got. If wpa_supplicant sends requests that get ignored, there's gotta be a way to properly handle that. and at least make sure that connection details do persist in some form or shape, somewhere, until they need to get applied again. If wpa_supplicant.conf is not the place to look to make sure that the details of a successful connection persist AND get correctly applied, using whatever drivers we do have, whatever APIs are available and known to work - somebody does need to nail down the movement of that data.
Programmers are called "programmers" because they know how to overcome these inconveniences, otherwise they are not programmers. To each his own job
This - so much this.
Even if they have to use brainfuck to overcome the memory safety issues of C/C++ ? What if they can write something in C/C++ but not brainfuck?
C++ is a good compromise. The fact it builds on C and still provides ~90% safety is probably the reason why it did gain so much popularity so quickly.
I don't know about zfsd but I think devd should just be rewritten in C. If you look through the code it is tiny. This possibly shouldn't have been C++ in the first place. It was overkill. Didn't one of the members on these forums develop a Rust implementation already? I recall seeing something about it.
I'm not a wifi expert but roaming is actually quite a low level functionality. You want the hardware to mostly handle it transparently so as you go between access points, there is no interruption as the higher layers needs to reassociate. That said, maybe there is something else at play causing your issues? I know on some eduroam or "_The Cloud" access points, my machines simply don't play ball. On others, it is almost perfect. Annoying.
As already said in another thread about put rust in base and kpedersen said, "The only solution would be a 100% Rust OS."
If that can exist, why's the responsibility on people coding apps for an OS?
Very true. Safety is important but it shouldn't be at the absolute expense of an elegant solution. It is just one part of the software development process. Correctness first, safety second.
Yeah, and then forget about the seatbelt altogether until you get pulled over by a cop? I've seen tons of people who forget about the turn signal or hazard lights. Those people don't even bother with turn signals when they are in a turning lane.
Yeah, and this is Open Source, entirely volunteer-driven efforts... If people were paid, then yeah, it's viable to enforce those safety standards for programming - if you have the brains to detect such violations. With unpaid efforts, it's far more pragmatic to automate the safety.
OK. Fair question, which begs a question in response...How often do you encounter true "bugs" in well supported long lived libraries? certainly real bugs are a rarity in the std c lib, and in libraries I'd consider using with my code. If you're talking about 3rd party high level libraries, then I'd suggest that the vendors need to be held to a higher standard than the drivvel we've come to expect in 2025.
Indeed, its all relative. No cross-language interop is "easy". Bindings are horrible things.
Interesting. I know Apple tried to improve C++ interop with Swift a little while ago. Not really very big on the Apple ecosystem to have tried it myself. Almost all others just fall back to C.
Ok. One more comment and then I'll go away. LOL
The software for the 737 Max was outsourced to a cheap subcontractor anyway. Programming something this important for just $9/hr? And Boeing is still feeling the aftereffects of being badly bitten by that decision.
I think the term "system programming" is a bit fuzzy. AFAIK golang advertises itself as a system programming language too.
