• 0 Posts
  • 26 Comments
Joined 1 year ago
cake
Cake day: July 23rd, 2023

help-circle




  • It’s reeeaaally good imo, but also a freaking time machine. You start to play it, and 1 hour later you traveled like 10 hours into the future.

    To be a bit more serious, the game has a very nice and cozy vibe, an interesting construction system with buildings on top of other buildings and intricate road and energy transmission planning, great water mechanics, and a good economy and survival loop. You can spend hours trying to figure out an optimal way to stack and connect certain buildings, and you have to be really careful about when to expand, cut back, or build more production and storage, because the next drought or bad water season could very well be your last!

    One thing I really don’t like is that you kinda have to play it with the time sped up, because many things just take a ridiculously long time to build. It also gets much easier once you manage to get your water supply under control, almost nullifying the survival mechanics.




  • I like to do two kinds of comments:

    • Summarize and explain larger parts of code at the top of classes and methods. What is their purpose, how do they tackle the problem, how should they be used, and so on.
    • Add labels/subtitles to smaller chunks of code (maybe 4-10 lines) so people can quickly navigate them without having to read line by line. Stuff like “Loading data from X”, “Converting from X to Y”, “Handling case X”. Occasionally I’ll slip in a “because …” to explain unusual or unexpected circumstances, e.g. an API doesn’t follow expected standards or its own documentation. Chunks requiring more explanation than that should probably be extracted into separate methods.

    There is no need to explain what every line of code is doing, coders can read the code itself for that. Instead focus on what part of the overall task a certain chunk of code is handling, and on things that might actually need explaining.





  • shrugal@lemm.eetoMemes@lemmy.ml***
    link
    fedilink
    arrow-up
    1
    ·
    edit-2
    11 months ago

    Do you have anything better to contribute to solve the YT problem than what I have contributed in this thread?

    Apparently pointing out false or at least misleading claims, instead of making them.

    Our servers are secured with SHA-384 Signature Algorithm

    This is a meaningless sentence.

    meaning we cant see the videos you watching, things you search

    This is just not true. Go to a video on their site, the browser requests the video id as cleartext from their server. Search for something, your browser sends the search term as cleartext as well. There is nothing encrypted beyond the standard, it’s all visible to them.

    This is how all YT proxy sites do it, but they don’t claim to use some sort of special encryption. It’s widely accepted that you have to put some amount of trust into whoever is hosting the instance you are using, because they can see the things you watch and search for.



  • shrugal@lemm.eetoMemes@lemmy.ml***
    link
    fedilink
    arrow-up
    4
    ·
    edit-2
    11 months ago

    What the hell is an encrypted server? What’s special about SHA-384, where do they use it to improve privacy? Please don’t bullshit people with random IT terms.

    Glancing at the code, this is just another YT proxy. Ofc they have your user info, they just choose to only store aggregated data.


  • The problem is that they don’t communicate this and still ask for the full price.

    Imagine I’m a gamer who wants to buy and play a working game today, not in half a year. Nothing on their store page indicates that the game isn’t in a playable state yet, so I’d pay full price for a game I can’t actually play. That’s misleading at best, and a downright fraud at worst.

    They could easily fix this by delaying the game or launching it as early access for people who don’t mind playtesting a half-finished game, but they didn’t.




  • What’s confusing about that? It’s null, just two different kinds with slightly different meanings. Is having two boolean values also confusing?! Should we simplify it?

    I mean I can get behind trying to remove null entirely and replacing it with better concepts, but I cannot understand why having one more null value suddenly makes it confusing. You don’t even have to care in 95% of the cases, and it can be useful in the other 5%.

    Honestly, it looks more like some kind of misguided purism to me.