![](/static/253f0d9b/assets/icons/icon-96x96.png)
![](https://lemmy.ml/pictrs/image/c0ed0a36-2496-4b4d-ac77-7d2fd7f2b5b7.png)
It’s the second time I see it on a programmer humor community. I get you want to advertise, but we already told you that this isn’t the place for that
It’s the second time I see it on a programmer humor community. I get you want to advertise, but we already told you that this isn’t the place for that
Oh I’m not talking that it can’t be trained well. That’s not my point.
Of course dogs can be trained to sniff drugs or find people, the gist of it is that they were trained for this behaviour, and might not understand it like we do.
A good exemple is a study that research on cancer sniffing dogs had problems with false positives.
proud Rust developer
Joke aside, everytime people gush over AI, I always have to remind them that AI is just a puppy that learnt how to maximise treats, and not actually understand shit. And this is a perfectly good example.
Oh yeah, there it’s a completely different story. But that’s mostly on OP to not provide context.
But if it was installed that way, it’s just MS being shitty again
Apart from the search engines being both shitty, here there’s nothing wrong
If you installed an extension to use bing search, what you want is to use bing search, not Google. So of course the extension has to say “don’t switch”
There’s also a good point on chrome’s side. There’s extensions that will switch your default search engine without your consent, so having the possibility to undo directly is nice.
Another way to see it, would be to switch chrome for firefox, Google search for duck duck go, and bing to qwant. Same story, but no shitty companies clouding judgements
Good meme, bad reasoning. Things like that are why JavaScript is hated. While it looks the same, It should never, and in ANY case be IMPLICITLY turned into another type.
Dang. I didn’t knew that 🧡 was so popular. I thought it would be ♥️ but alright
Oh, then you use and_then()
or something similar.
There’s also the possibility to use the guard clauses patern and do let <...> = <...> else {}
.
And finally, you can always split into another function.
It’s not straight rules. It depends on what makes it more readable for your case.
Use a match
? Unless it’s for guard clauses, a match is fine enough
It’s a lot less readable imo. As well than a cargo fmt
later and it’s gone (unless there’s a nightly setting for it)
Those async blocks exist when doing async in traits.
And I never said I respected the 4 level of indentations. That’s exactly the point of those rules. Keep it lowly indented but still readable
While I totally agree with that philosophy, it heavily depends on the language.
For Rust, my philosophy is more like this:
Your code goes up to 110.
I’m out of the loop. What is “winning humane” and what does it has to do with programming?
There’s Listenbrainz, but it’s more artist based.
I would do that… If CI wouldn’t be set to
-D warnings
Who even does that? Oh wait, it was me.
Joke aside, it does help to keep the code clean, even more for open source projects where multiple separate people may all have their own codding style, and it helps make it easier to organise.
But I do agree that it can be really, really annoying.