You did 200k years. You need to do 200k years as seconds (the 6.311e12 they mentioned). Their math is right.

Not sure why you’re acting like they claimed to invent the logarithm, either…

There’s also that moment in No Man’s Sky when you figure out what the story is implying. I’m being vague here to not spoil it for anyone. But it doesn’t have a single point in time where you piece it together. There’s a growing amount of evidence before the game outright tells you what’s going on.

Let’s not pretend people acknowledge warnings, though. It’s a popular meme that projects will have hundreds of warnings and that devs will ignore them all.

There’s a perfectly valid use case for opinionated languages that don’t let you get away with that. It’s also similar to how go has gofmt to enforce a consistent formatting.

Honestly, I’ve been using Go for years and this unused variable error rarely comes up. When it does, it’s trivial to resolve. But the error has saved me from bugs more often than it has wasted my time. Most commonly when you declare a new variable in a narrower scope when you intended to assign to the variable of the same name (since Go has separate declare vs assign operators).

And I’m upvoting you because while I completely disagree with your comment, I’m in gratitude of your effort and we will always need new comments.