Kushan

Am I correct in saying that you’re used to languages that aren’t type safe? Or at least not as strict about it.

Everything you’re describing sounds more like you’re struggling with type safety in general and I wouldn’t say any of those packages are at fault, in fact I’d even go further and say they’re like that by design.

The reason you don’t actually want any of those separate packages to be more interoperable out of the box is because that would couple them together. That would mean dependencies on those packages, it would mean if it wanted to use something else then you’d be a bit stuck.

Like I’d question using a uuid as a salt, like it’s fine and I get why they’re suggesting it, but you can use anything as a salt so why couple yourself to a specific uuid library? Why couple yourself to uuids at all.

Side note: I’m guessing the reason the crate expects you to supply your own salt is because you need to also store the salt next to the password hash, if it generated the salt for you there’s a chance you might ignore the salt and suddenly not be able to validate passwords.

Anyway…

The only way you could make these separate packages work dramatically together and without coupling them would be to use a universal type - probably a byte array - and at that point you lose most of the benefits of a strong type system. What are currently compile errors become runtime errors, which are much worse and harder to diagnose.

My suggestion to you would be to reframe your thinking a little, think less about how you can make different crates speak to each other and more about how you convert from one type to another - once you crack that, all of these integration problems will go away.

Rust is completely correct to be a dick about it as well. Type safety is there for a reason.

I don’t know why LTT are somehow the bad guys in this, they weren’t the only ones to realise that the extension messed with their affiliate links and it’s not like it’s a thing to publicly shout about every dropped sponsor.

I bet LTT has dropped plenty of sponsors without making a big public deal about it.

That’s not quite accurate.

The onion’s bid was technically lower overall, but they made an agreement with some of the victims of Jones’ harassment that would make them better off overall.

Essentially one group is legally owed 97% of the proceeds of the sale while everyone else gets what’s left. The agreement was that instead of a 97:3 split, the smaller group gets a bigger payout and the larger group gets a cut of future ad revenue.

Everybody wins in this arrangement, except Alex Jones. So everyone wins.

We’re not getting out of this unscathed.

The infighting and arguing is, at best, the grifters trying to secure the best grift for themselves at the expense of everyone else.

Don’t worry about not having any insights, I still valve-ued the pun.

Whoops 😅

I agree this is probably overall a good thing, but I worry if this bacteria thrives due to the amount of plastic around what that would mean for the amount of CO2 produced.

Genuinely forgot Obama was in his 60’s, fuck I’d be glad to be that fit in my 40’s.

People blame Google for the death of jabber because of one blog post from a disgruntled contributor but the truth is jabber was never popular and Google chat died as well.

Jabber was a mess, most of the clients were barely compatible with Each other and it was a wild west of feature support. Some clients were well featured with the ability to send richer messages, but typically only worked with a specific server and the same clients. Jabber did a crap job at making sure clients and servers interacted properly with each other and didn’t push the standards quickly enough, forcing clients to do their own thing.

Which is all Google did, they went their own way because nobody used jabber and the interoperability was causing more harm than good. It didn’t work, Google talk died and many years later clients like WhatsApp took over instead.

I’m on the side of “automate it all and stop whining”, but I do think it’s important not to so readily dismiss the thoughts and opinions of those this directly affects in favour of the opinions of the security researchers pushing the change.

There are some legitimate issues with certain systems that aren’t easily automated today. The issue is with those systems needing to be modernised, but there isn’t a big push for that.

Made with Layers (Thomas Sanladerer)

TL;DW the stuttering is also present on console and doesn’t appear to be shader compilation.

Who cares? If even just one person on the fence sees the support Walz has in a community he cares about, then the rally did its job.

Nah this isn’t usual Nintendo bullshit, this guy was installing pirated games as part of his mods - he’s brought this on himself.

Yeah, really want musk to buy it…

I fully expect Nintendo to flip the switch 2 into switch 1 mode for that backwards compatibility, then charge extra for switch 2 enhanced titles.

It’s just the low effort anti-user kind of bullshit I expect from them now.

Yup I’m with you here. I love KBM and it’s my preferred way to play for most games, but when it comes to driving I’d much prefer a controller with analogue triggers and a stick (unless it’s a sim racer, in which case a wheel of course) for that extra precision.

Unfortunately I can’t think of a good design to give that level of control to just one hand. Analogue keys are a thing but they sound awful, nowhere near enough precision due to the short travel of them.

Call him Tantrum Trump or something

I’m devastated that they’re not working on a sequel at all, it was such a fun and refreshing game.