• 0 Posts
  • 28 Comments
Joined 2 years ago
cake
Cake day: June 12th, 2023

help-circle





  • I think the idea is that for one, the front screen can be smaller and more easily used because the main screen is bigger. On the other hand, the main screen is bigger, allowing it to act as a tablet without having to carry a second device. On top of all that, it still fits in your pocket.



  • wastes literal resources extracted from our planet to fix or replace the car

    This is the big part for me. The car exists. It’s made. That can’t be undone. Making it unsafe (from vandalism) to drive, the only remaining option is for it to go to waste, for the most part. Sure, it can be recycled, but that’s still wasteful compared to continuing to use it.





  • Okay, this I can explain. New Microsoft Teams is the new app. It was also installed before the person installed the old Teams. “Microsoft Teams New” is actually just “Microsoft Teams”. The “new” is part of the Windows UI, not the name. It just denotes that it’s a new option for opening “msteams” links. It’s a new option because it was recently installed. The real solution to this is just don’t install two different Teams clients. The old one is actually retired now so that’s not an option and it’s a solved issue.




  • I don’t know Rust, I’m just here to chill. I can tell you what I would do, and have done, in PowerShell to solve this. From there you can translate that to Rust.

    Let’s go with your limit of 200 requests per second. At the start of the script, I create a stopwatch. Literally, a stopwatch that’s tied to real world time and can be reset. Then, I have a variable that counts my requests. Every time I make a request, I increment it. Before every request, I check if the variable is 200. If it is, check the timer to see if a second has passed. If not, calculate how much time is left until a second has passed and sleep for that amount of time. After doing that check/sleep, reset the request counter and the stopwatch. From there, continue on.