If you knew anyone that worked on the other ends of those deals, you'd know that it was always a load of trash. He basically relied on people caving to threats. That tactic only works if the other side believes the threat is credible and that they actually have something to lose.
Shit thanks for pointing that out. My door lock isn't 100% effective at stopping thieves, so I guess I can get rid of that annoying thing. Will be nice to never worry about being locked out again!
I don't get where the idea comes from that the popular error crates make error handling complicated in Rust. Because you're right, all thiserror is doing is giving you a shorter syntax for writing error enums. You could write the exact same things out by hand if you wanted to, and from the library user's side nothing would change.
As for anyhow, if a library ever exposes that, then that's just the author being lazy and not doing errors correctly. It's the equivalent of doing throw Exception("error!") in C#.
How do you feel your data for Kagi Maps compares to Google Maps? It's the kind of thing that's harder to test than switching web searches over to Kagi. I need to already know that the business and transit data is reliable which is why I still go to Google Maps.
Local queries are the I've things I use Google for still -- but Kagi makes it easy, you just start your query with !g and it redirects you. So it's pretty safe to switch the default.
But also great for speed. Larger libraries can take a measurable amount of time to import (even if they have no transitive dependencies). If only some of your code paths actually need the large library then it makes sense to import it lazily. Without lazy you have to do it conditionally which can lead to the imports happening in strange places rather than all being listed out at the top of the file.
That's how twilight anesthesia works. That's the kind you get when having something like wisdom tooth removal or an endoscopy. They want you to be responsive to instructions but completely relaxed and unable to form memories of the event.
I have no problem with Twitch channel points gambling via predictions, but doing that alongside actual* gambling is really messed up. It's blurring the line to the viewers between the two. And probably putting ideas in their head like "oh I won so many channel points predicting the outcomes, I should do some real gambling!"
*It could be sponsored and thus either rigged or all of the money being used was provided by the company under the expectation that it would be paid back to them through losses.
Gambling and scalping (and the combo that comes from reselling things like pokemon cards and other blind box products). They really do seem like the only options for a lot of people to live the kind of life that they've been sold as the ideal.
And as much as I hate that this is what is happening, I feel like that's what I'm going to end up being forced to try after 15+ years in working software development jobs, given how badly the companies want to replace us with LLMs. Hasn't gotten to that point yet but I'm shocked every day we're not laid off.
You say "a lot of people" but there aren't many of those. The scalpers/pokemon resellers/... making bank and posting on Instagram are, if not outright fraud, at best the 1% to 0.1% of those trying to do it
reply