The funny thing is, although it is a bogus "bug" report, they treated it like it was real.

In any case, Mozilla only collects anonymized data by default. And you can happily, quickly, and easily turn that off and it will turn it off and it will remember that across updates.

The problem isn't setting the pointer to 0, it's forgetting to free that pointer. If you wrote the value zero into it, you either did it accidentally, or, you meant to, which you'll find on review. I would add a comment above where you set the pointer to zero, explaining why it's being to set to zero. It wouldn't recommend randomly overwriting variables and pointers, unless you're doing something obvious with line of sight. A good rule of thumb is 50% of your code base should be comment, for that reason.

Do I set things to null for garbage collectors? Usually, depending on the language, when I'm done with them, since it marks the memory as truly free, and generally results in better garbage collection. In TypeScript / JavaScript it's generally a good policy to intentionally mark your structures as free, when you're done with them.

Seatbelts are a safety device, but they don't guarantee you can't get injured in a car accident. The issue is: Rust developers treat the seatbelt as accident prevention when it's not. Unsafe is the same as not putting the seatbelt on, but then claiming it's the same as being accident safe anyway, since someone else is wearing a seatbelt. If you doubt they think that, look up Lunduke, and read or watch his Rust coverage, they absolutely believe that Rust is some kind of magical language that makes the concept of bugs impossible.

I'll even settle this pointless argument if instead of memory safety, we just call it's reasonable memory assurance, which is more accurate.

>"For all they keep doing, the one thing they can't seem to do is make a checkbox to stop being harassed about updates."

You literally post this on every article about Firefox. Aren't you tired yet? I have replied numerous times that they are *NEVER* going to do that. And then I pointed you to using policies, which will disable updates.

Once again showing the world you guess and bullshit with authority while not doing the bare minimum to educate yourself. Or do you think 4MB is 20% of 84MB?

If you're going to "help" someone, be right for a change. The screwed up symbol was the multiplication symbol. It's 20x less, or 5% of the original memory use. Stop spreading your ignorance.

I remember it was a Shakespeare play. "full of sound and fury. Signifying nothing"

If features that don't impact you and you can ignore while browsing impact you it's not a dedicated mode you need, it's ADHD medication.

We're sick of GNU Linux. We're making NEW Linux.

I've never met a highly skilled person who is perfect. Neither have you, you may just pretend you have.

No one said rust is magic. But but attempting to claim that whole world of memory safety issues being resolved is somehow countered by a single vulnerability is not just dumb, it's mindbogglingly stupid.

Rust isn't perfect. But claiming the old tools were is just spectacularly ignorant, especially given the recent history of CVEs related to those "well-working, _old_ tools".

Rather than your dumb fucking US vs THEM approach, how about you advocate for both sides to improve their code?

So if you restart Firefox (at which point the process and its resources are released by the OS) and it doesn't fix your memory problems, what makes you say Firefox has a leak?

And just what do you suppose a browser that already browses and has a plugin system to customise your browsing do to improve the browser?

People who don't understand history think the idea of a currency free from any manipulation by an economic agenda is a good thing. The reality is very different. You only need to look to major economic depressions during times when some countries still had currencies backed by gold or silver. The inability to control the economy through monetary supply caused those specific countries to suffer from economic depression far longer than other countries.

The long timing and severity of the great depression for the USA, France, and Belgium is widely acknowledged to be caused by them switching back to a gold standard after WWI. In fact several countries floated their currency to enact economic controls (France) specifically because there was no other way for them to get out of depression.

But please, tell us who much you want to fuck yourself with your silly math cosplaying as a currency.

That is an incredibly dumb assessment precisely because you completely failed to address the problem of the cable. The number of people who have accidentally ripped their headsets from the head due to the cable is near enough to 100%. A very very significant portion of people have damaged their cable or their headset, often beyond repair. The defining failure mode of the Rift CV1 wasn't the headset, but the fact that no replacement cables are available. Heck one of my friends ruined his motherboard thanks to yanking the cable with his arm mid game and reefing the USB port straight off the PCB. I ruined one cable just sitting on my arse when it was run over by the wheels of my chair one too many times.

The people who strived to eliminate the cable are the opposite of idiots. They addressed a very real problem. I loved my original Oculus Rift. I loved my Rift S, but wholly fucking shit did a whole world of usability open when that god fucking awful experience of being tethered and tangled was eliminated. And I played most of my games sitting on my arse.

You are not most people, and clearly you've never met or conversed with most people. Get out, spend a bit of time on VR dedicated forums, or even just reddit. You'll find your opinion is in the strong minority. Side by side latency comparison is useless. The question is does it work for the use case or does it not. The existence of 144Hz+ gaming monitors doesn't mean that most people are perfectly fine gaming at 60Hz (in fact the majority of people are).

Latency has zero to do with why VR "couldn't break into the mainstream". At least not since Oculus resolved the motion sickness issue caused by latency back in 2013. By the way VR headsets have well and truly outsold the Nintendo 64. So if you don't consider that mainstream it's worth noting you also didn't consider a ground breaking and highly successful and popular gaming console mainstream either. I really question either your knowledge of the industry, or your disingenuous use of the term "mainstream".

Bitcoin isn't a currency in the sovereign sense, but it is an intangible commodity. It's value is defined by supply and demand. As long as someone is willing to pay $76k (or the equivalent in goods or services), it's "worth" $76k regardless of your personal opinion of its legitimacy.

I don't personally consider art less than a century old "worth" the millions it sells for, but someone does, and that's all that matters.