• 0 Posts
  • 12 Comments
Joined 1 year ago
cake
Cake day: July 1st, 2023

help-circle
  • On thinking about this a bit more, I feel like you may be expecting the system to handle situations where your business requirement needs the new field to be used now, but used to work without this field before. Based on the example you provided, I am imagining something like a getTasksForUser functionality which previously might have just been filtering on userId but if the business now says that this functionality should now return tasks sorted by priority, you expect the system to somehow know the business requirement and force the developer to use this new priority field ?

    If that’s what you’re hoping for, the problem is harder to solve although not impossible. Assuming the example as above , you could maybe just inject the priority field at the data access layer . Another way would be to make the modified entity private and expose a facade with helper functions that are exposed. Now when code that previously used to rely on the entity inevitably breaks , you can replace those usages with usage specific functions exposed from the facade and since the entity is now accessible only from the facade, you can easily update all usages within the facade and make sure no one can miss passing the priority field since the entity is private to the facade and all functions in the facade are known to use the new field.



  • I am still confused about what OP is looking for. Even in typescript, if a new field is added and not used in other places, compilation will fail. Unless OP explicitly marks the field as optional.

    There’s also the possibility that the codebase is littered with the “any” keyword (I’m not saying OP is doing it but I’ve definitely seen plenty of codebases that do this). If someone says they’re using typescript but their code is full of “any” keywords, they’re not using typescript. They’re just using plain JavaScript at that point.



  • Got it. I think I see what you mean but I’m not sure if I just got lucky or if the games I play have accounted for it but I am able to just suspend and resume without issue on my windows handheld. Unless we have different definitions for what we call suspend. When I want to suspend, I usually pause the game and push the power button once and leave it like that for hours and then come back and push the power button again to turn the screen on and resume playing. I’ve done the same thing on a steam deck and it works similarly there as well so I’ve not noticed any difference. Unless you mean the ability to somehow take a snapshot of the running games state and store in on non volatile disk and completely power down and turn it back on to resume. If steam deck can do that out of the box, that is indeed impressive.


  • I understand this is lemmy and comments like this are to be expected but does it have to be for every post that is related to windows ? In general, I agree that windows has quite a few drawbacks compared to Linux but for gaming pcs, once the initial setup is done, you can just launch a game and it just works without any tinkering. I don’t understand the argument that people should throw away a whole OS and switch to a different one and lose the ability to play a bunch of games in the process. Doesn’t context matter when discussing the pros and cons of something? Or is there some massive drawback to windows for gaming handhelds that I’m not seeing ? Or is there some magic sauce in Linux that makes every single game playable without tinkering ?