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.

My girlfriend is gonna be mighty upset is she thinks I’m into that kinda thing. […] please change the image to something Gnome-related and/or trustworthy.

That’s an interesting takeaway from a DDoS issue

It’s a step in between

It then takes it a step further, as they are both 0 in that regard

I’d say that trying to get Rust everywhere is just something that is done in the hope it will help the ecosystem mature faster. It’s a bit hard to compete with languages that are 30, 40, or over 50 years old

TBF, your previous post reads to me the opposite way, like ‘it is not enough of a hate site’. Also I would offer you to look at it as a Venn diagram, if something is a hate site and more, it is still a hate site, just with extra

Yeah, that sounds like a crappy way to promote the product

What’s the use for those in corporate env, that’s not available outside of it?