• 0 Posts
  • 37 Comments
Joined 1 year ago
cake
Cake day: July 24th, 2023

help-circle


  • I do not get why it would work in that case. I assume the scenario is someone with a bike coming, doing theft, then leaving with the same bike.

    Therefore there will be a period without bike, then a period with bike, then a period without bike again.

    Let’s assume there is no bike on the particular moment viewed. How do you know whether it occured before or after the theft? If you make the wrong decision, you get stuck on an endless binary search… Unless you take note at each timestamp where you made the decision, draw a tree of timestamps, and go back the tree if your search is fruitless but that’s much more complicated than what this post says.


  • For a first time don’t try to get the strongest character possible. It’s a time sink to do that. Usually the main campaign of games are beatable even if you screw up something. The worst that can happen is you backtracking a bit and spending time to level up before doing the next quest.

    When you played the game once and got used to the mechanics you can make a 2nd char and plan it more deeply ahead if you wish. You know what mechanics you like so the prospect of finding what to invest in what is worth etc… becomes more streamlined. But you don’t have to. You can just be happy to have finished the game and call it a day.

    That’s what I did for Diablo 4. After the main campaign I did not feel like venturing more into the game or making another character so I started playing another game. If you really want to 100% a game it does require a ton of time and planning but you don’t have to




  • About your specific example I find the Rust code to be much simpler to understand than your equivalent Golang code…

    To understand the Rust code I just have to understand each case. 0…1 returns false. Ok. 2…n returns true iff no divider was found between 2 and n-1. Ok the function is primality test

    The Golang code is much harder. I do not take into account the division by 2 because its not part of the original Rust code.

    A for loop starting at 2 that look for divisors. Then the return value > 1. Why is it OK to just return value > 1? Oh that’s because the loop did not return. Why did it not? Either no dividor was found or we did not get into the loop at all. If value > 1 we have the guarantee the loop was executed so it’s really a primal number. If value <= 1 it is either 0 or 1 which are not primal. Ok, so we return value > 1.

    I think people dislike Rust because it has a lot of functional languages constructs and people are not used to code in functional languages.

    Whatever you fight in Rust you end up saving time by avoiding runtime bugs that would have plagued your productivity anyway. I’d much rather have a language with a hard entry but with solid and maintainable code rather than fast-written spaghetti that no one knows what it is supposed to do 2 years after.



  • The Christian Bible’s Matthew 24 had a prophecy that is about to become historical-fact, in the coming decade.

    Here’s a decent version of it:

    https://www.biblegateway.com/passage/?search=matt+24&amp;version=AMPC

    That bit around verses 15-20 is the pertinent area.

    Simply wait 1 decade, and see: if Israel still exists, as a country, in 2033, I’ll eat a hat.

    The nice thing about prophecies is that they can never be proven to be false. Indeed, one would have to examine the future to prove it wrong. Which is either impossible or unrealistic.

    Me too I can make a ton of prophecies and claim they will be eventually right. I will never be wrong.

    Let’s see. Let me prophesize that:

    • The US will cease to exist
    • We will encounter aliens
    • See where you are living right now? Eventually, it will be filled with lava.
    • See where you are living right now? Eventually, it will be flooded with water.
    • A giant comet populated with nyan cats will crash on Earth

    However, you can be sure that in 2033 I will come back in this thread and have you eat a hat. Marking the date and the link in my calendar. If lemmy is still alive, that is



  • Yeah exactly. Here follows some spoiler for those who have never played Dark Souls

    spoiler

    Once you escape from the asylum you can get to the catacombs right away. I did that and got my ass kicked so I figured I was not supposed to get there first.

    So I went up towards the upper Bell. Which I did ring. But then afterwards it looked so clear to me, especially as you unlock the shortcut to Firelink : yes ! The other bell must be down in the catacombs! So I headed there.

    I struggled a lot to handle all the monsters. I kept going until the valley where you face skeletons on wheels and the black Knight. I figured “no something isn’t right, I don’t think the game is supposed to be that hard. There are tips on the ground about using a divine weapon but I don’t even know how to get one.”. I read a post online and figured I went the wrong way… Once again

    Once I fixed that and went the right way things got significantly easier. I heard how some players literally got down to the catacombs from the get go and somehow managed to get to the boss door only to be met by a yellow fog that can’t be passed, and how they struggled to get back to firelink without getting killed…

    The bottom line is that I think you need to have someone telling you where not to go to really enjoy Dark souls. Because its not obvious whether you die because of your incompetence or just because you were not supposed to be there right now. I wouldn’t say its bad design though - but it’s not for everyone for sure





  • They are for providing special hardware for Neural Network inference (most likely convolutional). Meaning they provide a bunch of matrix multiplication capabilities and other operations that are required for executing a neural network.

    Look at this page for more info : https://www.nvidia.com/en-us/data-center/tensor-cores/

    They can be leveraged for generative AI needs. And I bet that’s how Nvidia provides the feature of automatic upscaling - it’s not the game that does it, it’s literally the graphic cards that does it. Leveraging AI of video games (like using the core to generate text like ChatGPT) is another matter - you want to have a game that works on all platforms even those that do not have such cores. Having code that says “if it has such cores execute that code on them. Otherwise execute it on CPU” is possible but imo that is more the domain of the computational libraries or the game engine - not the game developer (unless that developer develops its own engine)

    But my point is that it’s not as simple as “just have each core implement an AI for my game”. These cores are just accelerators of matrix multiplication operations. Which are themselves used in generative AI. They need to be leveraged within the game dev software ecosystem before the game dev can use those features.





  • That’s true especially in gaming circles.

    There are big misconceptions about game development jobs. People tend to think that implementing X or Y feature “surely can’t be that hard”. They have absolutely zero experience in game design or game programming and yet they take on such a condescending level when you read their posts.

    Programming is hard. Balancing is hard. Developing a game while you have a whole player base against you is hard. The game industry is most infamously known for its crunch times and high turnover rates. And yet players do not respect that.

    Whenever a game gets released at all, it’s such a ton of work that have been done. Even if the game turns out to be not as fun as people wanted. Or even if there are bugs. In fact, i am sure that half of the people that complain aggressively will never do something that impressive in their life, ever.

    We should be in awe and respect our fellow devs because this job is one of pure passion.