• 1 Post
  • 154 Comments
Joined 1 year ago
cake
Cake day: October 5th, 2023

help-circle



  • I found a number of articles specifically stating that video games and software remain illegal. Unfortunately I couldn’t pinpoint the specific part of the law as they appear to br written in French and was running into hurdles with Google Translate character limits that I couldn’t be bothered to work around.

    I’m not sure if it’s explicitly illegal or if music, videos, etc are explicitly exempted, or if software etc is different due to terms of service for example.

    Furthermore, it’s illegal for anyone to record your IP address torrenting a work and track you down that way as it violates Swiss data protection laws.






  • It’s great to see the attempt and also an example of what the C4 guidelines are made to avoid.

    Notice how many comments are little nitpicks about this and that. Completely stalling the commit and getting further away from the original point of C4 which is to reduce contributor friction and avoid these kind of endless discussions on PRs.

    I don’t want to be too critical because some of that is a clear lack of understanding of the motivations of C4 which is explained more thoroughly in Pieter’s blog posts. You don’t want to adopt a contributor guidelines that you don’t understand of course.

    IMO it’s better just to implement it as-is and start using it in practice rather than bikeshedding.


  • Best practices for minimizing complexity:

    1. Try out “stacking”
    2. Simplify software design

    I didn’t say there wasn’t information in there but the above paraphrased quote goes to the heart of what my comment was about.

    Firstly, how is purchasing their product considered a “best practice”? It’s not generally accepted or the standard superior option by any stretch of the imagination.

    Secondly, the option they give to minimizing complexity is to simplify your software design. Ignoring a couple problems with this statement, if they’re being honest this should be above the recommendation to “try out stacking”.

    It doesn’t have to be that deep. You can give it a quick read and take from it what you will, but it is an ad for their product more so than it is an article that contains broadly useful information. They have every right to do so and maybe their product really is tremendously great but I’m just calling it how I see it.











  • This is not an answer to your question but it’s tangentially related.

    Someone I greatly respected ran an open-source project with the policy of merge everything. Completely flip this idea of carefully review, debate and revise every PR. His theory was that it helps to build an open community, and if something breaks someone else will revert that commit. He says that the main branch was almost always stable, a massive improvement to how it was run previously. He passed several years ago and for some reason this reminded me of him.

    I guess what I’m trying to say is if you get something out there that people find useful, the code will be looked at. It doesn’t help you if you’re looking for someone to collaborate sorry.