mcronce

That doesn't mean it's not memory safe - it means that those constructs need to be thoroughly scrutinized for memory safety, which is significantly better than the entire codebase needing to be thoroughly scrutinized for memory safety

I haven't experienced that at all. Any of the codebases I've worked in - both proprietary and open-source - have converted errors to strings when it becomes necessary: When presenting it to a user, whether that means logging or placing it in an HTTP response body, etc.

Yeah, but that futzing typically happens separately near the "outer" error type's declaration - and when it doesn't, a concise .map_err() often does the job.

It's also often taken care of by a sort thiserror macro invocation per "inner" type. There are obviously more complex error setups, but this covers the vast majority IME

I had a bug hunt as part of an interview once (or, I should say, once that I remember). It was different from that proposal in that the code was not part of the company's actual codebase - it was entirely fabricated for the test. It was fun, though; I enjoyed that more than livecoding and live-whiteboarding.

According to another replier it's been moved to dedicated VMs in Azure, so it's not as bad, but still subject to noisy neighbors. I agree with your assessment - if I were fixing it I would do something similar.

They're also benchmarking on Github Actions runners, with swings of up to ~50% from run to run, which is more than enough to shuffle the results to more or less random positions. I contributed to it last week but without any will to solve that kind of fundamental problem I don't see it as being particularly good.

There's also no control on quality of contributions to the language-specific benchmarks.

That would be changing the actual piping, which they mentioned.

A misfire is a failure to combust the air/fuel charge in the combustion chamber during the expansion stroke, and they aren't typically caused by muffler deletes.

They can lead to the popping sound you're describing, but they don't always, and they're far from the only cause, and muffler deletes aren't necessary for those either. Unburned fuel hitting oxygen in the tip of a hot exhaust and immediately burning is the direct source of the noise, and causes for that are numerous.

Your analogy really hits. I don't mind doing construction in general (I quite like doing it once in a while), but roofing absolutely sucks no matter how you cut it

I can't (or, more accurately, don't) believe that, but I can certainly believe they have nothing interesting to say about the topic of static vs dynamic typing.

If slide-out keyboards were still a thing they wouldn't be nearly as bad but we had to get rid of those because being thinner is the most important thing in the world

You, me, and anybody else reading the comments.

If you want to disagree on the metaphysics or whatever go ahead, but this is already proving to be a huge waste of time and I'm not particularly interested.

Not disagreeing you, just adding a point...I self-host Conduit and use FluffyChat on my phone, with ntfy for push notifications. While that works great most of the time, I occasionally have to restrict ntfy because it'll get into some state where it destroys my battery... And push notifications obviously don't work at all in that state.

It's very unfortunate there isn't a privacy-friendly push notification mechanism built into Android that doesn't ruin battery life. Or iOS for that matter; that might actually be a feature that would get me to switch.

I would

And yet here you are reading that comment, writing this one... And those experiences are real.

That's certainly possible, but it doesn't make your experiences any less real

Note that this isn't true for all heat pumps, nor all furnaces. A forced-air system can vary the air handler speed, and a hydronic system can vary the water temperature; with heat pumps, there exist variable-speed compressors, but there also exist single-speed compressors.

Also known as the AFLW 1.0 License!

Why do you assume they're not touching them?

> Ameriflu™ by Bayer®

FTFY

The project itself may not be large, but if it's pulling in 517 dependencies, that's a lot to compile.

Rust also does significantly more for you at compile time than C++ does, so I don't mind the compiler taking some not time to do it

If you're already an expert in some other programming discipline (e.g. another language) I wouldn't expect it to take 10 years to become a Rust expert. I'd expect one or two if you're using it primarily, which is similar to what I'd expect for most other languages.

The downside is that there's hardly any political will in the US to regulate businesses

I think that depends on your perspective - specifically, whether you think more deaths or fewer deaths is winning:)

I haven't found a single "silver bullet" solution, but the combination that has worked for me is bat houses + citronella (candles as well as whole plants, planted around the patio/deck) + the classic electric bug zappers.

We wanted to avoid insecticides because we have a pretty significant pollinating bee population that we didn't want to harm, but if that's not a concern for you, just carpet bombing the yard with pyrethrins is a solid foundation.

I've had good luck with Mosquito Magnets in the past; the only reason I'm not using one now is because the bat houses are approximately zero maintenance, and I'm a sucker for fire-and-forget solutions

If charging for it isn't too hard, it sure as fuck isn't too hard to list it

I self-host Gitlab, which is pretty familiar to people, but I still mirror repos for which I'm hoping to get contributions to GitHub for the same reason

My current pet example for the trend of hiding more and more details from users is an issue I recently had with Doordash.

I was trying to place an order, and it kept failing with a red banner stating "something went wrong" (I'm paraphrasing as I don't recall the exact verbage, but it was one of those completely worthless error messages)

Pop open dev tools ... the server is returning something about a graphql error.

Support had no idea what was wrong.

The problem ended up being that my saved credit card had expired. For fuck's sake, that is a user-actionable error; tell me what the problem is. At least tell me it was a payment problem, since that's probably all the payment processor told you.

Rune was mine. A buddy and I got into level design, and I got into modding along with it

One often gets the impression that large swathes of people (even on here) don't realize that software today is more complex than software from 1993