lad

That’s almost as good as the ones that limit password on the sign-in UI, but not on the sign-up

GPS information from the source

Here, I think you’re being downvoted because you missed one of ð in the

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

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.

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

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

One can be pro- or anti- any concept or thing, some options just make more sense

This is an interesting article, but I think that this standardisation is exactly for port being the same, not for pinning specific implementation of the 600+ pages long standard.

Wow what a marketing scum trick to show all compatible older generations as separate products

because I’m not interested in arguing

This sounds more toxic to me, tbf

So… solitaire should be 18+ after all?

Because it’s a computer banana and the mascot is real? I don’t know, this makes no sense, but I can see how sometimes this kind of mix can work

This is just gold 🤣