• 26 Posts
  • 375 Comments
Joined 2 years ago
cake
Cake day: June 11th, 2023

help-circle





  • A standard for build output might make sense to me. Maybe just throw cache stuff in .cache and build output to .build (with intermediate artifacts in there as well potentially).

    When enabled via flag, dotnet puts stuff into artifacts/obj, artifacts/bin, and artifacts/publish respectively. I like that. So much better than every proj folder having their own.

    And there’s really no need to make it a dot folder. For the publish you don’t want to anyway. And you may want to navigate to bin as well, to run a build or inspect the output.


  • A bit too broad to give a specific answer from my side.

    Overall, I prefer web based over apps, because I can CSS hack and if necessary JS hack them.

    Web also means it doesn’t litter my PC or mobile phone or tablet. And that it can’t fetch more data than it needs or I want it to have access to.

    Bad software is bad software, no matter if it’s installed or on the web.


  • The git compatibility is necessary for adoption and connected use.

    jj does significantly reduce the work interface, but the git compatibility increases complexity again.

    I tried it out a little bit a few days ago, and found it interesting. But given my git knowledge and tooling, I can’t reasonably switch. First, I would miss my TortoiseGit Log view (entrypoint to everything). But also, the connection between jj and git seems complex and potentially error prone.

    As a fresh and independent tool I can definitely see how it’s much easier and better, especially for people not familiar with Git.