• 0 Posts
  • 21 Comments
Joined 1 year ago
cake
Cake day: June 5th, 2023

help-circle

  • Most clients are web browsers and support for torrents in http is the same as for every other file.

    So that would only give us a use for torrents as a form of content distribution plattform to get the actual files closer to the client.

    In cases where we have actual non browser clients: i like to curate what i am distributing and don’t want to distribute anything i happen stumble upon or would you be willing to store and more importantly share everything you find on 4chan or that might show up in your mastodon feed?



  • Access control and offering a sound interface.

    You don’t need getters and setters if every attribute is public, but you might want to make sure attributes are accessed in a specific way or a change to an object has to trigger something, or the change has to wait until the object is done with something. Java just has tools to enforce a user of your objects to access its attributes through the methods you designed for that. It’s a safeguard against unintended side effects, to only open up inner workings of a class as littles as necessary.

    In a language without something like private attributes you’d have to account for far more ways someone might mutate the state of objects created by your code, it opens you up to far more possible mistakes.














  • Ember Knights is a rogue lite heavily inspired by the gameplay of hades. Supports up to 4 players.

    Plate Up is somewhat simmiliar to overcooked, but is more about process optimisation and not about dealing with the oddities of a stage.

    Most lego games also offer local coop and are good fun.

    30xx is a roguelite with gameplay simmiliar to MegaMan X that can be played by 2 players.

    Towerfall Ascension is also worth a look.

    Hell Divers is also a great game, but it had sound issues(strange echoes of some enemy sounds) last time i tried.




  • I guess some lessons need to be learned through pain.

    • Commiting regulary.
    • Following the branch rules.
    • writing tests.
    • writing tests, that test the desired not the current behaviour
    • refactoring your code.
    • not refactoring code, you don’t understand nor have tests for.
    • actually reading code before merging a pr.
    • not pulling in 23 unmantained libraries to solve a simple problem.
    • keeping your dependencies up to date.
    • that dirty hack will make your life harder.

    Yes, all those hurt. They sometimes still do, most of us are not machines that turn caffeine into code and we are never as clever as we think we are.