• 1 Post
  • 237 Comments
Joined 3 years ago
cake
Cake day: June 15th, 2023

help-circle






  • I think you have done way more work than would be needed to learn Rust. I mean, it certainly is useful knowledge if you want to do any of those things in Rust, but it’s definitely not needed to learn Rust.

    The Book (the Rust language guide) assumes that you know some other language first, but you don’t need to be an expert in anything in order to start learning Rust. If you understand the basic concepts of branching, loops, recursion and function calls, you are good to go.

    There are of course other concepts you will encounter in Rust (like Algebraic Data Types, Polymorphism, Ownership,…), but those are all explained in the Rust Book, so there really is no need to learn them in advance.


  • The best part is the job opening…

    Actively use and promote AI-assisted development tools to increase team efficiency and code quality

    Probably the boss of the person who had to write the job opening demanded they include something about AI, and the person who wrote it decided to turn their sarcasm up to 100. The only way to make it more clear would have been sarcastic casing:

    Actively use and promote AI-assisted development tools to InCrEaSe TeAm EfFiCiEnCy AnD cOdE qUaLiTy









  • I’m willing to bet that it’s AI. It soft-contradicts itself quite often, emphasising that C++ is “Performance First”, but then also claiming stuff like “Rust achieves memory safety with zero runtime overhead”.

    Edit: What I am trying to say is that I have seen text like this in LLM output quite often, if the LLM is mixing text from different sources in its training data.

    Also, there is just wrong stuff in the text itself, not only in the conclusion. For instance the claim that Rust’s type system makes data races impossible. They are easier to avoid, but there is nothing stopping you from writing data races… Here, for instance, have a data race in safe Rust




  • There are several small differences between the Xbox 360 and the Xbox Series X gamepad. No single point by itself would be a very big difference, but overall it sums up. I have both gamepads in front of me, and will try to make a comparison:

    • The material of the Xbox 360 gamepad feels “better”. I can’t exactly say why, but I think it’s because of its smooth material on the bottom.
    • The Xbox 360 gamepad has bigger analogue sticks, with stronger springs.
    • Similarly, the triggers of the Xbox Series X gamepad are “weaker” than of the Xbox 360 gamepad.
    • I would have sworn that the Xbox Series X controller is a lot lighter too, but turns out, after weighing them both, that the Xbox 360 controller is slightly lighter. It does not feel this way though, with the Xbox 360 gamepad feeling way sturdier and heavier (but, as said, it’s actually lighter?!?).
    • The buttons on the Xbox 360 gamepad feel a lot smoother. They don’t make a “cheap, broken device” noise when being pressed.
      • This also applies to the D-Pad.

    I think the last point - the feeling when using the buttons and especially the D-Pad - is the most important one for me. On the Xbox 360 gamepad the buttons feel like actual buttons. On the Xbox Series X gamepad they sound and feel like a fidget toy. Using the D-Pad on the Xbox Series X gamepad is really annoying, because of the noise it makes.