Sure... I mean why are you wary of them because they work with the US military?
FizzyOrange
joined 2 years ago
I agree. The syntax for useless error handling is indeed more verbose than Rust (a whole if block Vs a single ?) but the difference when you actually do proper error handling and add a useful context message is much smaller.
You could argue that's a good thing because it encourages writing proper error handling code.
I've seen plenty of Rust code with only ? which leads to really bad error messages. I've seen Rust errors in complex programs that are literally just Could not open file or directory - no context, no filename. Go definitely has better error messages on average.
That said I still prefer Rust's error handling, and writing Rust in general.
There isn't. This is the colloquial use of "exponentially" which is very obvious from the context.
due to their support of the US military
What?
I find the git CLI pretty intuitive
You might be the first person to ever say that! How do I delete a remote branch?
Still better than Device Tree though right?
that they would disclose on their website
Wouldn't it make more sense then for them to simply host the Flatpak themselves? I kind of thought that was the whole idea of Flatpak.
What would they sign it with? How do you verify the signature?
I don't think this is a very interesting article. We already know AI suggests nonsense a lot of the time. That in no way demonstrates that it is net-negative. In my experience it's a net positive even accounting for the times it gets things wrong.
Yes you do have to review its code closely. News at 10.
It is kind of funny that they picked an example where it made an obvious mistake for their hero image though.
No, the filter is correct even for UTF-8. Any ASCII character is exactly unchanged in UTF-8 (part of the reason it is popular). Since this code only filters out ASCII characters it works fine with ASCII or UTF-8.
This is 14 years old by now - hardly "modern". RAII itself is even older.
This is fine precisely because it is a blog post. If it was a scientific paper... sure maybe they shouldn't say that. But the meaning is abundantly clear from the context. There is no ambiguity.