> Gears are a common type of spare part used in various industries...

/Spare/?

The whole thing looks like "AI" mashup.

Seems like an manufactured controversy - homeless people were given a temporary job and earned money. What's the difference in paying them to show a shop / company sign on the streets to asking them to roam around in a conference with a hotspot device?

Yup!

> Fees for room and board—yes, literally for a thin mattress or even a plastic “boat” bed in a hallway, a toilet that may not flush, and scant, awful tasting food—are typically charged at a “per diem rate for the length of incarceration.” It is not uncommon for these fees to reach $20 to $80 a day for the entire period of incarceration.

https://www.brennancenter.org/our-work/analysis-opinion/amer...

This is a mockery of the term "slavery". It is no more slavery to be coerced to work for a shorter sentence than it is slavery to be coerced to follow the law to avoid prison.

"Behave a certain way and you will be imprisoned for less/no amount of time" is not slavery unless the law is slavery. The full term imprisonment is just, and being able to shorten it is a privilege.

I'm the opposite - I really like checked exceptions in Java because it's very easy to see how developers are handling errors and they also form part of the function signature.

Most functions will just pass on exceptions verbatim so it's better than error return values because with them the entire codebase has to be littered with error handling, compared to fewer try catch blocks.

setjmp, etc. are like unchecked exceptions, so I'm also not a fan, but I use this occasionally in C anyway.

Shit, you figured it out. It's not! That's whats been causing all the autism! Big ultrasound has been managing to keep this under wraps for decades!

Wondering if OP has malware that’s injecting results into the search.

Wanna DRY out your github actions yaml?

Generate it from Dhall, or cue, or python, or some real language that supports actual abstractions.

If your problem is you want to DRY out yaml, and you use more yaml features to do it, you now have more problems, not fewer.

It's annoying, but not for the error handling. To the contrary, I think the error handling is actually improved by this pattern. If you manually convert beforehand you easily run into working with a Result<Result<T, E>, E>.

What I find annoying about the pattern is that it hinders API exploration through intellisense ("okay, it seems I need a XY, how do I get one of them"), because the TryFrom (sort of) obscures all the types that would be valid. This problem isn't exclusive to Rust though, very OO APIs that only have a base class in the signature, but really expect some concrete implementation are similarly annoying.

Of course you can look up "who implements X"; it's just an inconvenient extra step.

And there is merit to APIs designed like this - stuff like Axum in Rust would be much more significantly more annoying to use if you had to convert everything by hand. Though often this kind of design feels like a band aid for the lack of union types in the language.