Did the citizens of that country take the loan? No Did they benefit at all from the loan? No Did the world bank make any effort to ensure the above were answered ‘yes’? No When you make a leveraged loan are you supposed to be guaranteed that the it was risk free? No

If leveraged loans could be made risk-free ‘breal your legs’ style the way the world bank does to countries, banks would be offering loans to every punter who wanted to bet on the dogs.

deleted by creator

No, I’m saying that when people run into strange bugs, sometimes they put together an issue (like the person behind cve-rs), and sometimes they quietly work around it because they’re busy.

Seeing as I don’t often trawl through issues on the language git, neither really involve notifying me specifically.

My lack of an anecdote does not equate to anecdotal evidence of no issue, just that I haven’t met every rust developer.

Yes, the problems rust is solving are already solved under different constraints. This is not a spicy take.

The world isn’t clamoring to turn a go app into rust specifically for the memory safety they both enjoy.

Systems applications are still almost exclusively written in C & C++, and they absolutely do run into memory bugs. All the time. I work with C almost exclusively for my day job (with shell and rust interspersed), and while tried and tested C programs have far fewer memory bugs than when they were first made, that means the bugs you do find are by their nature more painful to diagnose. Eliminating a whole class of problems in-language is absolutely worth the hype.

If someone did, why would I hear of it?

The code used in cve-rs is not that complicated, and it’s not out of the realm of possibility that somebody would use lifetimes like this if they had just enough knowledge to be dangerous.

I’m as much a rust evangelist as the next guy, but part of having excellent guard rails is loudly pointing out subtle breakages that can cause hard to diagnose issues.

They made a smart call that has probably increased the long term privacy of their users.

People were using port forwarding to host illegal shit, and governments were getting pissed off about it. Mullvad has been able to prove in court that they don’t keep logs, but that’s not a perfect deterrent; a properly motivated government, perhaps if somebody is using Mullvad to host CSAM, might attempt to legally force Mullvad to put logging in and add anti-canary clauses.

Preventing port forwarding keeps customers as consumers rather than hosters, and avoids this issue.

Not necessarily, plenty of good programs written in C89 for example.

With something that is heavily library dependent, having a more recent development stack may mean better maintained libraries but definitely not a sure thing.

I’m honestly more worried about science communicators projecting life-changing properties onto it because “superconductor”, and then the public coming away with “these scientists are all hyperbolic hacks”.

This looks a lot less like diamagnetism than the previous videos, but is still using way larger magnets than they should need; still very sceptical.

Also a reminder to anybody reading a news article about this: LK99 is likely a ceramic, so the attributes specifically for metallic superconductors would not apply.

The GPU driver should already be in mesa, no?