• 0 Posts
  • 450 Comments
Joined 3 years ago
cake
Cake day: June 17th, 2023

help-circle
  • The time to beat a game is generally for the main story if you don’t take ages doing other things. Quite often with side quests or other non essential steps like collecting things or trying to 100% a game it will take way longer then the estimated time to complete. This is epically true for more open-world type of games with lots of places to explore.






  • I don’t think this is the win we want. Sounds like palwprld change the game to no longer infringe on Nintendo copyright claims. So Nintendo can no longer seek an injunction. They are still seeking damages.

    I really want to see the copyright claims be challenged in court so we know where we stand. Rather then the continual settling out of court because Nintendo has more money.

    It doesn’t sound like Nintendo are on track to win or lose this. Just Palworld changed the game to limit the impact of the lawsuit. Which is in a way a small win for Nintendo.








  • Yeah, Steam may be effectively a monopoly, but it’s because nobody else really wants to compete with them at their level.

    Steam has two types of customers. Us the gamers where we can decide which platform to use. They have an effective monopoly on us because they provide a good service. But with a large game library we are locked into steam as well and cannot just switch to a different platform. If valve ever did decide to be evil then we are screwed.

    But developers are also customers of valve. And this is arguably where valve makes their money. They take a cut from the developers sales. Devs cannot just use a different platform without cutting out a huge userbase. This gives valve a real monopolistic control over developers.


  • Its hard to argue that 2 config files both multiple lines long is simpler then a single line in an existing file. Adding a service to cron is just simpler. But adding all the extra bit you are going to want on top increases the things you need to learn to do and configure correctly.

    IMO systemd timers are simpler to get right at a little bit more of an upfront cost to learning how they work. But cron is still simpler to just get something working without caring that much. I still find that ends up biting you in the longer term though though all the missing features you need to add manually on top of that one basic line you added.


  • Cron jobs are nice and simple to create. Until they go wrong then they are a pain in the ass. You need to manage logging yourself. If you forget you root mail will fill up your disk and crash the system. If you forget the mailto setting. If you remember it you justlose all logs and have no clue why something is not working. You need to redirect the output to a logfile yourself. And then risk filling up the disk with logs unless you remember to also set up logrotate. And you then still don’t know when something last ran or if it ran successfully.

    So many traps and that is just the logging side of things.