It is a strict improvement to be able to transfer data or charge at degraded speeds, compared to not being able to plug it in at all. Wanting all your cables to end up entirely incompatible just because you don't want to bother checking labels (modern cables come with clear ones, I have ones that clearly say 40Gbps/240w on them) is, frankly, silly.

At the same time, they did listen to the feedback and deliver. It now has a genuinely good interface for it where you don't have to opt out of everything, but can opt-in where you want it. It's not just a big off button, it's a general out-out including new features, but that then exposes individual opt-ins if you want for each feature. Most other browsers won't respond at all. Firefox is still by far the best browser out there for people who care about their privacy.

Especially on HN, Firefox just gets so much more hate than software that is way more user hostile for much less bad behaviour. I'm not saying we shouldn't hold it to a higher standard when that is what it's selling itself on: clearly we can't allow "not as bad" to let it slip into worse and worse, but at the same time, I don't understand how the narrative seems to trend towards "they are essentially the same as google" when that is so clearly not true (to be clear, not saying you are saying that in this post, just that's the vibe of HN's commentary as a whole).

(To be entirely clear, not because agents won't be a relevant thing, although certainly I have my doubts, but because I believe even if they are a relevant thing, requiring special allowances from sites undermines the whole point, and such things will only end up used by bad actors to mismatch what agents see to what humans see, and so will be intentionally ignored.)

As my comment made the case: it's not a simple addition, it's a trade-off, and I'm saying it should be thought about in those terms. I didn't find that was evident from what you said, I guess the "push back" framing was more negative than I intended.

By having obscurity you lose anther layer of security: public scrutiny. It's harder for security issues to remain if people can see them and point them out, more eyes mean more chances to catch problems.

There is also a cultural component: having to lay out what you are doing publicly means you can't just think "no one will know", and let something slide, which pushes you towards better security practices.

Of course, this doesn't mean obscurity is always going to be the worse choice, there are times it will offer more than it costs and it's particularly evident that in, for example, open source projects, a lot of the time the number of eyes on most code is low enough that "many eyes" is a bit misleading, but I think presenting it as a pure positive is wrong, obscurity has cost, even if you think it's worth it in some cases.

The bigger factor is probably that PCI-e tunnelling at most a ×4 link, while when you plug a GPU in you are generally doing so into a ×16 or at least ×8 slot, and very few GPUs target ×4.

It's normal and reasonable to discover someone who makes bad decisions is running something and decide that makes using it a higher risk for you. Sometimes you don't have a choice, but sometimes you do.

To make an obviously unproven and not universal observation: I feel like it's people who just like the google integration in Chrome and want an excuse to run it, even though they feel like they should use Firefox because it's more compatible with their world view, so they latch onto any issues Firefox has to go "see, they are all the same anyway", and then just repeat vague "Mozilla sucks" stuff.

I think game engine tooling tends to encourage bad code too, lots of game engine make it hard to do everything in code, rather things are special cased through UIs or magic in the engine, which means you often can't use all the normal language features, and have to do things in awkward ways to fit the tooling.

Of course, this varies a lot by engine.

It's weird seeing people just adding a few more "REALLY REALLY REALLY REALLY DON'T DO THAT" to the prompt and hoping, to me it's just an unacceptable risk, and any system using these needs to treat the entire LLM as untrusted the second you put any user input into the prompt.