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

help-circle



  • What I miss in the CLI, is proper structure in the text.

    For example, a good IDE will list all problems found with your code, ordered in a sensible way. If I then click in a problem, it expands, and I get to see the full text description of that error. I can then click on a file/line combo, and be directed immediately there.
    If I run CMake directly, I get kilobytes of error message dumped into a single blob of text.
    Colors, line prefixes, and separator lines attempt to bring some structure into this mess, but it still remains a big wall of text.
    It takes less effort for me to process the data presented to me by a good IDE, because it is organized and structured.

    Same thing with git commits/branches/tags.

    Same thing with diffs/merges.

    Almost ALL text data can be organized in some way. But most text data is not big enough or common enough, that it is worth our time and effort to structure it that well. I therefor see GUIs as tools for when you are doing something so commonly done, that the effort of structuring the data was worth it.






    1. Defeat boss in top-down hack-n-slash style combat with lots of abilities.
    2. Farm materials needed for the unlocks of the boss.
    3. Use unlocks to upgrade base/castle.
    4. Use upgraded base/castle to upgrade gear.
    5. Find bigger/better boss to defeat, and go to step 1.

    After every 3 or 4 bosses they introduce a new gameplay mechanic. More abilities, more dangers, potions, etc.
    Hence, you are always unlocking something that feels like progress.

    The castle building is also done nicely. You grow if from a couple of wooden palisades and a wooden coffin, to a multi layered castle with different rooms (for crafting bonuses), farming areas, a dungeon, servants that you can send on raids, and a lot of decoration options.