And you have sources? Because last time I checked this was the worst way of doing it, as you leave enough bacteria to try and mutate into resistivity.

If you already had resistant bacteria, taking antibiotics wouldn’t heal you for long anyway, tried it first hand a few months ago.

Hashes are ‘proper cryptography’, it’s just that sometimes even when you use the right tools you get a bad result, e.g. when a backdoor exists in the hashing parameters that is hard to find. Yes, sometimes hashes are overused, but this example here doesn’t seem like the case, and true randomness wouldn’t allow the proofs to be deterministic, thus requiring everything to be checked which is not desirable because it requires time and power to do so.

Maintainers, I guess, as in, the update that was rolled out, was broken for some users. But I don’t know if that’s the case here

But then someone will have to deal with it somewhere, better just unwrap it under the carpet.

it’s clear at this point already that Zig is a weakly-typed language

Uhm… pretty sure it isn’t.

They seem to think any type inference makes for a weak typing, judging by their previous rant about auto in C++

So, yeah, author’s views are a bit special, not sure this article will help me be better :(

That’d betting the information they collect from literally everywhere will not be enough to sanitise the bad parts. This might be the case but I’d say this bet is heavily rigged in their favour.

Albeit true, I want to note that some languages encourage such practices way more than others do. Also, when you’ve got a hammer everything looks like a string nail.

So he wanted features merged outside maintenance window again? I’m a bit inclined to think, Kent doesn’t really want to play by the rules at all

Chances are, he doesn’t have any female friends, because he scared them off long time ago.

By printing memes on it?

Vibe coding is when you’re not coding, just typing prompts into AI in hopes it will produce a legible code.

The unraveling of the Byju’s empire has come as a shock to many employees. One former employee who led a team for several years until 2024 told me he was proud of the work he and his colleagues had been doing

This is the only side that gets my sympathy in this story, the workers who tried their best to make a great product

This is maybe a second time I hear about the Browser Company, but what they declare sounds a bit contradictory. They say, they moved too fast with Arc, now they say that speed is not going to be a trade-off anymore (so, even faster changes, even more to learn for a user?). Open-sourcing a product without its dependency seems better than not at all. What they aspired to build sounds interesting, but ultimately, I’m not sure I would’ve tried that before, and even less now after they discontinued it ¯\_(ツ)_/¯

Source I found from a link on Stack overflow

Also, the could be better if it had alt text

I find this statement to be a bit contradictory to your point of ‘there is no “best” solution’

I don’t think vibe-coding is particularly good thing, but I find it completely normal for someone to just want to vibe something up and not want to understand. It’s not always a useful approach, but sometimes it might be a ‘best’ strategy, too

That’s just short for JavaScript, isn’t it?

If that’s a joke, it’s a good one. Otherwise, well, there are a lot of “this letter isn’t needed let’s throw it away,” in most cases it will not work as good as you think.

This quote from Linus is what I find inspiring hope of a future wider adoption or Rust:

Thanks. I decided to try to do the merge on my own, but failed. I came close, but it was good to have your example merge to see what I got wrong.

The pin_init becoming a crate of its own, but ‘pin::Pin’ being in the core crate ended up messing with my “monkey see, monkey do” approach to Rust merges.

I’ll learn eventually, in the meantime please do continue to give me example merges and I’ll use them as training wheels.

Not everything that’s poorly written is ai, you should give humans more credit

We have an engineering manager that’s about the same, the only issue is that they let PR through because features are wanted and there’s no time to get things right.

I think, I may be pleased to have to redo everything several times to make it better and simpler, but what we get is that everything is bad but we’ll still merge 😞

I now feel at several times I fucked up quite a lot by making something that works but not something simpler.