• 0 Posts
  • 20 Comments
Joined 6 months ago
cake
Cake day: March 3rd, 2026

help-circle

  • I think the best analogy to highlight the drawbacks of Rust is to say it’s like “Good test coverage.”. If you read that as 100% test coverage you can spend a lot of time doing some trivial overhead that probably isn’t doing a whole lot. But, if you have half a brain it’s probably not particularly harmful. If you read that as effective test coverage, you probably know the problem quite well and it’s probably some overhead, but you get to feel a bit more confident and have some executable documentation.

    Neither of which I have heard to be useful or converted in the game industry so it sounds like a waste of time.

    That said, if you’re like me and that overhead sounds nice, then you might like Rust :P



  • The edge case is software development, for the bog standard stuff I write at work it probably helps me get work done about 15%-30% faster and with costs of $200-$400 USD a month the math actually works out. At current prices anyway. Also the electricity costs of running open weight models is even cheaper and if there is a pop HW prices may make that an obvious choice too. The worst case IMO would be a slow boil of prices to recoup the unsustainable growth then a slow decline to wherever normal ends up. In that case everyone is left indignant.














  • My take is that it is all subjective, I feel like I busted ass, I feel like a god interviewed, I feel like it was my lucky socks. Without a study and metrics we can’t objectively measure reliably, but that would be overkill for every little thing. So we take our subjective shortcuts and move on. My advice would be focus on the sentiment, “that’s impressive, it’s good that hard work/gods intervention/lucky socks helped that outcome, because it seems so surreal otherwise.”. That or have the heart to heart and put in the effort to align if it’s important and they are important to you.