• 0 Posts
  • 13 Comments
Joined 1 year ago
cake
Cake day: July 2nd, 2023

help-circle



  • A given programming language often has limitations which are largely different than the limitations from others. This means that different languages are often used on different kinds of problems. Want something fast, use C. Want to write something quickly, use python. Want it to run on just about anything, use Java. And so on.

    So why don’t we make one ultimate one or a few that fulfill all needs? Well, partially because we haven’t figured out how to do that, but also it’s really easy to learn yet another language once your understand how they work. I can write in python, js, c, c++, c#, Java, kotlin, rust, perl, ruby, php, forth, lisp, and I could keep on going for quite a while. The underlying concepts are largely the same and so picking up a new language is no big deal (though being good at it is a bigger deal). We have so many because ultimately it just doesn’t really matter that we have so many.



  • Final fantasy 7. But for a different reason. I tried playing that game many times wayyy after it’s release but I just couldn’t get into it. But I got really big into final fantasy 6 and I got really big into other JRPGs, so it wasn’t that the gameplay was bad just that the 3d graphic hasn’t aged well. But I also played some pretty crusty PlayStation 1 games back in the day, so it’s not like if I didn’t play it at the right time I wouldn’t have loved it. But just cuz I didn’t play it around release, cuz I didn’t know about it I was a kid, kind of missed out on an entire thing.

    I like the remake but, I don’t think it’s the same.







  • I have a bad solution to this:

    1. measure the mean and std. of loading times for a given loading task on a wide variety of machines, store this
    2. when a user encounters a load that needs a bar (above a certain time threshold), compare their machine to those stored to get a mean/std
    3. go to your desired confidence level above the mean (say 99.9% of all cases) and use that as a loading time.
    4. progress the loading bar smoothly for that time. If the loading is done before that DO NOT end early, just keep going and record the new time to work it into the mean/std (which should probably be reported back to the dev and fetched by the user’s machine daily)
    5. If it goes over on time, just dismiss the loading screen just very very slowly transition to the game, and if its still not done just crash the game. If we cant have an accurate loading time we won’t have any loading time.

    This should annoy enough devs and users alike and make them admit that fake loading bars are better than accurate ones.


  • Anyone with experience with joysticks (these or regular ones), I have a weird backlash issue with my Steam Deck where if I pull the joystick all the way in one direction and release it, it will overshoot the center and go ever so slightly in the other direction, and weirdly enough its only a recent issue and did not crop up till this past month (after I let it sit for a month or so).

    I am going to eventually swap to the hall effect sticks cuz I like the idea, so my question is: Should I try to fix this issue in software (i.e. increase deadzones, would that be effective?), is there a quick hardware fix that I can do a without taking apart the Deck, or should I just go ahead and fastforward my timeline in getting and swapping to the Hall effect sticks? I figure if I have to open the Deck I might as well do the swap, but I want to put that off as long as I can.