[–] 1 point 9 months ago*

I don't think they mention maintenance burden specifically. Using a framework with packages means you have to track upgrades, do upgrades, check release notes, breaking changes, support and end of life cycles, license changes, etc. It's a have maintenance burden if you keep it live, even if you don't intend to make any changes.

Vanilla doesn't have this problem. Server-side has it too, but in a slightly different flavor.

The heavier and integrated the framework, and the more additional packages you include, the heavier the burden.

  • source
  • [–] 7 points 9 months ago (2 children)

    Why does nothing link to the content/MS page in question? Not this article, nor the Bluesky post or replies.

    I would have liked to see and verify the context, and explore the git history which should lead to some context that may give some context to what the author asks at the end: How did it come to be, with what ideas or goals, or justification, etc.


    The Bluesky replies mention(/claim) that the image has been replaced, now seemingly copying a graph from Atlassian docs.

  • source
  • [–] 3 points 9 months ago (2 children)

    It is impossible for me to remember all my passwords. Maybe I have more accounts than other people. I remember the most important ones, amongst them a very long password manager DB password that is annoying to enter, especially on mobile.

    First time I set up keepass I forgot the password. I still have the DB file without access. But the second time, I was more serious and committed to it, and made sure to remember and use the password. 😅

  • source
  • parent
  • context
  • [–] [S] 3 points 9 months ago (2 children)

    I find itch.io to be a great resource not just for games as a "finished product" but for prototypes as well. The regular gamejams contribute to this - a platform of many prototypes. They don't need the polish and coherence you'd want to invest and publish on Steam.

    Have you considered publishing your prototypes?

    Even as only a player, some prototypes make for very interesting playful exploration, even if it's short. For a technological, creative, and inspiration they can be a treasure trove as well.

  • source
  • parent
  • context
  • [–] 2 points 9 months ago

    To what end? What would you expect version numbers to do? How would you specify or use them, which what consequences?

    Grouping changes into releases with explicit numbering instead of a living standard with generic @supports checks?

    I guess it would make some things easier and more obvious.

  • source
  • parent
  • context
  • [–] 6 points 9 months ago

    For software to be perfect, can not be improved no matter what, you'd have to define a very specific and narrow scope and evaluate against that.

    Environments change, text and data encoding and content changes, forms and protocol of input and output changes, opportunities and wishes to integrate or extend change.

    pwd seems simple enough. cd I would already say no, with opportunities to remember folders, support globbing, fuzzy matching, history, virtual filesystems. Many of those depend on the environment you're in. Typically, shells handle globbing. There's alternative cd tools that do fuzzy matching and history, and virtual filesystems are usually abstracted away. But things change. And I would certainly like an interactive and fuzzy cd.

    Now, if you define it's scope, you can say: "All that other stuff is out of scope. It's perfect within it's defined target scope." But I don't know if that's what you're looking for? It certainly doesn't mean it can't be improved no matter what.

  • source
  • view more: ‹ prev next ›