HN user

ShinTakuya

593 karma
Posts1
Comments296
View on HN

Yeah I never get the "we knew about it internally" excuse. I can understand if another reporter got to it on the same day and they were in the process of mitigating, but even then they should have to prove it somehow.

I'm sure someone will tell me why I'm wrong but it feels like they're just dodging payouts. Reduces trust and motivation to report it.

I don't support this idea of rewriting everything in Rust but the answer to your question should be fairly obvious. Rust that compiles will generally be stable assuming you don't do a bunch of unwraps and panics. C that compiles can seem fine until it isn't.

LLMs still aren't as good at detecting C memory management issues as an experienced developer. With Rust, that doesn't matter as much because generally the compiler will tell the LLM when it's wrong.

This is all well and good in theory, but the number of times I've seen tests that don't actually test what they say they're testing is hard to count. Yes even when you encourage the developers to ensure the test fails first and do TDD. Tests help you ship with confidence but there's usually at least a few that are just passing by pure luck.

So no, I wouldn't judge a rewrite as being equal just because it passes the tests. That said, I don't think that means you shouldn't do it. You just have to be pragmatic about it.

Except all major social media sites are also corporations with their own interests. I'd rather the business model of traditional media that rides on journalistic reputation to a recommendation feed where the only job of it is to keep you on the site, especially when said feed can easily be manipulated.

No media organisation is perfect but your description of social media as some nirvana of decentralised truth is very questionable.

For what it's worth, this is commonplace in Australia too. I feel like you're describing a general safe country thing. I've lived in Japan so I know it's probably one of the safest places in the world, but I feel like what this thread describes is more US/Canada/some Euro countries being particularly dangerous, and not Japan being uniquely safe.

I think the main reason more time might be spent thinking is because there's relatively less training data on Haskell out in the wild, meaning an agent may have to check back and forth with static analysis to figure out what's valid.

Compact syntax is generally only a good thing for LLMs because it saves context windows and tokens.

Plenty of valid reasons to pick C, memory safety isn't a reason to trade off all other possible benefits. One big reason is portability, you can't compile Rust for example for certain targets.

I mean, supply chain attacks are a thing that could have happened even in the earlier days. Linux almost got backdoored in 2003.

Also with the number of remote code execution exploits that have occurred in Web browsers over the years it's hard to know for sure if what you installed hasn't been hijacked unless you spent all your time on gnu.org

You're assuming performance has been the core priority, or even a priority at all, and I think this is a bad assumption to make. I would estimate a much smaller number of people-months of work if I were you.

Dev users assume the only problem a product can solve is performance, when there is a lot more than that in reality.

As far as I'm aware it keeps a history of the frequency you visit each directory so yes it will select the one you've visited more often (assuming you don't always start at the base one and work your way down).

There's nothing inherent about C++ that makes it more suited than Rust for game engines though, Rust supports careful management of memory too. Of course, nothing besides inertia (i.e. Libs, existing code, etc.). And that of course is more than big enough of a reason to stick with it.

While I agree they shouldn't be putting their money towards political causes, the scrutiny of the budget is also political in nature. Of the $400 million in expenses, only around $15 million went to executives, and around $1 million went to the DEI stuff. The rest was split evenly between developing and marketing Firefox, which is basically what you were criticising them on not doing.

If they got rid of all the executives and DEI, they could increase the other budgets by 2%. There is 0 chance that the 2% extra budget could help the market share and development in any significant way.

And if you don't pay executives enough, you get worse executives who make worse decisions because the good ones will go to other companies. So you'll be complaining even more if the $15 million executive pay got dropped.

So in short: I agree Mozilla shouldn't get involved in politics. Despite this, no reasonable person could look at the numbers and conclude it's having a material effect on the destiny of Firefox.

Keep in mind that my own knowledge of physics is very rusty, so some of this is definitely making bad assumptions.

The density in the singularity (centre) of the black hole is in theory infinite. But the event horizon (the part where light no longer escapes) is not the singularity, it's simply where the gravity becomes so strong that light can't escape.

Think of it as the sun vs the planets - we're not in the sun, but we still feel its effects. The density of the solar system isn't the same as the density of the sun. This is bad analogy because the same mathematics/physics doesn't apply, but it should help you get the general picture based on your original assumption.

In general, the heavier the black hole, the less dense it is when measured from the event horizon. So in theory, it's possible to have a black hole so heavy that the event horizon contains the entire universe. In fact, the known universe is heavy enough to be a black hole 3 times the known radius of the universe. But as we know from stars that turn into black holes, just because something is heavy enough to be a black hole, doesn't mean it is one yet.

Not sure where you people are getting these multi decade toasters, I need to replace mine every 5-10 years. Obviously not the worst case of e-waste either way but 1 or 2 seems like a severe underestimate but that could just be my own experience.

Usually a heating element dies or similar. If it were easier to replace the heating elements I'd think it'd help reduce waste, but as you and others have noted, that wasn't the point of the article.