Yes - I was only talking about when a person removes some code from use, removing the code as well as the call to the code. I wasn't meaning the compiler at all (although it would be nice if the compiler could autodetect it, as you say, that could become tricky).
I don't understand - wouldn't this be observable by the person making the change? They used to call this function / use this class and now they don't any more? Even if it's inside a conditional compilation block.
This is how I hope the world will continue to be, because then programming, which is one of the most enjoyable things ever, may remain a human task, assisted by AI and other tools.
That makes total sense (though it would be nice if it could do that detected, I suppose), but what makes less sense to me is the accumulation of unnecessary code (and presumably unit tests for that code) that isn't removed as soon as it's no longer needed.
> I’ve cut over 11,000 lines of completely dead code from Bun. I can’t think of another project whose codebase was so neglected as to reach 11K lines of dead code. I’ve also rewritten and modernized parts of the codebase, trying to rely more on Zig’s stdlib. In the process, countless bugs have also been fixed.
This is astonishing. Is anyone else surprised at this dead code figure? Is it a feature of large projects I've just never noticed?
My big discovery a few years ago was uninstalling apps, especially social media apps. I don't mind the platforms, but removing their ability to ping notifications up was massive. I watch some people just get their phone out to dismiss a load of notifications for 20-30 seconds. It's a chore now. I think limiting notifications is the best thing you can do, on your phone and your watch.
> They're just text behind the scenes, so you can copy them if you really want to. KeepassX lets you do it, and got into a kerfuffle about it.[1]
Yes - the kerfuffle is broadly I think the fact that it negates the main advantage of passkeys: people can't be tricked into pasting them into a fake login screen.
> It's an impossible design. It's all just obfuscation, most of which is confusing to users.
I agree - they're explained in a really odd way, and I think that's because they're a technology with multiple interaction patterns, rather than a single thing like a password. E.g. your fingerprint on your Mac is implemented as a passkey, or clicking on a browser passkey is also a passkey, or using a password manager via a different UI is also a passkey, or touching a Yubikey is also a passkey. The underlying mechanism (passkey) probably has been surfaced more than it should've been.
True. I think there are two new issues this cycle:
1. They are testing what the market will bear. Ubisoft's silly "quadruple-A game" rhetoric and executives saying "people will have to get used to $100 games" is them testing the water. This should pull back, as most people don't want games that cost that much, unless they're really amazing. They aren't (currently). I imagine this same thinking is going on in hardware-land.
2. Current RAM/GFx card prices are driving up prices all round. It should still be true that for the same spec, console components should get cheaper over time, but I can imagine it's less of an effect at the moment with all the AI data centres hoovering up manufacturing capacity.
That's one thing. The other is price. Consoles can be sold at a loss, particularly early in their 10-year cycle, when early on the loss is high, but close to the end of the cycle the loss is minimal, and so they appear much cheaper.
I've had a few OnePlus phones - currently a Nord 4 - and have always found them good value for money. Early OnePluses (I think I had a 2 or 3 originally) were incredible value. Also, very fast charging and almost stock Android are lovely features.
I don't understand why you don't like them, because you haven't said!
3D-Secure long predates apps, including in the UK. I had to work on a Government Gateway integration for local council payments in the mid 2000s that included 3D-Secure. I still see it today, although it normally now results in a ping to an app approval.
Indeed. It's the same principle[0] the other way too - start a timer from user typing for an autocomplete function and only refetch after the timer expires.
Oh - that's interesting too! But I meant more as a frontend across various integrations a business might have. E.g. having a bot that tells you if your CI failed is currently likely surfaced inside Teams or Slack. Having an internal chat service feels like a big win so companies don't need to integrate private companies' tooling so deeply.
Would a better example be Python's inline if else construction?